nachtli

In development · macOS first

Know when it breaks before your users do.

nachtli lives in your menu bar and watches the health of your builds and your production: CI, deploys, uptime, errors, certificates. One icon, one glance.

Not released yet. Linux and Windows are planned.

Built for the person who ships the thing

If you run an app on a handful of services, there is no single place that says everything is fine. nachtli is that place, and nothing more.

  • One section per app

    Group the build, the deploy, the health check and the error feed under the app they belong to. The worst thing is always at the top, so one look is enough.

  • Quiet until it matters

    nachtli alerts once, after two failed checks in a row, and tells you when it recovers. Slow things like certificates and domains are checked on their own slow schedule instead of every minute.

  • Your tokens stay yours

    Tokens are kept in the system Keychain, and read-only scopes are enough. nachtli talks straight to each service. There is no nachtli server in between, and no nachtli account.

What it watches

More than twenty services today, each added with a token you paste once. nachtli finds the organization or project for you, so there is no ID to type.

Builds and deploys

  • Buildkite
  • GitHub Actions
  • GitLab CI
  • Bitbucket Pipelines
  • Jenkins
  • Railway
  • Netlify
  • Vercel
  • Cloudflare Pages
  • Render
  • Fly.io
  • Expo EAS

Errors, uptime and analytics

  • Sentry
  • PostHog
  • Better Stack
  • UptimeRobot
  • Checkly

Data and payments

  • Supabase
  • Neon
  • Stripe webhooks
  • Postmark
  • Resend

App stores

  • App Store Connect
  • Google Play

No account needed

  • A URL
  • Certificate expiry
  • Domain expiry
  • A TCP port
  • A DNS name

Health, not an inbox. No pull requests, no issue lists, no revenue charts. Other tools do those better. nachtli answers one question: is it working?

Local by design

nachtli is a desktop app, not a service. It polls from your machine, keeps its settings in a file you can read, and keeps your tokens in the operating system's Keychain.

  • No backend. Requests go from your computer to the provider and nowhere else.
  • Read-only access. Every provider screen says which scopes to grant, and none needs write access.
  • Encrypted only. Hosts must use https. Plain http is accepted for a server on your own machine.