The Indie Hacker's Ops Stack: What a Solo Founder Actually Has to Track

The myth of the indie hacker is that shipping is the job. It isn't. Shipping is maybe 30% of a working solo SaaS. The other 70% is quietly keeping the ops stack alive — the domain you registered three years ago, the DNS records you set up once, the Stripe webhooks, the email sending reputation, the API keys, the analytics integrations, the privacy page, the renewal on the small app you bought to send transactional email.

The product doesn't go down because your code has a bug. It goes down because the domain expired and nobody was watching. This guide is the stack you're actually running — layer by layer — and the single dashboard that keeps it honest.

The iceberg under your solo SaaS

A typical solo-founder SaaS that makes, say, $3,000 MRR has somewhere between 15 and 30 vendors quietly supporting it. The founder can rattle off five. The rest surface only when something breaks. A short and incomplete list:

• Domain registrar.
• DNS provider (sometimes the same, sometimes not).
• Hosting / platform (Vercel, Fly, Railway, Hetzner).
• Database (Supabase, Neon, Planetscale, Turso).
• Auth (Clerk, Supabase, Auth0, rolled your own).
• Transactional email (Resend, Postmark, SendGrid).
• Marketing email / newsletter.
• Analytics (Plausible, Fathom, Google).
• Error tracking (Sentry, Baselime, Axiom).
• Payments (Stripe, Lemon Squeezy, Paddle).
• Customer support (Intercom, Plain, Crisp, plain email).
• CI / version control (GitHub).
• Storage / CDN (R2, S3, Cloudflare).

Each one is small. Together they run your business. Losing any single one for 48 hours is painful; losing two is a real incident. The point of an ops stack view is to never be surprised.

The seven layers of the indie stack

A useful way to group the iceberg is by layer, from the DNS root down to admin:

1. Domain, DNS, SSL.
2. Hosting and infrastructure.
3. Billing and revenue.
4. Email and deliverability.
5. Auth, keys, and secrets.
6. Analytics and observability.
7. Legal and admin.

Each layer has a small "must track" list. If you track those, the product stays up.

Layer 1 · Domain, DNS, SSL

This is the layer that takes your product off the internet fastest if you neglect it. Track:

• Domain expiry. See the never miss a domain renewal guide. Auto-renew on. Card on file valid. Registrar account email monitored.
• DNS provider. If it's separate from the registrar, note it. An outage at Cloudflare DNS is an outage for you.
• Critical DNS records. Apex A / AAAA, the main CNAME, MX, SPF, DKIM, DMARC. A backup export of these lives in your ops store.
• SSL certificate renewal. If you're on Vercel / Cloudflare this is automatic. If you manage it manually, track the expiry.

Layer 2 · Hosting and infrastructure

Track:

• Hosting platform, plan, billing cadence, renewal cost.
• Database provider and backup policy. When was the last backup verified?
• CDN / object storage provider and account.
• Any background worker or queue provider.

The single highest-leverage habit here: verify your database backup once a quarter. A backup you've never restored is a backup you don't know works.

Layer 3 · Billing and revenue

You need a one-glance read of money in. Track:

• Payment processor (Stripe, LS, Paddle) account status.
• MRR and a rough churn number.
• Failed-charge rate (the single best leading indicator of an integration problem).
• Tax setup — automatic in Stripe, manual in some providers.
• Paid invoices vs. issued, if you invoice separately.

Don't overbuild this. A single metric (MRR, say) plus a weekly glance at failed charges covers most of the real risk.

Layer 4 · Email and deliverability

Email is where a lot of indie SaaS quietly loses revenue — transactional emails land in spam, password resets don't arrive, onboarding sequences are invisible. Track:

• Transactional provider (Resend, Postmark, SendGrid) and plan.
• Sending domain and its SPF / DKIM / DMARC records.
• Bounce rate and spam complaint rate.
• Marketing email vs. transactional email as separate domains or subdomains.

One habit: send yourself a test password reset once a month from a fresh Gmail. If it lands in spam, fix before it becomes a support ticket wave.

Layer 5 · Auth, keys, and secrets

The place most solo founders eventually get burned. Track:

• Every API key in production, where it's stored, and when it was last rotated.
• OAuth apps you've created (Google Cloud, Slack, etc.) and their credentials.
• Third-party accounts with programmatic access to your product.
• 2FA recovery codes for every critical admin account.

A short rule: rotate production keys on a known cadence, even if nothing's wrong — quarterly is reasonable. Stale keys are the ones that get leaked into GitHub by a future contractor.

Layer 6 · Analytics and observability

You don't need elaborate dashboards. You need three kinds of signal:

• Usage. Plausible, Fathom, or equivalent. You want to notice if traffic drops overnight.
• Errors. Sentry or similar. You want to notice if error rate spikes before a customer tells you.
• Uptime. A simple ping from UptimeRobot / Better Uptime pointed at your apex and one deep endpoint. Outages you hear about from Twitter are not fun.

More than this is optimization; less than this is negligence.

Layer 7 · Legal and admin

Not glamorous, but surprisingly important. Track:

• Business entity (if any), registration jurisdiction, renewal dates.
• Privacy policy and terms of service and when they were last updated.
• Data processing agreements with vendors you depend on.
• Accountant, tax deadlines, VAT / sales-tax setup.

A running note of the above turns your next accountant conversation from an hour-long dig into a ten-minute handoff.

The single ops dashboard

Done well, everything above fits on one screen. Not a "dashboard" in the enterprise-tool sense — a simple list of tiles, each one showing the current state of a thing that could blow up:

• Domain renewing in 47 days, auto-renew on.
• MRR, trending up or flat.
• Hosting plan and next renewal.
• Transactional email bounce rate this week.
• API keys not rotated in > 90 days.
• Outstanding incidents / errors.

When the ops dashboard is one glance, nothing sneaks up on you. The product goes down from genuine bugs, not from quiet infrastructure rot.

Livdock is built for exactly this layer — a calm, item-typed inventory for the operational tail of your business. If you want a single place for your domains, hosting plans, subscriptions, keys, and renewals, alongside a daily Today view of what actually needs attention, create a free account and spend one focused hour adding your ops stack. The compounding effect is immediate.