Firebase powers a real ERP.
And not some toy app — this one’s chasing enterprise dollars with taxes, invoices, and AI baked in.
Frihet’s architect, a lone coder, picked React 18, TypeScript, Vite on the front. Tailwind, shadcn/ui, Radix for looks. Firebase everywhere else: auth, Firestore, Functions, Storage. Stripe for cash flow. Vercel up front, GCP behind. Capacitor for mobile. Google Gemini for smarts. He shipped in under three months, 17 languages, 41 integrations. Solo. Competing with million-dollar machines.
Market fact: indie devs snag 15% of SaaS startups now, per Crunchbase data. Speed wins. But ERPs? They’re relational beasts. Firestore’s NoSQL? Ballsy.
Can Firebase Actually Run an ERP?
Short answer — yes, if you’re disciplined.
He isolated tenants at the database root. Security rules lock it down; bugs can’t leak data across workspaces. Denormalize reads — client names inline on invoices, no extra fetches. Writes reference the source. Complex stuff? Cloud Functions mimic joins, aggregates. Works for 80% of ops. The rest? Sweatier than Postgres.
Tradeoff screams vendor lock. Firestore queries ain’t SQL. Scaling hits Google’s bill. But zero ops: no clusters, no migrations. That’s solo dev gold. Costs scale to zero on Functions. Auth’s plug-and-play — email, Google, GitHub, Microsoft.
Realtime sync? Firestore’s killer app. Data flips, UIs update everywhere. No polling hell.
Here’s his data flow, crystal clear:
User action → hook → Firestore write → onSnapshot → React re-render
No Redux. No Zustand. Firestore is state. Optimistic updates bridge lag. Bugs like stale caches? Vanished. Database rules all.
And taxes — Spain’s VAT mess (21%, 10%, 4%), Canary IGIC, freelancer IRPF. One rounding slip? Audit nightmare.
He centralized it. Single calculateTotal engine. Fix once, ripples everywhere: invoices, quotes, expenses.
import { calculateTotal } from '@/lib/calculations';
const result = calculateTotal(lineItems, { taxType, withholding });
That’s surgical. Components stay dumb.
Why Skip Redux? Firestore’s the New State King
State management’s a vampire — sucks dev hours.
This stack kills it. Hook fires write. Listener catches confirm. Re-render. Done. Optimism fakes speed. Persisted data lands fresh.
Lighthouse scores: 100s across board. FCP under a second. Builds in 10s. Lazy everything — routes, AI on demand.
AI’s no gimmick. Gemini 2.5 Flash/Pro. Function calling, typed. create_invoice({ clientId, items, taxRate }). No fuzzy RAG hallucinations. Lazy loads on hover. Injects real context: your clients, invoices, taxes. Permissions mirror UI — can’t touch what you can’t see.
Payments? Stripe Billing + Connect. Hosting split: Vercel frontend zippy, GCP Functions backend.
Mobile? Capacitor — one codebase, iOS/Android.
Localization? 240K translation memory. AI fills 2.2% gaps. Cost plunged 91%. CI blocks unlocalized commits. 17 langs in sync.
The Solo Edge — And Hidden Traps
Numbers don’t lie. He shipped what teams grind years on. Firebase freed him from infra jail. No DevOps tax.
But here’s my take — unique angle: this mirrors Basecamp’s 2004 Rails pivot. Simple stack, ship fast, iterate. They dodged enterprise bloat, built a $100M biz. Frihet could echo that if it hooks SMBs tired of SAP/Odoo giants.
Critique the hype, though. Firestore shines early. Reporting? Cross-queries? You’ll export to BigQuery or bolt Postgres later. Vendor lock bites on exit. Solo win now — team scale? Re-arch inevitable.
Prediction: 2025 sees Firebase ERPs spike among indies. Market: ERP SaaS hits $50B by 2027 (Gartner). Speed-first stacks grab the fringe, then consolidate.
Performance obsession paid. Vite’s HMR flies. Shadcn/Radix: accessible, customizable. No bloat.
Is this blueprint? For solos, hell yes. Teams? Weigh lock-in vs velocity.
He nails it: “The architecture you can ship with is better than”
—the perfect one in your head.
Why Does React + Firebase Beat Traditional Stacks for Indies?
Velocity math: Firebase ops = 0. Traditional backend? 40% time sunk (his estimate).
ERP needs: multi-tenant, realtime collab, taxes ironclad. Firestore checks realtime, rules handle tenants. Centralized calc owns taxes.
Downsides real. NoSQL modeling discipline or chaos. 20% queries hurt. But 80/20 rules startups.
AI integration smoothly — functions on live data. Not chat fluff.
🧬 Related Insights
- Read more: CodeRabbit Just Shredded My Messy Pull Request — And Changed How I Code Forever
- Read more: Docker Sandboxes: The Force Field Letting AI Agents Run Wild Safely
Frequently Asked Questions
Is Firebase suitable for production ERP systems?
Yes for solos shipping MVPs — realtime, zero ops. But plan for reporting limits and lock-in.
Why use React with Firebase for state management?
Firestore as source of truth kills sync bugs. No Redux needed; hooks + snapshots handle it.
Can a solo dev build a full ERP stack?
Absolutely — this one proves it: 17 langs, AI, payments in 3 months.
