Managed self-hosting for Firebase-compatible backends

What to build

A managed hosting service for Aruma — a clean-room, self-hosted backend that's API-compatible with official Firebase SDKs — targeted at indie developers and small teams who want to migrate off Firebase without rewriting their client code.

Aruma lets developers point unmodified Firebase SDK code at a self-hosted backend instead of Google's infrastructure, opening a packaging opportunity: sell managed deployments and migration tooling to teams trying to exit Firebase's billing and lock-in.

Demand

Indie and small-team developers who've been burned by Firebase's unpredictable billing or lock-in are the likely buyers, and the Show HN post signals the project exists now and is gaining early visibility among exactly this audience.

• Hacker NewsNews

  Show HN: Aruma – clean-room self-hosted backend for the official Firebase SDKs — 3 points, 1 comments on HN.

Stack

• Aruma (open-source backend)
• Docker / Kubernetes for managed deployments
• Terraform for provisioning customer instances
• Stripe for billing
• Postgres or the underlying DB Aruma wraps
• Grafana/Prometheus for instance monitoring

Solo + AI difficulty

The hard part isn't building a UI — it's operating and keeping pace with Aruma's compatibility against Firebase SDK changes, plus handling multi-tenant deployment, backups, and security hardening for other people's production data; a solo builder with AI could get a basic one-click deploy + billing wrapper to MVP in a few weeks, but ongoing SDK-compatibility maintenance is the real long-term cost, not the initial build.

Entry threshold

The core open-source project already exists, so the work is wrapping it into a hosted or managed offering, writing migration guides, and handling ops; moderate build effort over a few weeks, no licences needed but real infra and reliability work to get right.

Window

6-12 months

Where to find first users

• Hacker News (comment on or follow up to the original Show HN thread)
• r/Firebase and r/webdev
• Indie Hackers
• Firebase migration/complaint threads on Twitter/X and Reddit where developers vent about billing surprises

Counter-signals & risks

• Maintaining full compatibility with evolving, undocumented official Firebase SDK wire protocols is high-effort and may break with future Google SDK updates, creating ongoing maintenance risk for any vendor built on this project.

• Google could change Firebase SDK behavior, add client-side attestation, or pursue legal action over clean-room reverse engineering, undermining long-term viability.

• The target market (indie devs, small teams) may have limited willingness to pay for managed hosting/support, and larger enterprises needing this would likely prefer established alternatives (Supabase, AWS Amplify, or Google's own cost controls) over a niche clean-room clone.