Introduction

What Apperio does

Apperio tells you when your site or app breaks or slows down, what visitors were doing when it happened, and which change caused it. It explains each change in plain English and drafts the bug report for whoever does the fixing.

Most error trackers stop at the error. Apperio also keeps a record of what you shipped: every commit on the branch you deploy from, and every deploy. When a new error appears, it is lined up against that record, so you can see which commit probably caused it and whether your last deploy made things better or worse.

How it fits together

Three things feed a project:

1. The SDK. The apperio package runs in your app. In the browser it reports uncaught errors, page views, slow requests and Web Vitals on its own, and sends anything you log yourself. It works in Node.js too, for logs you send by hand.
2. GitHub. The Apperio GitHub App sends the commits pushed to the branch you link, plus deployments, releases and issue events from that repository.
3. Deploys. Apperio picks up GitHub deployments and releases on its own. If you deploy some other way, one API call from your CI job records the deploy.

What you see in the dashboard

• Issues. Errors grouped by cause, with how often each happened and how many sessions it reached. When a new kind of error appears, the project owner is notified without any setup. See Errors and issues.
• Changes. Every commit and deploy, each commit with a short summary written in plain English. See Commits and summaries.
• Deploy verdicts. An hour after each deploy, Apperio compares the error rate before and after and labels it Improved, Healthy or Degraded. See Deploys and verdicts.
• Likely caused by. For each issue, the recent commits most likely to have caused it, with a one-line reason. See Suspect commits.
• GitHub issues. One click drafts a GitHub issue from the error. Closing that issue on GitHub resolves the error in Apperio. See GitHub issues.
• Session replay (beta). A recording of what a visitor saw and did, with form inputs masked. Off until you turn it on. See Session replay.
• Web Vitals and performance. Page load times, slow requests and Core Web Vitals from real visits. See Performance and Web Vitals.

Getting access

Anyone can sign up. Create an account with your email or GitHub, then create a project from the dashboard. No invite or credit card is needed.

Where to start

1. Quick start: install the SDK and see your first error.
2. Connect GitHub: start the change history.
3. Deploys and verdicts: make sure your deploys are recorded.