Catch a bad rollout in minutes
Installs, failed attempts, adoption, and success rate update every few minutes for the release that is live right now.
Capgo Observe, beta
Know when a release needs attention.
See what changed after your rollout, compare health by reported version, and move from a bad signal to the devices and logs behind it.
14-day unlimited free trial. No credit card required 14-day money-back guarantee. Cancel anytime.
-
01
Deploy Mark the version, channel, and deployment date.
-
02
Observe Compare reported health before support tickets arrive.
-
03
Investigate Follow the trend into errors, versions, and devices.
Watch a release land, minute by minute
The moment a bundle goes live, Observe tracks installs, failed attempts, adoption, and success rate for that exact version and channel in 5-minute buckets.
- Know within minutes whether a rollout is healthy, not after support tickets
- Top failure reasons ranked for the release that is live right now
- Jump from the release to its bundle or channel statistics
See which update failures actually matter
Failed downloads, checksum mismatches, unzip errors, and rollbacks are grouped by cause, so you can tell a flaky network from a broken bundle.
- Every failure tagged as network or device, bundle, or rollback
- Daily trend per failure type for the selected period
- Top affected versions and devices, one click from their logs
Compare app health by version, not by guesswork
Launch time, WebView load time, crashes, ANRs, and JavaScript errors reported by the Capgo updater, broken down by version, platform, and channel.
- Launch P90 and WebView P90 for every reported version
- Spot the release that introduced a regression
- Signals come from the updater plugin you already ship
Know when an update needs a new native build
When a channel serves a bundle whose native packages differ from what installed apps were built with, Observe flags it, names the blocking packages, and links the dependency diff.
- Catch a native mismatch before it reaches devices
- Accept the change or roll the channel back from the same screen
- A full history of every compatibility decision
See which updater versions your users really run
Updater plugin versions across production devices, grouped by Capacitor major, with the exact install command for the version to move to.
- Devices behind the latest updater for their Capacitor major
- Plan native releases with real fleet data
- A clear reminder that plugin upgrades ship through the stores
Follow any signal down to the device
Every updater and app event with its device ID, version, and error details attached. Filter by action, time range, or device, then export to CSV.
- Error messages and status codes stay attached to each event
- Filter by action, device, or time window
- CSV export for support tickets and post-mortems
Stop treating production as a black box
Your rollout is only done when you know what happened next.
Observe gives every release a health view, then gives you the evidence to decide what deserves action.
Stop shipping native mismatches
Observe flags bundles that need native packages the installed app does not have, before they reach more devices.
Follow the evidence in Logs
Use grouped failures, affected versions, devices, and action logs to investigate a trend.
See the release, not just the metric
Start broad. Narrow fast. Know where to look next.
Read all-version health, compare the versions that diverge, and use the release marker to connect the change to the impact.
Explore Live UpdatesAll versions summary
Read issue-free devices, native issues, launch P90, and WebView P90 before narrowing your investigation.
Version breakdown
Compare reported app versions when health or timing differs from the overall picture.
Action breakdown
Separate launches, WebView loads, native issues, and update activity while you investigate a trend in Logs Insights.
From signal to evidence
Do not hand your team a chart. Hand them the trail.
Observe
See which reported version changed the release picture.
Compare health and timing with the context of what you deployed, where, and when.
Logs Insights
Identify the errors, versions, and devices behind the trend.
Use Logs Insights to group errors by category, follow the daily trend, and identify affected versions and devices. Then open filtered raw action logs for the details.
Read the Logs guideObserve with AI agents
Ask your agent how the last release is doing
The hosted Capgo MCP server reads Observe, stats, and channel state, so Claude, Codex, or Cursor can answer release-health questions and point to the bundle to roll back.
Try asking your agent
- Which release raised the crash rate?
- Show update failures for the latest bundle by app version
- Roll back the failing channel to the last good bundle
-
CLI
Every release action is a command. Script it in CI or let an agent run it.
npx @capgo/cli@latest bundle upload -
MCP server
Tools for apps, bundles, channels, stats, and native builds, ready for any MCP client.
npx @capgo/cli@latest mcp -
Agent Skills
Teach your agent the right way to add live updates, builds, and Capgo plugins.
npx skills add Cap-go/capgo-skills -
llms.txt
The full Capgo docs in one file, ready to paste into any model.
capgo.app/llms-full.txt
Customer proof
Release teams rely on Capgo in production
Observe runs on the same platform thousands of teams already use to ship live updates.
Being able to add Device ID's to certain groups and push the changes to only certain groups is a life saver.
Getting set up took less than a day. Channel-based rollouts let me test on my own device before anything hits production users.
Observe every rollout
Ship with proof,
not just hope.
Put deployment history, release health, and Logs Insights in one release workflow.
Start Capgo Observe: release health and Logs Insights for every rollout.
human support from Martin
14-day unlimited free trial. No credit card required 14-day money-back guarantee. Cancel anytime.