Deploying cards

Deploying an experience to an account turns each designed card into a deployed card: a flat, self-contained record that carries your branding and its template, plus a global short id that is its shortcode.

Why deploy denormalises

At request time, a deployed card is a single lookup keyed by its shortcode — there’s no experience → card traversal. That’s what makes hosted pages and on-site widgets fast and cacheable.

What happens when you deploy

1. Choose Deploy in the editor and pick the account.
2. Each card is denormalised with that account’s branding.
3. Each deployed card gets its shortcode and link.

Re-deploying and multiple accounts

• Re-deploy overwrites the deployed card in place — the shortcode stays the same, so existing links keep working.
• Deploying the same experience to two accounts produces two deployed cards, each with its own shortcode and branding.

Note

Edits you make in the editor change the designed experience. They don’t reach people until you re-deploy.

Where deployed cards show up

• Hosted (Outpost): the shortcode link opens the card directly.
• On your site (Onflow): the snippet matches the page against your account’s manifest, finds the right card shortcode, and loads that card’s artifact — no per-page database hit.

Related

• The id you get: shortcodes.
• The model: experiences & cards.