Start free today paid checkout coming soon

Less chasing bugs.
More shipping fixes.

Find the failure. Prove the fix. Take control of the recovery. Start free with monitoring, replay and verification, then explore signed code patches and recovery controls for your release workflow.

See a bug reproduced and a fix verified Interactive demo · no account needed
  • Free

    Prove the workflow on your first app.

    $0 / month

    No card needed

    Capture your first bug

    No card needed · start with one app

    • Capture the steps behind a failure
    • Replay supported recordings against your code
    • Try fix verification before upgrading
    • 1 workspace member
    • 1 project
    • 100 new capsules / month
    • 500 MB capsule storage
    • 7 days capsule retention
    • Docs and best-effort help
  • Pro

    Make reproducible bugs part of your daily workflow.

    $49/ month

    Per workspace · billed monthly

    Start free, explore Pro

    Creates a Free workspace · no card needed

    • 20× the monthly capsules of Free
    • Keep evidence for 30 days, not just 7
    • Work together with 5 included members
    • 5 workspace members
    • 3 projects
    • 2,000 new capsules / month
    • 5 GB capsule storage
    • 30 days capsule retention
    • Email support
  • Enterprise

    Shape the capacity and support around your organization.

    Custom

    Quote based on your needs

    Discuss your needs

    Scope and pricing agreed with you

    • Plan for higher capture volumes
    • Agree the retention your team needs
    • Define your support requirements
    • Members and projects by agreement
    • Capsule volume and storage by agreement
    • Retention by agreement
    • Event and transaction volume by agreement
    • Agreed support scope

Free is available now. Paid checkout is coming soon. Pro and Team prices show the planned upgrade options. Start on Free, or talk to us about a paid plan. No payment is taken here.

In every plan

Buy back the time between “it broke” and “it’s fixed.”

Every plan includes the core workflow. Paid plans give your team more capacity and a longer window to investigate.

  • Know what needs attentionGroup errors into issues, track crash-free releases, and inspect slow transactions and traces. Prioritize with production evidence.
  • Get past “can’t reproduce”Capture supported actions, network responses and state in a capsule. Replay the recorded scenario against your app code.
  • Check the fix, not just the ticketRun the same supported scenario against your working tree. Inspect verification results and evidence before closing the bug.
  • Keep fixed bugs in your CITurn a captured failure into a regression scenario with bugcapsule regress. Check whether that recorded failure comes back.
  • Keep the handoff in contextUse comments, assignees and linked issues to keep the investigation together. Connect alerts to Slack, email, webhooks, GitHub or Jira with setup.
  • Control what leaves the appUse on-device redaction, sampling, scoped keys and a remote capture kill switch. Flutter, Android, iOS and web share one dashboard.

Replay and verification apply to supported recordings and dependencies, not every possible failure. Check your platform’s coverage. Integrations require configuration.

From a broken release to a controlled recovery

Finding the bug is only the beginning.

Contain the damage, validate the exact fix, and restore access with evidence. Bring the response into the same workflow as the bug.

01 / Emergency Recovery

Pause the broken feature. Keep the response moving.

Use signed policies to block a failing feature, make it read-only, show a maintenance message or request an update in an integrated app. Target affected versions while your team prepares the fix.

  • Feature controls backed by signed policies
  • Server guards for sensitive operations
  • Approval and audit history for incident actions
Explore Emergency Recovery

02 / Signed Code Patches · early access

Deliver a targeted fix to an app already installed.

Replace registered module logic, UI surfaces and assets without rebuilding the app binary, where the app and distribution channel qualify. The app checks the signed patch and activates it on a later launch.

  • Registered logic and layouts on supported mobile runtimes
  • Replay validation tied to the exact patch artifact
  • Compiled fallback and signed rollback
See what you can patch

03 / Staged rollout & restoration

Expand when the evidence says it’s safe.

Restore a guarded feature in stages: 1%, 5%, 25%, then everyone. Watch crash rates, transaction failures or latency. Automatic restoration waits for enough data and reapplies the restriction when a configured guard is breached.

  • Health checks before the next stage
  • Second-person approval where required
  • Rollback actions and reporting-device status
