Emergent

Publishing types

Overview

Emergent has two publish environments, preview and production, that serve distinct purposes in your development workflow. Understanding how they differ helps you test confidently and release intentionally.

Coming from another platform? Publishing is the same thing as deploying - what other tools call deploy, deployment, or redeploy, Emergent calls Publish and Re-publish.

The two publish environments

Preview

Your development sandbox, used for building and iterating with the agent before going live.

Production

The live, publicly accessible version of your app, published from the Emergent platform.

Preview environment

The preview environment is your active development sandbox, the place where the agent builds, edits, and iterates on your app. It is not a snapshot or a permanent artifact; it is a single, mutable workspace.

Key characteristics:

  • Single sandbox per project: there is one preview environment per job, not multiple parallel previews
  • Preview URL: accessible at {slug}.preview.emergentagent.com
  • Sleeps after inactivity: the preview spins down after 30 minutes of inactivity to conserve resources
  • Separate environment variables: preview env vars are independent from production after the first publish (the first publish carries .env values across as a one-time seed). You can add .env keys, which will merge on re-publish but not the values of the keys.
  • Rollback in preview: you can roll back the conversation and code in preview using the Rollback button in the chat timeline; re-publish to push any changes to production

When to use preview:

  • Building and iterating with the agent
  • Testing new features before releasing to users
  • Reviewing changes before hitting Publish or Re-publish

Because preview sleeps after 30 minutes, it may take a moment to wake when you return. This is expected behaviour and does not affect your production published app.

Production environment

Production is the live version of your app, the URL your end users visit. You create or update it by clicking Publish (first time) or Re-publish (subsequent updates) from the platform.

Key characteristics:

  • Production URL: your app is served at <appname>.emergent.host (or a custom domain)
  • Stays live: production does not sleep the way preview does
  • Separate environment variables: production secrets are managed independently from preview; edit them in Preview → Manage → Secrets
  • Default subdomain cannot be renamed: once set, the subdomain is permanent; deleted URLs are never reused

Published app operations available in production:

  • Re-publish: update the same app with the latest code

  • Replace: zero-downtime blue-green swap of a different job onto a live app (user secrets carried over; choose to keep or start a fresh DB)

  • Rollback: revert to one of up to 3 previous production images (URL and database remain unchanged)

There is no "Promote to Production" flow. You simply iterate in preview and click Re-publish when you are ready to ship. Republishes are free of charge (beyond the monthly tier fee).

Comparison table

Aspect Preview Production
URL {slug}.preview.emergentagent.com <appname>.emergent.host (or custom domain)
Sleep behaviour Sleeps after 30 min inactivity Always live
Environment variables Separate from production (seeded from .env on first publish) Separate from preview; managed in Preview → Manage → Secrets
Typical use Building, iterating, testing Live release to end users

| Rollback | Chat/code rollback via timeline button | Up to 3 previous production images |

Environment variables and secrets

Preview and production environment variable sets are completely separate. Changes you make to secrets in one environment do not automatically carry over to the other. The one exception is if you are adding a brand new key for a new integration. The secret values for the key still has to be set in the secrets panel.

  • In preview: env vars live in .env files inside the app code; the agent reads and writes them directly
  • In production: secrets are managed in Preview → Manage → Secrets; the UI can edit values of existing keys but cannot add or delete keys (to add a new key, ask the agent to add it to .env, then re-publish)

Never paste real API keys into the chat. Chat content is sent to the AI provider. Enter real third-party keys in Preview → Manage → Secrets → Custom keys instead.

Publishing plan considerations

Publishing tiers, Starter, Launch, Grow, Scale, Elite, determine the CPU, and RAM for your production app. The minimum to start a published app is 50 credits. Tier changes take approximately 2 minutes and do not require a rebuild.

For more detail on resource allocation per tier, see Publishing plan levels.

If you encounter problems during published app, consult the publishing issues and publishing pipeline failures troubleshooting guides.

Related pages

The chat-to-published app flow

See how your app goes from a chat prompt to a live published app.

Publishing plan levels

Compare resource allocations across Starter, Launch, Grow, Scale, and Elite tiers.

Custom domain

Configure a custom domain for your production published app.

Publishing issues

Troubleshoot common published app errors and failures.