Your Bot Deserves a Real Status Page. Here's One That Costs Nothing.

Status pages used to mean signing up for another paid tool. Now your bot can generate its own, live, with zero extra setup.

Your Bot Deserves a Real Status Page. Here's One That Costs Nothing.

There's a specific kind of credibility a status page gives a project — a real one, with uptime history and an incident log, not just "trust me, it's usually fine." For years, getting one meant signing up for a separate service, wiring your bot up to report into it, and paying a monthly fee for the privilege of proving your own bot works. That's no longer necessary.

What a status page actually earns you

When something goes wrong — and eventually, something always does — the difference between "the bot's down again, who knows why" and "here's exactly what happened and when it recovered" is enormous, both for how your users feel about it and for how much you have to explain yourself in a DM. A real status page turns downtime from a mystery into a data point. That's worth having, at any scale.

It's already there. You just haven't looked.

import staypresent

staypresent.run("bot.py")

If you're already using StayPresent, you already have this. A live status page, complete with uptime percentages over 24 hours, 7 days, and 30 days, plus a running incident history — served automatically at /status, with nothing extra installed and nothing extra configured.

Built from data your bot was already generating

This isn't a page bolted on top of your bot reporting into some external service. It's built directly from what StayPresent already tracks internally — every start, every crash, every restart, every recovery. Nothing here is fabricated or estimated. If your bot has been rock solid for a month, the page says so. If it had a rough Tuesday, the page says that too.

Public where it should be, private where it matters

Visitors see what a status page is supposed to show — is it up, has it been reliable, what happened during any recent incident. The deeper technical detail — actual exit codes, a tail of what your bot was logging right before it went down — sits behind a simple admin login, so you get real debugging context without handing raw internals to every random visitor.

A branded page, not a generic one

staypresent.web.status(
    title="My Bot Status",
    copyright="Your Name or Company",
    footer_links=[{"label": "Support", "url": "https://yoursite.com/support"}],
)

Two minutes of setup, and it looks like it belongs to your project — not like a plugin bolted on top of it.

The bar for "looks maintained" just got a lot lower

You don't need a funded team or a monitoring budget to look like you take your project seriously. You need one link you're not embarrassed to share.

pip install staypresent[prod]

/status is already live. Go look.