Deploy
How a verified app goes online in REM CloudHub by itself, its database, its permanent link, Redeploy, and what a deploy card means.
You do not press a deploy button. As soon as a build passes its checks, Vibe Coder deploys it to REM CloudHub in the background, while the chat finishes. Deploying never delays the result or the preview.
What happens
Database. If the plan says Saves your data in a database, REM CloudHub creates a database for the app (256 MB to start) the first time. The connection details are given to the app by REM CloudHub when it starts; they are never written into your code.
Code. Your app's files (only your app: nothing of Vibe Coder's tooling) are saved to the app's repository on its own branch.
Deploy. REM CloudHub builds the app into a container and starts it. A web app built by Vibe Coder serves its screens and its API from one address.
Check. Vibe Coder waits until REM CloudHub says the app runs (at most 15 minutes) and opens its address once to be sure it answers.
Deployed. The card reads Deployed — your application is ready, with Open app and the permanent link, shown once. The preview pane switches to the deployed app, and the project shows as live in the sidebar.
What else the app needs goes with it: AI (the app gets a key for REM CloudHub's AI gateway when it calls AI), file storage (its own folder in REM CloudHub Files), a Redis cache, the data warehouse, or mail, when the code uses them.
One permanent link
A project has one address for its whole life. Every change you deploy later replaces the running version at the same link, so bookmarks and links you shared keep working. Where the app answers: see Custom domains.
Redeploy
The chat header has one small Redeploy: it deploys the latest delivered version again, with the same steps. Use it after REM CloudHub was down, or after you changed the app's settings in REM CloudHub. A second deploy never starts while one is still moving.
Deploy states
You see | Means |
|---|---|
Deploying | REM CloudHub is building and starting it |
Retrying | A step failed and is tried again; the build is not affected |
Deployed | Running at its permanent link |
Code saved | A project with no app to run (scheduled jobs only): the code is saved and the jobs are registered in REM CloudHub |
Deploy failed | The deploy did not finish; the card says why. The preview keeps working; ask "deploy it again" or use Redeploy |
Other kinds of project
MCP server. Ask for "an MCP server that…" and the deployed project is a tool server for AI assistants, reachable at its link under
/mcp.Scheduled jobs. Ask for "a job that every morning at 8…" and you get a project with jobs and a small job console as its preview. Registering the jobs in REM CloudHub shows one confirm card listing every job, its file, its schedule and its time zone.
After deploy: REM CloudHub
Open in REM CloudHub takes you to the app's page there: its deploys and versions, logs, the database, its settings (address, sign-in required, allowed addresses, rate limits) and its usage. Plans that include Deploy to CloudHub can deploy; your REM CloudHub plan covers the running app.