Features · Monitoring & backups

You can see what it's doing.

Self-hosting is only worth it if you can tell what's happening without SSH-ing into a box at midnight.

What you get without asking

Live logs

What an app is printing right now, in the dashboard. No SSH session, no docker logs, no guessing which container.

Health, watched

Every app checked continuously. An email when one stops answering, and another when it comes back, so silence means everything is fine.

Backups on a schedule

Dumps of every app database and the platform's own state, kept on your disk for as long as you choose.

History

Every build, kept with its log.

Deploy history does not evaporate. Weeks after a build broke you can still open it and read exactly what the installer said. That is the difference between diagnosing a problem and reproducing it.

The same is true of the platform's own events: what was deployed, what changed, who was granted access to what, and when.

Backups and restore →

Every deploy status · commit · full build log

Every app checked continuously · alert on failure

Every night databases + platform state → your disk

What arrives

The email you actually get.

Short, specific, and sent once. A second message follows when the app answers again, so an inbox with nothing in it means everything is running.

inbox

From: Astrodock <noreply@yourdomain>
Subject: oncall is not responding

oncall stopped answering its health check
at 03:14 and has failed 3 checks in a row.

  https://oncall.yourdomain
  Last deploy: 2 days ago, succeeded

Logs and history are on the dashboard.

Next Sign-in Real user accounts without writing any auth

Or install Astrodock and try it on a machine you control.