Reference · names and addresses
Names and addresses
A box has a name of two parts, a short name and your handle: home.<handle>. Environments answer under it, on a domain of their own, bettik.dev. This page is the rules.
The shapes
home.<handle>- Your default box. Its page is on the dashboard.
dev.<handle>- Any other box of yours: its short name, then your handle. A box of an organisation's has the organisation's name instead:
jordan.northwind. catan.home.<handle>.bettik.dev- An environment: its name, then the box.
api-catan.home.<handle>.bettik.dev- An environment's extra address: the entry and the environment, joined by a hyphen, then the box.
public.home.<handle>.bettik.dev- The box's public folder,
~/public: a file opens for anyone with its link. gateway.home.<handle>.bettik.dev- The box's messaging gateway: producers post to a topic with a token, and the box delivers to your sessions.
home.<handle>.bettik.dev- The machine itself, for ssh only.
mcp.bettik.ai- The connector. One address for every box you have.
Handles and names are lowercase letters, digits and hyphens. An environment's name is what you asked for, lowercased, with punctuation turned to hyphens; if that changed it, Claude tells you. An environment's name is unique on its box, and a box's short name is unique under your handle, so two addresses never collide.
Why environments have a domain of their own
An environment runs code you wrote; the dashboard and your sign-in run code Bettik wrote. Keeping them on different domains means nothing an environment does -- a cookie it sets, a script it runs -- can reach your Bettik sign-in. So a private environment has a sign-in of its own: the first time you open it, you pass through www.bettik.ai and come straight back.
Some words are reserved — the ones it would be bad for a stranger to hold on a real subdomain. You will not get support. An environment cannot be called public either: that name is the box's public folder. Nor browser or gateway, the box's own browser and gateway (services).
Who can open an address
An environment's address opens for you and for nobody else, unless you say otherwise. Requests reach your box through a tunnel the box itself opened to Cloudflare, and a gate on the box checks your sign-in before anything reaches an environment; Cloudflare carries the traffic and decides nothing. A visitor with no session is sent to sign in at www.bettik.ai, once per address, and comes back to the address they asked for. The box itself accepts no HTTP from outside.
So there is nothing to expose and nothing to lock down. A dev server bound to 0.0.0.0 inside an environment is reachable at its address by you, and not by the internet. The database is never published at all; from a laptop it is an ssh tunnel to the port in the environment's .env.
An environment can be made public. share_environment with public, or the button on the box's Environments tab on the dashboard, and anyone with the URL can open it -- no account, no sign-in. That is for a friend, a client, a playtester. It is the environment's addresses only, every one it has: the box, the dashboard and the connector stay yours, the firewall does not change, and the tunnel is still the only way in. A clone of a public environment starts private. private takes it back within a minute.
Public means public: crawlers included, and whatever the environment does for a stranger, it now does. Nothing in front of a public environment limits who or how often. When something you built is for other people for good, that is a deploy somewhere else.
The handle is permanent
It is in the name of every box of yours and every environment's address, and so in every URL anyone has bookmarked. It is chosen once.