n0t1 n0t1
Request access

Monitoring for small teams on Heroku

Know your app is failing before your customer emails you.

n0t1 reads your Heroku logs as they happen. When requests start timing out, crashing or erroring, it sends your phone a few plain sentences: what broke, how badly, and which customer it is hitting. When nothing is wrong, you hear nothing.

Request access

What it watches

Timeouts and crashes

H12 request timeouts, H10 crashes, 5xx bursts and memory overruns. The errors your app never sees, because the router answered for it.

Who it is hitting

Name your API partners by IP or key, and every incident says which one is affected, so you can reach out before they do.

Plain English, not graphs

Each incident comes with a short summary written by Claude from the failing requests and your app's own error lines.

Quiet by design

One notice when it opens, one when it clears. No dashboards to check, no alert storms, nothing on a good day.

Slow before it is broken

Requests creeping toward the 30 second limit get flagged while they still succeed.

Who is in your app

Optional: see when a real customer signs in, the pages they open, and a link to their session replay.

Why it exists

An API partner's requests started timing out one Saturday. Heroku's router answered them with 503s, the app never logged a thing, and the first alert was the partner's email. n0t1 was built that week, and has watched production every day since.

Setup takes five minutes

1. Add a log drain

One heroku drains:add command per app. No agent, no SDK, no code change.

2. Install the app

Add n0t1 to your phone's home screen and turn on notifications.

3. Name your callers

Optional. Label the partners and integrations you care about most.

Request access

n0t1 is in a private beta for teams on Heroku. Tell us about your app and we will get back to you within a day.