Hello Bello — Ops Handbook

The single source of truth for the services, domains, and infrastructure that keep Hello Bello’s website and backends running — and the runbooks for fixing them when they break.

This exists because our stack grew as a patchwork across several employees and hand-offs. The goal here is that no piece of paid infrastructure is known to only one person, and that when something lapses (a card expires, a domain doesn’t renew, a webhook is missed) anyone on the team can find what it is, who pays for it, where to log in, and how to fix it.

How to use this handbook

• Domains & Registrars — every domain, which registrar holds it, and when it renews. Start here when a domain stops resolving.
• Subscriptions & Vendors — every paid service, its billing owner, the card on file, and renewal cadence. Check this whenever a credit card changes so you can proactively fix auto-renewals before something lapses.
• Infrastructure Map — what runs where (Vercel, Render, AWS, Cloudflare…) and how the pieces connect.
• Access & Ownership — who holds the keys to each account.
• Runbooks — step-by-step fixes for recurring incidents.

Conventions

• 🔒 Never store actual secrets here. This document records where a credential lives (the password manager, the vault, the account), never the credential itself. Even though the site is access-gated, secrets belong in the password manager only.
• ⚠️ VERIFY marks a value that was inferred or carried over and has not been confirmed by a human yet. Treat it as a lead, not a fact. Remove the marker once verified.
• TODO marks a field nobody has filled in. Filling these in is the ongoing work.
• Put a Last verified: YYYY-MM-DD note on rows you confirm, so staleness is visible.