Start free

Ship several apps as one release.

Build apps and components from a branch or tag, or promote what runs in staging to production. One release, one approval, and a history of what went where.

Start freeBook a demo

Each environment left to right towards customers. A card that spans environments means the same version.

  1. Demo project
  2. Releases
Sample data

Two ways to release

Build it, or promote what you tested.

Build from a branch or tag

Pick the apps and infrastructure components, then a branch or tag. Each one builds on its own pipeline, then they deploy together.

  • If one build fails, nothing deploys
  • Or choose to deploy what built and ship the rest later
  • Add a note for whoever looks at it later

Promote between environments

Take what runs in staging to production. You see the version each app runs in both environments before you start.

  • Flags a version older than what runs in the target
  • Tells you when something isn't in the source environment
  • Production releases warn that customers get them as soon as they deploy

Or ask Mica to ship it.

Name what goes and where. The approval is the confirmation.

How approvals work
  1. 01Say "ship api and web from main to staging" or "promote staging to production"
  2. 02Mica works out the apps and components, states the plan in one sentence and asks for one approval
  3. 03A release card in the chat follows it while it builds and deploys
  4. 04If a build fails, Mica reads its logs, names the cause and proposes the fix

History

Know what went where.

See what runs in each environment, and how it got there.

  • Release history

    Every release to an environment, newest first: who started it, whether it built or promoted, and how it ended.

  • An outcome for each app

    Each app and component in a release shows its commit and whether it built, deployed or failed, with the error when one did.

  • One row in Activity

    Activity shows a release as one row, not a run for each app, so the feed stays readable.

Questions

Releases and your pipelines.

Do apps still deploy on every push?
Yes. Each app keeps its own pipeline and push trigger. Use a release to ship several things at once, or to move tested versions from one environment to the next.
Can a release include infrastructure?
Yes. A release can include the environment's infrastructure components as well as its apps.
Does every release need Mica?
No. Start one from the Releases page with New release, or ask Mica in the chat. Either way you confirm it once before anything builds or deploys.

Ship your next release in one go.

Start with one app, then release several together.

Start freeGetting started