See staged restoration

04 / QA context & AI-assisted investigation

Give your team and coding agent a useful starting point.

Attach approved QA context and bug evidence to MCP repair tasks. With incident AI assistance enabled, draft root-cause hypotheses, recovery strategies and test proposals for your team to review.

  • Approved expected behavior alongside bug evidence
  • Scoped agent access and repair-task history
  • People review advice and approve recovery actions
Explore the agent workflow

Planning for recovery and patching?

Let’s review your apps, patchable scope and rollout needs together. Access and commercial scope are confirmed separately; a Pro or Team signup starts on Free.

Discuss recovery & patching

Recovery requires compatible SDKs and app integration; sensitive operations also need server enforcement. Signed patches are early access and require a shipped patch runtime, registered capabilities and an eligible distribution channel. Arbitrary native code, new capabilities and runtime changes still require a new app release. Rollback receipt depends on device connectivity and activation. QA, MCP and AI assistance require configuration; you run your own coding agent.

Compare plans

Choose the room your team needs.

LimitFreeProTeamEnterprise
Monthly price / workspace$0$49Quote
Best forProving the workflowDaily debugging, small teamsCustom capacity and support
Workspace members15By agreement
Projects13By agreement
New capsules / month1002,000By agreement
Capsule storage500 MB5 GBBy agreement
Capsule retention7 days30 daysBy agreement
Error events / month5,00050,000By agreement
Performance transactions / month1,00010,000By agreement
SupportDocs, best-effort helpEmailAgreed scope

Prices in US dollars per workspace, including the listed members. Annual monthly equivalents are rounded; the full yearly charge is shown above. Paid checkout is not yet available. Applicable taxes will be shown before payment.

Billing FAQ

Before you upgrade.

Something missing? Ask us directly.

If the core features are free, why upgrade?

Upgrade when more people need to investigate, more apps need coverage, or you need more recorded evidence and time to use it. Pro adds 5 included members, 20× Free’s monthly capsule allowance and 30-day capsule retention. Team gives development and QA 15 members, 10 projects and 90-day capsule retention.

Is the price per person or per workspace?

Per workspace, with the listed members included: 5 on Pro and 15 on Team. The listed capsule, storage, event and transaction allowances describe each plan. For needs beyond Team, contact us to agree an Enterprise scope.

When can I pay for Pro or Team?

Paid checkout is not available yet. The Pro and Team buttons create a Free workspace so you can evaluate the workflow now. To discuss a paid plan or higher usage before checkout opens, contact us.

Can Code Patches fix any code without a store release?

They can replace supported logic, surfaces and assets that your app registered when it was built with the patch runtime. They cannot replace arbitrary native code or add new plugins, permissions or runtime capabilities. Patches activate on a later launch and distribution eligibility must be reviewed. See the patching scope.

What counts as a capsule?

One recorded failure uploaded by the SDK, automatically or from the QA capture button. Error events and performance transactions from monitoring are counted separately.

How does annual billing work?

You pay for twelve months up front and get two months free: Pro is $490 a year and Team is $1,490 a year, instead of $588 and $1,788 on monthly billing.

Do subscriptions renew automatically?

Only if checkout clearly says so and you agree to it. Any change to a renewal price is announced in advance, with a chance to decline. See Subscriptions, prices and renewal.

Can I cancel?

Yes. Your plan stays usable until the end of the period you paid for. Voluntary cancellation is not refunded; mandatory legal rights are not affected. See Cancellation.

Can I change plans later?

Start with Free today. Pro and Team are planned upgrade options once paid checkout is available; self-service plan changes are not live yet. If you need more capacity now, contact us.

Are Emergency Recovery, Code Patches and AI included in my plan?

These workflows have separate setup and availability requirements; this page does not promise access through a paid tier. Recovery needs compatible SDKs and app integration. Signed Code Patches are early access and need a registered base, trust configuration and distribution eligibility. QA and AI features need workspace configuration. Contact us to confirm access and commercial scope.

Make your next bug report actionable.

Start with one app and one recorded failure. See the evidence, try the replay, and check your fix before choosing a paid plan.