Maximilian Kaske

If you're ever looking for status page components, we've published a @shadcn.com component registry built specifically for that.

If you have a website and not using @openstatus.dev speed check you're missing out 🤯

I was able to improve the performance in some regions by up to 150x 🤯

They have an AI skill you can install to let agents check the performance in multiple regions at once.

Link ⬇️

that’s the way

my life in a nutshell rn

yes

One API to Rule Them All: Migrating from zod-openapi to ConnectRPC We're unifying our internal tRPC API and public REST API into a single ConnectRPC service. Here's how we're doing it—and how AI is accelerating the migration.

We are going full connectRPC by @buf.build

www.openstatus.dev/blog/migrati...

time to market it

Introducing Status Page Components A major architectural refactor that decouples status pages from monitors, enabling flexible status reporting and better self-hosting support.

Status pages started simple @openstatus.dev: a page showed the uptime of a monitor. That assumption shaped our entire data model - and eventually became our biggest limitation.

Not anymore.

openstatus.dev/blog/status-...

shipper and sipper

A component form card listing the current status page components. An open dropdown suggests you can connect monitor and static components while third-party components are yet disabled.

its been a long way - we are going to improve the status page experience with page components

do no mistakes

💯

Noticing the same esp for frontend code.

Different story for backend, which can also be more unit tested so ai is less prone.

💯

most people are forced to use it 😂

Openstatus 2025 Year in Review: Lessons Learned and What’s Next As we close out 2025, it’s the perfect time to pause, reflect, and share where we are heading for 2026.

Time to share what we have been through in 2025 and our goals for 2026.

www.openstatus.dev/blog/2026-ro...

logs.run

OpenStatus Template We've created this template to help you get started with your @shadcn/ui project. It uses @nextjs in an SPA mode and can be exported statically (BYO router).

haha yeah - this time it was mainly the migration for our new landing. So lots of copy from template.openstatus.dev/landing

in the meantime

GitHub - openstatusHQ/openstatus-template Contribute to openstatusHQ/openstatus-template development by creating an account on GitHub.

github.com/openstatusHQ...

New open-source dev tools marketing template just dropped:

- content in MDX
- static Next.js export (byo router)
- boring elements (no fancy animations)
- ASCII code snippets
- theme-aware images

template.openstatus.dev/landing

👋

img w/ caption - grid style

You’re a 100x dev or what happened in Bavaria? You’re driving too fast man

What happened? 😭

🔥

screenshot of status page with a single website monitor followed by two grouped monitors for EU and US. The second US group is collapsed.

wip: grouped monitors

themes.openstatus.dev

Introducing: The Status Page Theme Explorer Customize and build your own status page experience.

www.openstatus.dev/blog/introdu...

more images of the supabase theme