Skip to Content
DeploymentsDeployment types

Deployment types

Every production deployment is one of four types. The type is set by what you deploy, and it decides whether the deployment has a user-facing page, an embeddable widget, or only API endpoints.

TypeHas a user-facing UI?Deploy it from
Web App✅ A full web pageThe vibe workspace
Copilot✅ A chat widgetCopilot Studio
Agent API❌ API onlyThe Deploy menu on the Deployments page
Multi-Agent❌ API onlyThe Deploy menu on the Deployments page

Web App

A Web App deployment serves a complete vibe-coded application — its frontend and its backend — at your-app.qraptor.app. Use it when you generated a full app and want end users to open it in a browser.

Deploy a Web App from the vibe workspace. See Publish to production.

Copilot

A Copilot deployment publishes an AI chat widget you can embed on any website or open as a standalone page. It’s powered by an agent (or a multi-agent system) and has no backend of its own.

Deploy a Copilot from Copilot Studio. See Deploy a copilot and Embed a copilot.

Agent API

An Agent API deployment exposes one or more agents as API endpoints — with no web page or widget. Use it when another system calls your agent: a backend service, a scheduled job, or another agent.

An Agent API deployment gives you:

  • A base URL (your-deployment.qraptor.app) with per-agent endpoints.
  • API keys for programmatic access.
  • Scheduled runs for recurring jobs.
  • A2A integration so other agents and external platforms can call yours over the standard A2A protocol.

Create one from the Deploy menu on the Deployments page — or straight from an agent editor’s Deploy menu (both open the same wizard). See Production deployments.

Multi-Agent

A Multi-Agent deployment publishes a whole multi-agent system behind a single endpoint. A router directs each request to the right member agent, and the members are deployed automatically alongside it.

Build the system first in MAS Systems, then create the deployment from the Deploy menu on the Deployments page — or from the router builder’s Deploy button (Deploy a MAS).

Combining types

Agents and multi-agent systems don’t only stand alone — you can also add them on top of a Web App or Copilot deployment. For example, a Web App deployment can host both its application and a set of agents that its frontend calls. A deployment’s card shows everything inside it:

  • Application Service — the app backend (Web App).
  • Chat Widget — the copilot UI (Copilot).
  • Agents — one or more deployed agents.
  • MAS System — a deployed multi-agent system.
  • API Only — no user-facing surface.
A deployment card showing its type badge, the services it contains, its URL, and its authentication methods

Starting a deployment from the Deployments page

For Agent API and Multi-Agent deployments, use the Deploy menu at the top of the Deployments page:

  • Agent — deploy one or more agents (Managing agents).
  • MAS System — deploy a multi-agent system (Multi-agent systems). Only systems with a published production version are listed.
  • From blueprint — appears only when the project was created from a blueprint that carries a deployment configuration.
The Deploy menu on the Deployments page showing Agent and MAS System options
ℹ️

Web App and Copilot deployments are started from their own builders, not this menu — the Deploy menu here is for agent and multi-agent deployments.