The address, your own domain, the mobile app, and agents.
Settings › Deployment is where the site goes live: its status and address, your own domain, Deploy now, the mobile app and the agents.
your-name.flexos.site, claimed for the project.Type the domain you own, like app.example.com. The panel gives you two records to add at your domain provider, each as name → value with what it is for. The site answers on your domain once the records have spread, usually within the hour. Until then the FlexOS address keeps working, and it keeps working after.
Ship to the stores takes a FlutterFlow app to the App Store and Google Play. Where it stands shows the last build and what each store holds; Fix keys asks for the store keys that are missing. The phone app article has the whole flow.
The project's agents, each at its own address, your-name-<agent>.flexapp.one, with Open, which opens the agent's own page signed in for you (a ticket for that person, that project and that agent, fifteen minutes). The owner sets one up by typing its folder's name under agents/; its code must be in the repo first. FlexOS makes its Vercel project, its address and its secret, puts the Vault's keys and FlexOS's own model key on it, and starts its first build. The line under the list says what the agents have spent on AI this month, against one ceiling; past it, no agent opens until next month.