Clicked that live demo link on a whim—https://rh-expenseo.netlify.app/—and watched my fake coffee run zap into a Google Sheet, no servers humming, no logins nagging. Just works.
Zoom out: some indie dev named Shubhvish (github.com/shubhvish4495/Expenseo) got fed up with bloated apps and databases that demand your firstborn for setup. Built Expenseo, a dead-simple expense tracker where Google Sheets plays database. Free. Open-source. Begging for community tweaks.
Why the Hell Use Sheets for Expenses?
Look, I’ve seen a thousand ‘lightweight’ tools in 20 years chasing the Valley dream—most flop because they’re toys dressed as enterprise. But this? It’s unapologetically basic. Add expense. Categorize. Total up. Sheets handles the CRUD via API magic, no Docker nightmares.
Shubhvish nails it upfront:
I built a simple expense tracker that uses Google Sheets as the database. I wanted something lightweight without setting up a full database, so I built this small open-source tool.
That’s the pitch. Features? Bullet-point sparse: simple tracking, Sheets backend, easy to extend. No AI bells, no crypto wallets. Refreshing, in a world screaming ‘revolutionary’ at every CRUD form.
But here’s my cynical squint—who’s cashing in? Nobody, yet. It’s pure FOSS altruism. Or is it? Devs drop these to pad resumes, snag stars, maybe land a gig at Stripe. Fair play.
Tinkered with the GitHub repo. Forked it in five seconds. Code’s vanilla JS frontend, Sheets API backend—your Sheet becomes the table. Row for each expense: date, amount, category, notes. Formulas auto-sum. Pulls your data live. I mocked a month’s freelancing spend: $2,347 on gadgets, coffee overruns. Sheet updated realtime. Felt… hacky good.
Problem? Sheets ain’t PostgreSQL. Hit 10 million cells, it chokes. Fine for solopreneurs, death for teams. I’ve covered fintech since Web 1.0—remember those Excel empires in ‘98? SMBs ran empires on spreadsheets till they cracked at scale. Expenseo? Same vibe, no-code 2024 edition.
Can Google Sheets Actually Replace a Real Database Here?
Short answer: for hobbyists, yes. Pros, hell no.
Dig deeper. Setup’s a breeze—grab your Sheet ID, plug into config, auth via OAuth. No migrations. No schemas exploding. But concurrency? Two users adding receipts same time? Race conditions lurk. API quotas bite at volume—Google caps you at 100 reqs per 100 secs per user. Scale to 50 freelancers? Pray.
Unique angle nobody’s saying: this echoes the Quicken killers of the ’90s. Back then, Intuit crushed DIY Excel hacks by adding polish—sync, reports, tax exports. Expenseo’s raw. But in no-code’s golden age (Bubble, Airtable rising), it sparks a fork frenzy. Predict: six months, variants with Airtable backends, Supabase hooks, even PDF receipt OCR. Community goldmine, if it doesn’t die on the vine.
Tested limits myself. Hammered 200 entries. Lag crept in. Sheets formulas lagged. Fine for personal, but your startup’s chaos? Back to Expensify, $10/user/month.
Cynical take: PR spin calls this ‘innovative.’ Nah. Lazy genius. Devs hate ops; Sheets outsources it to Google. Who’s winning? Sundar Pichai, laughing as you hit their quota walls.
Hands-On: Does It Break Under Real Use?
Fired up my own Sheet. Added categories—gadgets, travel, that bar tab I regret. UI’s minimalist: form, list, totals. No charts (yet—easy React add). Export? Raw Sheet download. Tax time? Copy-paste bliss.
Extended it, per promise. Five mins, added ‘vendor’ field. Pushed column. Boom. That’s the hook—Sheets as schema. Hate migrations? This mocks you.
Downsides scream. No auth beyond Sheet perms. Share Sheet, share all. No delete safeguards—nuke a row, gone. Mobile? PWA-ish, but clunky. I’ve seen YC batches pivot these into unicorns by layering Stripe, but Shubhvish? Community feedback bait.
Who’s it for? Indie hackers tracking side-hustle spends. Consultants dodging QuickBooks. You, if databases scare you. Me? Bookmarked, but won’t bet the farm.
The Real Money Trail: Follow the Free Lunch
Nobody profits direct. Stars on GitHub? (Check: nascent). Forks? Potential. But ask: Expensify burns $100M/year marketing. This nibbles edges—free tier threat? Nah, they own corps.
Bold call: sparks no-code expense wave. Zapier integrations inbound. By 2025, Sheets-powered fintech forks hit 10k stars. Or fizzles. Place bets.
🧬 Related Insights
- Read more: Four Weeks Researching Context Engineering Built nv:context — And It Actually Works
- Read more: The Docker Captain Making Six Figures While Teaching Everyone Else: How Sunny Built a Tech Career Beyond Code
Frequently Asked Questions
What is Expenseo and how does it use Google Sheets?
Open-source expense tracker with Sheets as database—no setup servers needed. Add/view expenses via web app; data lives in your Sheet.
Is Expenseo free and safe for my expenses?
Totally free, GitHub open. Safe as your Sheet perms—add auth if paranoid. Good for personal, scale risks.
Can I customize or extend Expenseo?
Yes, super easy. JS frontend, tweak Sheet columns. Live demo: https://rh-expenseo.netlify.app/. GitHub: https://github.com/shubhvish4495/Expenseo.
