Unified developer dashboardSee your whole stack on one screen.

How’s the Stack is a unified developer dashboard. It brings the services behind your products into one place, so you can see your code, infrastructure, data and revenue without switching between dashboards.

Get startedSee how it works
howsthestack.com/overview
Sample data

A demo of the dashboard with sample data. It tours the Overview and the GitHub, Cloudflare, Supabase, Stripe pages. Use the button in the top bar to pause the tour and explore it yourself.

Connect the tools
behind your products.

Bring the services you rely on together in one dashboard.

Supported today

  • GitHub

  • Cloudflare

  • Supabase

  • Stripe

More over timeEverything above can be connected now. Anything else is not available yet.

Many services in. One view out.

Each service keeps its own data. How’s the Stack reads what you allow and brings it together, and the view stays the same as you connect more.

Everything you need to understand your stack.

Whatever you connect, the dashboard answers three questions. Each integration adds what it can.

  • Code, deployment, payment and project events together
  • A clear source and timestamp on every event
  • A feed that works with one integration or many

Fed byGitHubCloudflareSupabaseStripe

Recent activity

All services · sample data

  • Commit pushed to main

    fix: harden workflow badge when zero runs

    2m

  • Pull request merged

    #209 chore: bump deps

    5m

  • Route updated

    api.example.com/*

    8m

  • Charge failed

    card_declined · Team plan

    11m

  • Migration applied

    add_profiles_table

    26m

  • New subscription

    Team plan · $29 / month

    41m

  • Worker deployed

    api-gateway · v48

    2h

  • Release published

    v2.8.0

    3h

  • Database backup completed

    acme-prod · daily

    5h

  • Workflow run succeeded

    CI · main · #418

    6h

  • Invoice paid

    INV-1042 · $29.00

    8h

  • Worker deployed

    image-resizer · v12

    1d

3 of 4 services healthy

  • GitHub

    @acme · 3 repos · Synced 2m ago

    Healthy

  • Cloudflare

    Acme · 2 Workers · Synced 4m ago

    Needs a look

  • Supabase

    acme-prod · Synced 6m ago

    Healthy

  • Stripe

    Acme · Live mode · Synced 1m ago

    Healthy

Needs attention · 2

Worker error rate above baselineHigh · 4.2% error rate
2 failed payments need follow-upMedium · This week

Commits

142

14%vs previous 7 days

Requests

1.3M

6.8%vs previous 7 days

Sign-ins

168

9%vs previous 7 days

Revenue

$8,920

11.2%vs previous 7 days

Trend

7 days

Usage against plan

Cloudflare · Monthly requests1.3M / 10M
Supabase · Database size68 MB / 500 MB

Example view · sample data

From sign-in
to your whole stack.

Three steps, and nothing to install.

  1. Continue with GoogleSigned in as you@studio.dev

    Step 1

    Sign in.

    Use your Google account. There is no password to create.

    • GitHubConnected
    • CloudflareConnected
    • SupabaseConnected
    • StripeConnected

    Step 2

    Connect your tools.

    Approve access with each service’s own sign-in, or paste an API key where that is how it works. Nothing to install.

  3. Cloudflare · api-workerResolved

    Error rate back to 0.1%

    GitHubCI passed on main
    StripePayment of $49 received

    Step 3

    See your stack together.

    One overview of what is healthy, what changed and what needs a look.

Your connections. Your control.

Understand what you connect, what information is accessed, and how your credentials are handled.

  • Transparent access

    Every integration has its own authorization requirements, and some services only offer permissions broader than reading. We publish exactly what each one requests, and what we do with it.

  • Protected credentials

    Access tokens and API keys are encrypted with AES-256-GCM before they are stored. They are decrypted only on our server to make requests, and never sent to your browser.

  • You’re in control

    Choose which services and resources appear on Overview. Disconnect any integration at any time and its stored credential is deleted.

Want the technical detail? See what each integration requests

One dashboard for your entire stack.

Start free and upgrade as your stack grows.

Free

$0

Forever free

  • Connect up to 2 unique integrations for the lifetime of your account*
  • Unified dashboard
  • Individual integration dashboards
  • Key metrics, usage and activity
  • Automatic background synchronization
  • Last 24 hours of data history
Get started

Pro

$9.99/month

Everything in Free, plus

  • Connect all currently supported integrations
  • Connect multiple accounts and resources
  • Today, Last 7 days and Last 30 days filters
  • Historical charts and trends

*Free includes two unique integration types for the lifetime of your account: disconnecting one does not restore a slot, but reconnecting a previously connected one is allowed.

Your whole stack.
One calm screen.

Connect the developer tools you already use. How’s the Stack only sends them read requests.

Get startedSee the dashboard

Questions, answered.

What people usually ask before connecting their stack.

  • A unified dashboard for your developer stack. Connect the tools behind your products and see development, infrastructure, data and business information from all of them on one screen, instead of switching between each service’s own dashboard.

  • Indie hackers, solo founders and small SaaS teams whose product runs across several services and who want one place to check on all of it.

  • Today you can connect GitHub, Cloudflare, Supabase and Stripe. Those are the only integrations available right now.

  • The product is built to grow, and integrations are added over time based on what developers need. Anything not listed under Supported today cannot be connected yet, and there is no commitment to a specific service or date.

  • It depends on the integration. Today that covers repositories and CI, Workers and deployments, database and project health, and payments and subscriptions. Each connected service adds its own view, and the Overview brings the most important details together.

  • Each integration connects in the way that service supports. Most use the service’s own sign-in, where you approve access and come straight back. Others ask for an API key; a restricted key with Read permissions is recommended. Then you choose what to watch, such as which repositories or Workers.

  • The app only ever sends read requests. Some permissions are broader than that, though: a service may only offer a scope that bundles write access with read access, and a secret API key can do more than a restricted one. The permissions page lists exactly what each connection requests, and whether it can write.

  • Access tokens and API keys are encrypted (AES-256-GCM) and only decrypted on our server to make requests. Fetched data is cached briefly so the dashboard loads quickly. Disconnecting deletes the stored credential. The privacy policy has the details.

  • Yes. Within each integration you choose what to watch, for example up to 10 repositories or up to 10 Workers at once. Supabase shows one project at a time, and you can switch between the projects in your organization.

  • You will see it. The Overview shows how old each service’s data is, and expired sign-ins or failed syncs appear under Needs attention with a way to reconnect or retry. The last good data stays visible, with when it was last synced.