Built for the developer running everything alone.
dev-views started as a personal frustration and turned into a product.
Managing a modern production stack means juggling a lot of services at once. GitHub for code, Vercel for deployments, Supabase for the database, Stripe for billing, Sentry for errors, Linear for issues. Each one has its own dashboard, its own login, its own notification system.
The problem is not that these services are bad — most of them are excellent. The problem is that there is no shared surface. Every morning starts with opening a dozen browser tabs to answer one question: is everything okay?
dev-views is the answer to that question. One screen, pulling live data from every service your stack depends on. Not replacing any of them — just aggregating the signal that matters.
It is intentionally read-only. The goal is not to control your infrastructure from one place; it is to understand it. That constraint makes it safe to connect, quick to set up, and useful immediately.
Design Principles
Read-only, always
dev-views never writes to your services. No mutations, no side effects, no risk. You connect once with minimal read scopes and get a live view — nothing more.
No agents, no installs
There is no daemon to run, no sidecar to deploy, no code to add to your project. dev-views talks directly to each service's public API. Your infrastructure stays exactly as it is.
Privacy by design
Credentials are encrypted at rest and never appear in logs. No analytics, no third-party tracking. Your data is used to show you your data — nothing else.
Opinionated minimalism
The dashboard shows the metrics that matter for solo developers running production stacks. No configuration, no widget builders. Useful on first load.
Built With
dev-views dev-views is in active development. The dashboard is not publicly available yet. Join the waitlist to get early access when we launch — and to tell us which integrations matter most to you.
Get in Touch
Questions, integration requests, or feedback — reach out directly.