Apps
An App is anything you build with cdbx. Describe what you want, and cdbx builds it.
There is only one kind of thing to make. You don’t pick a project type, a framework, or where it runs — cdbx works that out from what you asked for.
Where your app runs
Most apps start instantly in your browser. Nothing to install, nothing to wait for.
Some things a browser can’t do: saving data between visits, user accounts and logins, a database, or a real backend. When you ask for one of those, the AI tells you what’s needed and asks whether to set it up. Say yes and your app moves onto a real server, keeping everything it already had.
You never have to choose. If you don’t need a server, you never get one.
Building
Type what you want and press enter. That’s it — there’s no template picker and no confirmation step.
Your app is React and TypeScript unless you ask for something else. If you’d rather have Vue, Svelte, Python or plain HTML, just say so.
Build, Plan and Ask
The dropdown next to the send button changes what happens to your message:
- Build — make the change. This is the default.
- Plan — talk it through first. The AI says what it intends to do and waits for your go-ahead. Nothing is written until you agree. Use this when you’re still working out what you want.
- Ask — a question about cdbx itself, answered from these docs. Changes nothing in your app.
Starting in Plan mode from the home page opens your app with an empty preview, ready to plan. It shows as Plan in your list until something is actually built, and it stays there — you can come back to it any time.
Your apps
Everything you’ve built is under Apps. Search, filter and sort it, or select several at once to tag, archive or delete them. Once you have a mobile app, the filter also has Type, to show only Mobile or only Web apps. The button next to the sort control switches between the grid and a list; it shows the view it will switch to.
Each app has a settings panel — the cog above the preview, next to Share and Publish — for renaming, sharing, environment variables, connectors, a database, and exporting to GitHub.
Apps you haven’t opened in a while
An app that runs on a server and hasn’t been opened for 30 days is stored away to save space. Nothing is lost: open it and it comes back, which takes a little longer than usual, up to about a minute. Any packages it uses are installed again as it starts.
An app that hasn’t been opened for a year is deleted for good. We email you twice first, at 6 months and at 9 months, with the date. Opening the app before then is all it takes to keep it.
Published apps are never deleted, however long it’s been. Apps that run in your browser aren’t affected by any of this.
Moving an app to another region
An app that runs on a server lives in one of two places: Stockholm (EU) or US East. A new app goes to whichever is nearer to you when you make it.
To move one, open its settings, and under General → Region press Move to US East (or Move to Stockholm). The app stops while it moves, usually for under a minute, and its files go with it.
- Its preview address changes, from
….eu.preview.cdbx.aito….us.preview.cdbx.aior back, so old preview links stop working. Its published address stays the same. - An app can move up to 3 times a day.
- In a Team, only the Team’s owners and admins can move its apps, since a Team may need its data kept in one region.
Advanced Mode
By default an app shows a chat and a live preview, and nothing else. To give the preview the whole width, click the button at the left of the preview’s tab row; the same button, facing the other way, brings the chat back.
If you want the code, turn on Advanced Mode in App Settings → Workspace. That brings back the file tree, the code editor, search, changes, the terminal, the console and dev tools — plus the Code Execution editor for compiled languages.
It’s off by default, saved to your account so it follows you between browsers, and takes effect immediately. You can turn it off again whenever you like; nothing about your app changes either way.