WA.cr

Your brand and your own domain

Set your product name, colour and logos, and run the console on your own domain, including the certificate step our team does with you.


Your tenants can work in WA.cr under your name, on your own web address. Branding takes a few minutes; your own domain takes a DNS record from you and a certificate step done together with our team.

Your branding

Open your Partner organisation page and find Branding. The owner and Partner admins can change it, even before the setup fee is paid.

You can set:

  • Brand name. Shown in the console header on your own domain.
  • Brand colour. Used as the accent in the mobile app.
  • Icon, light and dark. A square mark for small spaces.
  • Logo, light and dark. Your wordmark for the header and the sign-in page.

Image rules:

  • PNG, JPG or WEBP. SVG isn't accepted.
  • Up to 2 MB each.
  • Icons must be square.

If you leave a dark version empty, the light one is used. Changes reach your own domain within about a minute.

Your own domain

You run the console and the API on two hostnames of your own, for example app.yourbrand.com and api.yourbrand.com.

  • You need both, or neither.
  • They must sit side by side on the same domain: api.yourbrand.com, not api.app.yourbrand.com.
  • Your tenants' storefronts stay on their existing addresses.

Steps

  1. Open your Partner organisation page and choose Domain.

  2. Enter both hostnames and press Save.

  3. Add the one TXT record the page shows you at your DNS provider. It looks like this:

    TypeNameValue
    TXT_waht-verify.yourbrand.comwaht-domain-verification=…

    One record covers both hostnames. Neither the name nor the value mentions WA.cr.

  4. Press Verify.

  5. Wait for our team for the certificate step, below. Don't point your hostnames at us yet.

Step 4: the certificate, done with our team

Verifying proves the domain is yours. It does not make your hostnames work yet: a secure certificate has to be issued for them and our servers set up to answer on them. Our team does this by hand, with you:

  1. We request one certificate covering exactly your two hostnames.
  2. We send you two CNAME records, one for each hostname. Their names start with _acme-challenge_. Add both at your DNS provider, exactly as sent.
  3. Once the certificate is issued and your hostnames are set up on our side, we send you the address to point both hostnames at. Add an A record for each hostname with that address.
  4. We check both hostnames and confirm when your domain is live.

Point your hostnames at us only when we ask. Before the certificate is in place, a visitor would get a security warning instead of your console.

Keep the TXT record and the CNAME records in place afterwards.

If it doesn't work

  • Verify fails. DNS changes can take a while to spread. Check the TXT record's name and value, wait, and try again.
  • A hostname is already claimed. Another organisation has claimed it. Contact us.
  • You change a hostname. Editing the domains withdraws the verification, and the hostnames stop working as your console until they are verified again and the certificate step is redone for the new names. Talk to us before you change them.