Custom domain

With KB Cloud Pro and KB Cloud AI Agent, killBottleneck can run on your own domain — e.g. tasks.company.com instead of company.killbottleneck.com. You set it up yourself in Organisation admin; no need to write to us or wait. Your original address keeps working.

killbottleneck.com

Organisation admin → Custom domain. Only admins on KB Cloud Pro and AI Agent see the section.

What you need

• To be an admin of the organisation in killBottleneck (others don't see the section).
• Access to your domain's DNS settings — at your registrar or at Cloudflare, wherever the domain lives.

Steps

1. In killBottleneck open Organisation admin → Custom domain.
2. Type the address you want (e.g. tasks.company.com) and click Continue. The app shows two DNS records — one for the app, the other (agent.…) for the chat with the Hermes agent.

killbottleneck.com

Two CNAME records to copy — one for the app, the other for the agent chat.

3. Add both records at your DNS provider exactly as shown (the icon next to the value copies it).
4. Back in killBottleneck, click Check and switch. You see whether each record is right. When they are, the server switches over by itself within a few minutes — it issues an HTTPS certificate and changes the instance address.

killbottleneck.com

The records are right and the server switches over by itself. The app is unavailable for a few minutes.

5. Done. You sign in once more on the new address (the browser remembers sign-ins per address). Links in e-mails from the app now point to the new address.

A subdomain, not the root domain

We recommend a subdomain (tasks.company.com). A root domain (company.com) only allows an A record pointing at the server IP — if we ever move the server, the record would need updating. A subdomain points via CNAME to our address and survives a move.

When the check fails

• "record not visible yet" — new records usually propagate within minutes, sometimes hours. Try again shortly (you can check once every 10 seconds).
• "points elsewhere" — if your DNS is at Cloudflare, switch both records from the orange cloud to the grey one ("DNS only"). A certificate can't be issued through the Cloudflare proxy. Otherwise check the value for typos.
• The switch failed — the section shows the reason. Meanwhile the instance keeps running on the original address; nothing broke. Fix the records and try again.
• If your domain has a CAA record, it must allow Let's Encrypt (0 issue "letsencrypt.org").

Changing or disconnecting

• A different domain: enter the new one and follow the same steps — the old one disconnects by itself.
• Disconnect: the Disconnect domain button. The app returns to the …killbottleneck.com address; you can then delete the DNS records.

What stays the same

• The original …killbottleneck.com address keeps working — the mobile app, AI agent connections (MCP) and webhooks set up earlier don't break.
• E-mails from the app are still sent from our address (sending from your domain isn't offered yet).
• Google sign-in: if it is on for your instance, write to us — the new address has to be added in the Google settings.