Free
Basic checks for side projects.
$0/ month
No charge
Join early access- 5 uptime monitors
- 3-minute check interval
- Email alerts
Papel Monitor, in early access
Know your app is down before your customers tell you.
Papel Monitor checks your sites and APIs from several regions, groups errors from your code, pages the right person and keeps a public status page up to date.
Use cases
The jobs Papel Monitor is designed to do, and the teams it suits best.
Uptime for a website and app
HTTP and keyword checks from several regions on your marketing site, sign-in page and API, with alerts only once a failure is confirmed.
Scheduled jobs that fail silently
Nightly imports, billing runs and backups ping a heartbeat URL. If one is late, someone hears about it before the morning.
Errors tied to releases
Exceptions from web and mobile apps grouped by cause and tagged by release, so you can see which deploy introduced a problem.
A status page for your customers
B2B customers subscribe to incident updates instead of emailing support to ask whether something is wrong.
What Papel Monitor does
Uptime checks
Multi-region HTTP and TCP checks
Probe endpoints from several regions. A failure is confirmed from a second region before anyone is alerted.
Keyword checks
Assert that a page contains, or doesn't contain, a string, so a 200 response with an error page still counts as down.
Heartbeat monitors
Cron jobs and background workers ping a unique URL. If a ping is late, you get an alert.
Error tracking
SDKs for your stack
Capture exceptions from JavaScript, Node.js, Python, Swift and Kotlin with stack traces and release tags.
Grouped by cause
Similar errors are grouped into one issue with a count, first and last seen, and affected users.
Release tracking
See which deploy introduced an error, and whether a fix actually made it go away.
Status pages
Public status page
Show the state of each component, with uptime history pulled from your monitors.
Subscriptions
Customers subscribe by email or webhook and get notified when you post an incident or maintenance window.
Custom domains
Host the page at status.yourcompany.com with automatic HTTPS, on Business plans.
Alerts and on-call
Slack, SMS and email
Send alerts to the channels your team already watches, with recovery messages when things come back.
On-call schedules
Weekly rotations with overrides for vacations. Alerts go to whoever is on call right now.
Escalation policies
If an alert isn't acknowledged in time, it escalates to the next person or the whole team.
How it works
- 01
Add monitors
Enter the URLs, ports or keywords to check, and the interval. Create heartbeat URLs for your scheduled jobs.
- 02
Install an error SDK
Add the SDK for your language with your project key. Tag events with the release version from your deploy pipeline.
- 03
Set up alerting
Connect Slack, add phone numbers for SMS, and build an on-call schedule with an escalation policy.
- 04
Detect and confirm
When a check fails, a second region re-checks it. Confirmed failures open an incident and page the on-call person.
- 05
Communicate and resolve
Post an update to your status page so subscribers are notified. When checks recover, the incident closes with a timeline.
Architecture overview
How a failure becomes an alert and a status update. Signals come from your systems; Papel Monitor confirms them before anyone is paged.
Step 1: Your systems
Sites and APIs
Probed over HTTP, TCP or keyword checks.
Scheduled jobs
Ping a unique heartbeat URL on each run.
Your code
Error SDKs send exceptions with release tags.
Step 2: Papel Monitor
Multi-region checks
A failure is re-checked from a second region before an incident opens.
Error grouping
Similar errors combined into one issue with counts and affected users.
Incidents
A timeline from first failure to recovery.
Step 3: Alerting
On-call schedule
The alert goes to whoever is on call now.
Escalation
Unacknowledged alerts move to the next person.
Channels
Slack, SMS, email and webhooks.
Step 4: Your customers
Status page
Component status and uptime history.
Subscribers
Email or webhook notifications for incidents and maintenance.
SDKs strip common sensitive fields, such as passwords and authorization headers, before events leave your app.
Status pages are served from Papel Monitor, not from your own infrastructure, so they stay reachable when your app is down.
Error events are kept for 30 days on Team and 90 days on Business, then deleted.
Admin and controls
What the people who own Papel Monitor in your company can configure, review and restrict.
- Roles
- Admin and member roles, so engineers can acknowledge alerts while only admins change alerting and billing.
- On-call schedules
- Weekly rotations with overrides for vacations and swaps, visible to the whole team.
- Escalation policies
- How long to wait for an acknowledgement and who is next, set per service.
- Check regions and thresholds
- Choose which regions check each monitor and how many consecutive failures open an incident.
- Data scrubbing rules
- Add your own field names to the list SDKs remove before sending events.
- Status page settings
- Components, branding, custom domain on Business, and who can post incident updates.
- Maintenance windows
- Announce planned work to subscribers and pause alerts for the affected monitors.
- Usage against quota
- Error events used this month, with an email before you reach your plan's limit.
Integrations
| Service | What it does |
|---|---|
| Slack | Alerts, acknowledgements and recoveries |
| SMS and email | Direct alerts to the on-call person |
| Webhooks | Send incidents to any system |
| JavaScript and Node.js | Error tracking SDK |
| Python | Error tracking SDK |
| Swift and Kotlin | Mobile crash and error SDKs |
| GitHub | Link errors to releases and commits |
| Papel Cloud | Monitors created for each deployed app |
Security and data
Data scrubbing
SDKs strip common sensitive fields such as passwords, card numbers and authorization headers before events leave your app.
Retention limits
Error events are kept for 30 days on Team and 90 days on Business, then deleted.
Encryption
Event data is encrypted in transit with TLS and at rest on AWS.
Access control
Invite teammates with admin or member roles. Status page subscribers' emails are only used for status notifications.
More detail on our security practices and Privacy Policy.
Papel Monitor plans
Prices in US dollars, billed monthly. You aren't charged during early access until your workspace is live, and you can cancel at the end of any billing period.
Team
RecommendedProduction monitoring for a small team.
$12/ month
Billed monthly
Join early access- 50 uptime monitors
- 30-second check interval
- Error tracking, 50k events / month
- 1 public status page
- Slack and SMS alerts
Business
Multiple products and on-call rotations.
$39/ month
Billed monthly
Join early access- 250 uptime monitors
- Error tracking, 500k events / month
- 5 status pages with custom domains
- On-call schedules and escalation
Limits and fair use
What each plan includes, side by side. Figures match our pricing page; if anything here and your order form differ, the order form applies.
| Limit | Free$0 per month | Team$12 per month | Business$39 per month |
|---|---|---|---|
| Uptime monitors | 5 | 50 | 250 |
| Fastest check interval | 3 minutes | 30 seconds | 30 seconds |
| Error events per month | Not included | 50,000 | 500,000 |
| Error event retention | Not included | 30 days | 90 days |
| Status pages | Not included | 1 | 5, with custom domains |
| Alert channels | Slack, SMS and email | Slack, SMS and email | |
| On-call schedules and escalation | Not included | Not included | Included |
Fair use
- If you exceed your monthly error events, new events are sampled for the rest of the month rather than dropped entirely, and we email you before that happens. Uptime checks are never affected.
- SMS alerts to US and Canadian numbers are included on Team and Business plans. Other countries may be limited during early access.
- Only monitor endpoints you own or are authorized to test. Checks aren't a load-testing tool.
- Status page subscriber emails are used only for status notifications.
See also our Acceptable Use Policy and Service Level Agreement.
Roadmap during early access
Work we plan or are exploring, in no particular order. We don't promise dates: priorities follow what early-access customers ask for, and plans can change.
- Planned
Certificate and domain expiry checks
Warnings before TLS certificates or domain registrations expire.
- Planned
Incident write-up templates
A structured write-up attached to each incident, with the timeline filled in from monitoring data.
- Planned
More check regions
Probe locations beyond North America and Europe.
- Planned
Microsoft Teams alerts
Alerts, acknowledgements and recoveries in Teams channels, alongside Slack.
- Exploring
Performance tracing
Timing for slow requests and database queries, linked to the errors they cause.
Questions about Papel Monitor
Where do checks run from?
From several AWS regions in North America and Europe. You choose which regions check each monitor.
How do you avoid false alarms?
A failed check is retried from a different region before an incident opens. You can also require several consecutive failures.
What happens if we exceed our error event quota?
New events are sampled for the rest of the month rather than dropped entirely, and we email you before that happens. Uptime checks are never affected.
Does SMS cost extra?
SMS alerts to US and Canadian numbers are included on Team and Business plans. Other countries may be limited during early access.
Is Papel Monitor included in development plans?
Yes. Growth and Scale development plans include monitoring for the apps we build and host for you.
Can we monitor endpoints behind a firewall?
Yes, if you allow traffic from our check locations. We'll share the current list of source addresses during onboarding.
Does the status page stay up if our app is down?
Yes. Status pages are served from Papel Monitor, separate from your infrastructure, so customers can still reach them during an outage.
Can we move from another monitoring tool?
Yes. During onboarding we help you recreate your checks, alert routes and status page components, and you can run both in parallel until you're confident.
Get early access to Papel Monitor.
Tell us about your app and we'll set up your workspace with you. Billing starts when it's live.