Publish to production

By the end of this page you will have deployed your app to a production URL, and know how to push later updates.

Prerequisites

An app in Preview Ready state (The generation flow).
Sufficient credits for the deployment cost (shown during publish).

Steps

Click Publish

In the workspace toolbar, click Publish. qRaptor checks whether this app already has a production deployment.

If no deployment exists yet, the Deploy to Production dialog opens on the configure step (below).
If a deployment already exists, an Update Deployment dialog opens instead — see Updating an existing deployment.

Workspace toolbar with the Publish button

Configure the deployment

Fill in:

App Name — a URL slug for your app. qRaptor checks availability live as you type.
Production domain — choose between the default qraptor.app domain or app.qraptor.ai.

The dialog also shows the credit cost of the deployment and checks it against your available balance before you can proceed.

Deploy to Production dialog configure step with App Name, domain selector, and credit cost

The Deploy button stays disabled until your slug is valid and available, and you have sufficient credits.

ℹ️

Credit cost and balance are checked before deployment starts, not after — you won’t get partway through a deploy and then hit an insufficient-credits error.

Watch it deploy

Once you click Deploy, qRaptor shows a progress checklist: Configuration validated → Provisioning resources… → Finalizing deployment. This polls for status every couple of seconds.

Deploying step showing the configuration, provisioning, and finalizing checklist

Get your production URL

Once complete, the dialog shows your app’s Production URL, with a copy button and an Open App button to view it live.

Deploy success step showing the production URL, copy button, and Open App button

Updating an existing deployment

If your app is already deployed, clicking Publish opens Update Deployment instead of the create flow. This shows an Update to v{n+1} button (e.g. “Update to v3” if you’re currently on v2) and uses a rolling update strategy — your app stays available while the update rolls out.

💡

Updating an existing deployment doesn’t charge credits — only the initial deployment does.

Common issues

Slug unavailable — Someone else has already claimed that app name on the chosen domain. Try a different slug.
Deploy button stays disabled — Check that your slug passed the availability check and that you have enough credits for the deployment cost shown.
Deployment shows an error step — Click Try Again. If it keeps failing, check Deployment status for more detail.