I’ve been quietly working on something for the past few weeks and it’s finally at a point where I’m not embarrassed to talk about it. It’s called Dime, it tracks your expenses, and it will roast you in Hinglish when you buy overpriced coffee for the fourth time in a week.
That last part is non-negotiable.
What it is
Dime is an AI expense tracker. You type naturally — "grabbed lunch $14", "uber to work $12", "therapy after checking my bank statement $200" — and Gemini figures out the rest. Category, emoji, whether it was a need or a want (it’s usually a want). No dropdowns. No category pickers. No suffering.
It’s a full rewrite of WalletRIP, which I built last year and which… worked, but had problems. We’ll get into that in a separate post. For now: Dime is the version I actually wanted to build the first time.
Live at dime.tgoyal.me. Invite-only for now — which is a polite way of saying it’s mine and I like it that way.
The features
Natural language input is the whole point. Open the app, type what you spent, close the app. That’s it. The AI handles categorization, amount extraction, and the smug little Hinglish comment that appears after every entry. (“Bhai, ek aur coffee? Budget toh dekh.”)
AI insights — on-demand Gemini analysis of your last 30 days. What you spent, where it went, what the pattern looks like. It’s useful in the way that doctor’s advice is useful: accurate, slightly uncomfortable, and easy to ignore.
Monthly roast — hit the button and get a sarcastic performance review of your spending. In Hinglish. This was the first feature I built and the one I use most.
Subscription hunter — pastes through your expense history and finds the recurring charges you forgot you were paying for. I found two.
Quick Add API — this is my favorite part. I said “Hey Siri, log expense” and built a Shortcut that asks what I spent, sends it to the API, and logs it without me ever opening the app. Bearer token auth, no session cookies required.
curl -X POST https://dime.tgoyal.me/api/quick-add \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"text": "coffee at starbucks $5.50"}'
Bulk import — paste a bank statement, Gemini parses the whole thing at once. Preview what it found, deselect anything that’s wrong, confirm. Useful when you’ve been ignoring your finances for three weeks and need to catch up.
Spending charts — Needs vs Wants donut + weekly/monthly stacked bar trends. The bar chart is the one that actually changes behavior. Seeing that “Wants” stacked up taller than “Needs” for three consecutive weeks in a row is a specific kind of motivating.
CSV export, streak tracking, dark/light theme. The full stack: Next.js 16 on Cloudflare Workers (via @opennextjs/cloudflare), Supabase for auth and data, Gemini 2.5 Flash-Lite for the AI bits, Upstash Redis for rate limiting that actually works across serverless instances.
The design
Neon Midnight. #0d0d0d background, #00ff88 accent, Syne for headings, JetBrains Mono for the body. The vibe is “developer tool at 2am” which is fitting because that’s when I use it most.
It has a dark/light toggle. The light mode is clean but the dark mode is the one I designed for. I wrote about building a proper design system for this kind of thing in the Chibi post — Dime predates that system, but it shares the same philosophy: one accent color, used sparingly, on the one thing that matters most.
What’s missing (and what’s coming)
There’s a PATCH endpoint for editing expenses that has no UI. Every time I log something wrong I have to delete it and re-add it. This bothers me more than I expected.
Budget goals are the obvious next thing. Set a monthly limit per category, get a warning when you’re close, ignore the warning, feel bad, repeat. The database is set up for it. The UI isn’t.
Multi-currency is on the list. Right now everything converts to CAD which works for me but would confuse literally everyone else.
There’s a field in the schema called is_recurring that doesn’t do anything yet. The subscription hunter identifies recurring charges but doesn’t actually flag them in the database. That’s a gap.
Shared expenses — split tracking, IOUs, the “you still owe me $14 from that lunch” conversation — is the kind of feature that sounds simple and is not simple. Probably v2 territory.
The thing about WalletRIP
I’ll write a proper post about this separately, but the short version: WalletRIP was fine as a first pass and not fine as something I wanted running in production. Client-side database writes, in-memory rate limiting that reset on every cold start, some security choices that made me wince when I looked at them later. Dime fixes all of that. Every mutation goes through server API routes. Rate limiting is persistent across Workers isolates. Input validation runs server-side on every request.
The old version is still live at wallet.tgoyal.me, untouched, as a monument to what v1 looks like. It’s fine. It works. It’s just not what I’d build today.
Next post: why I built Dime instead of fixing WalletRIP, what the Vercel middleware vulnerability from early 2025 had to do with it, and how much of WalletRIP’s security posture was “it probably won’t matter.” (Spoiler: it probably would have mattered.) · May 2026