Upgrading an App

Most apps start instantly in your browser. When you ask for something a browser can't do — saved data, logins, a database, a real backend — cdbx moves your app onto a real server. Your original stays exactly as it was; the upgrade is a copy, the same as a fork.

What happens

1. Your app's template is mapped to the matching server-backed template (React → React + Vite, Vue → Vue + Vite, and so on).
2. Your files are copied onto the new server, laid on top of the target template's scaffolding, so it boots correctly from the first load.
3. Your files are scanned for the packages you actually import, and those are merged into the new package.json.
4. Your environment variables (secrets) come with it, so connected services keep working.
5. An AGENTS.md is generated for the upgraded app — your original notes (if any) plus an AI-written summary of what's been built so far, so its AI chat has context from message one.

Supported templates

Available for: HTML, JavaScript, TypeScript, React, React + TypeScript, Vue, Svelte, Angular, and Preact.

Compiled/scripting templates (Rust, Python, Go, and similar) aren't offered here — a server upgrade is built around a persistent, running dev server, which those templates don't use.

Requirements

• Server-backed apps need to be available on your plan.
• You must own the app (upgrading someone else's public app isn't supported).

After upgrading

You're taken straight to the upgraded app's editor while it finishes starting. Your original stays exactly as it was — its own settings show how many times it's been upgraded from.