Deployment

Settings › Deployment is where the site goes live: its status and address, your own domain, Deploy now, the mobile app and the agents' place.

Web

• Status: Not deployed, Building…, Live, or The last build failed.
• Address: your-name.flexos.site, claimed for the project.
• Vercel project: the project that builds and serves the site, linked to the repo.
• Deploy now builds the site from the repo as it is. It puts the Vault's keys onto the site first, so after you add or change a key this is what brings it in. After a failed build it tries again.

Custom domain

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.

Mobile app

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.

Agents

The project's agents live together in one place, your-name.flexapp.one, made with the project at setup. Each agent's page is at /<agent> on it; you open one from the Agents rail, where its space shows the page (Preview), its files and its playbook (Doc), signed in as you. The block here is the place itself: its address, its last build, this month's AI use against one ceiling (past it, no agent opens until next month), and for the owner Rebuild (the same commit again, which is how a new key reaches the agents) or Set up, for a project made before agents had a place. Flexi builds the agents in a chat; nothing is typed in here.

Where next

• Preview and going live: every build, and Put this live.
• Keys and the Vault: what Deploy now puts on the site.