Deploy

By the end of this page your Copilot will be live at a public URL, ready to embed.

Deploying a Copilot doesn’t build anything — it registers your configuration and serves the widget from qRaptor’s hosted renderer. There’s no pod to wait on, and later config changes apply within about a minute without redeploying.

Prerequisites

A brain bound (Bind a brain) — you can’t deploy without one.
Admin role.

Open the Deploy tab (or click Deploy in the header, which opens the same tab).

Configure the deployment

Choose your URL

Under Your URL, enter a slug. Your Copilot will live at https://<slug>.<domain>. The slug must be at least 3 characters (lowercase letters, numbers, and hyphens). A live check shows a tick when it’s available or This slug is already taken. if not.

Deploy tab form with the URL, production domain, access mode, and allowed origins

Pick a production domain

Production domain defaults to qraptor.app. Choose app.qraptor.ai (trusted domain) if your users’ networks block qraptor.app. The choice is saved to your project.

Decide who can use it

Under Who can use it?:

Anyone with the link (public) — no sign-in. Best for a public support or sales widget.
Signed-in users only (OIDC) — users sign in via your identity provider. Choose this for internal or gated Copilots (and to give users thread history).

(Optional) Add allowed embed origins

If you’ll embed the Copilot on another website, add that site’s origin (for example https://shop.example.com) under Allowed embed origins. You can also manage these after deploying — see Embed on your site.

Deploy

Click Deploy Copilot. The tab switches to the live view once provisioning finishes.

ℹ️

Deploying a Copilot consumes credits. If you don’t have enough, you’ll see Insufficient credits: X available, Y required — top up and try again.

After it’s live

The Deploy tab now shows:

A Live status (or Deploying… while it provisions), with your URL and a copy button.
Embed on your site — script, iframe, and direct-link snippets (details).
Settings — a summary of who can use it and the bound brain.
A Redeploy button to re-run the deployment (for example after changing the brain).

Deploy tab in the live state showing the URL, embed snippets, settings, and Redeploy

💡

You rarely need Redeploy for cosmetic changes — brand, behavior, and prompt edits apply automatically within ~60s. Redeploy is for structural changes like swapping the bound agent or system.

Common issues

Deploy Copilot is disabled — You need a valid slug (≥ 3 chars, available) and a bound brain with a default agent or a bound system.
“This slug is already taken.” — Choose a different slug.
“No brain bound” — Bind an agent or system on the Brain tab first.
Insufficient credits — Add credits and deploy again.