For indie SaaS founders

The operator's view of every product you ship.

You ship across iOS, web, desktop, Chrome extensions, npm. Your operating data lives in seven different vendor dashboards. Greenfield pulls it all into one warm, restrained terminal — GitHub state, Cloudflare deploys, beta signups, customer outreach, license keys, CI failures — and tells you what needs you, today.

BUILT BY AN INDIE FOUNDER · OPEN-SOURCED FRAMEWORK · CLOUDFLARE-NATIVE

2 people are waiting on you.

28 open · 17 active · 8 expired across 4 projects. Three CI workflows are red.

22h
Aaryan jhaa snapbymrjhaa@gmail.com
slipstream · pending · photographer · 1-4TB · Friend
Reply
3h
CI failing on ShotSelect Build and Release · v1.0.13
push to v1.0.13 · failed · last run 3h ago
↗ Triage
11m
ShotSelect license issued lovish@carpm.in
SHOT-BETA-eyJl… · expires 2026-05-15 · active
↗ Email
UNIFIED INBOX

Every person waiting on you, in one feed.

Beta signups, license requests, App Store reviews, support emails — pulled from D1, Resend, App Store Connect RSS, GitHub issues. Pending-first sort, one-click Gmail compose with a draft pre-filled per project.

REAL TIME

What's broken, surfaced loud.

Failing CI runs, slow landing pages, expiring TestFlight builds, OAuth token refresh failures — all banner-up at the top of the dashboard. One click hands the issue off to a Claude session scoped to the right local repo.

PORTABLE

Drop-in projects, drop-in connectors.

One JSON file per project, one .mjs per data source. Add Stripe, RevenueCat, Plausible, Buttondown — anything with an API. The framework is open source; subscribe for the hosted tenant + auto-cron + alerting.

Connectors built in · today

GitHub Cloudflare Pages Cloudflare D1 Cloudflare R2 Resend webhook HTTP probe App Store Connect (RSS + JWT) npm registry Chrome Web Store scrape Slipstream-style D1 forms

Pricing for solo operators.

All plans include the full UI, the connector framework, and the Claude handoff daemon. The difference is automation, scale, and how much we host for you.

Solo

$0/forever

For one project, manual refresh. The free framework you already see.

  • 1 project
  • All connectors, locally run
  • Unlimited beta signups + license keys
  • Cmd+K palette · Claude handoff
  • No hosted refresh
  • No alerting
  • Self-host on your own Cloudflare
Clone the repo →

Studio

$79/month

For indie studios with portfolios. Multi-operator + agency-grade.

  • Unlimited projects
  • Up to 5 team members with role split
  • White-label option (your wordmark)
  • Webhook ingestion (Stripe, RevenueCat, Linear)
  • Per-project public status pages
  • 1-year history retention
  • Priority support · roadmap input
Talk to us

Common questions.

Is this open source or proprietary?
The framework is open source — you can clone the repo and self-host on your own Cloudflare account forever, free. The Pro / Studio tiers are the hosted version: we run the cron, alerting, multi-tenant auth, and time-series storage so you don't have to.
What do I need to bring?
A GitHub account (we connect via OAuth) and your Cloudflare account ID if you want us to query your D1 / R2 / Pages directly. Everything else is configured in the onboarding wizard.
Why Cloudflare-native?
D1 + Pages + Workers Cron is the cheapest, fastest stack for this shape of product. Everything stays at the edge, costs cents. We can ingest data from anywhere, but the dashboard's own infrastructure runs on Cloudflare.
Can I use this with Stripe / RevenueCat / Linear / Plausible?
Stripe and RevenueCat are on the Pro tier roadmap (Q3). Linear, Plausible, Buttondown, and Sentry are connectors you can write yourself today — each is one TypeScript file. We accept community-contributed connectors with PR.
Will it tell me when CI fails on my repos?
Today, yes — the dashboard surfaces failing GitHub Actions runs as red banners and lets you hand off the fix to a Claude session scoped to the right local repo. On Pro, you also get Slack / Discord / email alerts within minutes of the failure.
Can I see who's signed up for my beta?
Yes — that's the central use case. Connect any D1 database with a beta-signup table and the rows render in the unified Outreach inbox with status (pending / approved), context (role, drive size, etc), and a one-click Gmail compose with a project-specific draft email.
Do I need to write any code?
For built-in sources (GitHub, Cloudflare D1, HTTP probes), no. For custom sources (your own database, a third-party API), drop a small .mjs file in the connectors directory — about 30 lines of code per connector.
What about privacy and data?
Your dashboard is private to your tenant. Your beta-signup emails, license keys, and outreach data live in your own Cloudflare D1 — we read it via API token but never copy it to our infrastructure. Cancel anytime; your data stays where it always was.