Status

Is it broken?

Probably not. But here’s the honest answer to how you’d know, and where anything that goes wrong gets written down.

There’s no automated monitoring yet, so this page can’t show you a live green tick. Plenty of status pages do that with nothing behind them — a hardcoded “All systems operational” that would stay green through a total outage. That’s worse than useless: it’s a promise you’d be told, and you wouldn’t be. So instead: the fastest way to know if Sarabellum is down is to open it. If it’s down, tell us — right now, that genuinely is the monitoring.

What could break, and what happens if it does

Sarabellum leans on four services. Here’s what you’d actually see.

Hosting (Vercel)

If this is down, so is everything — the site and the app. Rare, and not something we can fix from here; it recovers when they recover.

Database & login (Supabase)

The app loads but your data doesn’t, or sign-in fails. Nothing is lost — it’s all still sitting in the database on the other side of the outage.

Sara (Anthropic)

Sara goes quiet or errors. Everything else — tasks, dump, timer, journal — carries on completely unaffected. She’s a passenger, not the engine.

Discord

Nudges don’t arrive and slash commands fail. The app itself doesn’t care in the slightest.

Incident log

Anything that goes properly wrong gets written up here: what broke, for how long, and what was done about it. Starting from today, honestly, at zero.

Empty

No incidents recorded yet — it’s a new log. When something breaks, it gets written up here.

Planned work

This is a beta built by one person, so things change under you sometimes. Anything with real disruption attached would be announced in advance — on the newsletter and here.

Something wrong right now?

Tell us, or email aolsendev@gmail.com. What you were doing, what happened, roughly when. You’re not bothering anyone — you’re currently the alerting system, and that’s said with real gratitude rather than as a joke.