> **Stacked on #696.** That PR introduced the AI-categorization upgrade dialog this one generalizes. It targets `main` so CI runs, so until #696 merges this PR's diff also contains #696's commit — review/merge #696 first, then this diff resolves to just its own three commits. ## What & why The contextual "this is a paid feature → pick a plan → checkout" modal built for AI categorization is now a **shared component** reused at two more Pro-feature entry points, and every checkout it starts is **attributed to the upsell point** so we can measure revenue per point. ### 1. Reusable upgrade modal Extracted `AiUpgradeDialog` (+ `PlanCard`) out of `settings/billing.tsx` into a shared `UpgradeDialog` (`resources/js/components/subscription/upgrade-dialog.tsx`). It reads `pricing`/`locale` from `usePage`, takes `title` / `description` / `source`, renders the plan picker, and links to Stripe checkout. Used at: | Point | Trigger | Copy | |---|---|---| | AI categorization | Manage Plan toggle (unchanged) | "AI categorization is a paid feature" | | **Connections** | "Connect Bank" | "Bank connections are a paid feature" | | **Connected accounts** | Create Account → "Connected" | "Connected accounts are a paid feature" | Both new points already gated on `isFreePlan`, so the modal only shows to free users. The old plain `UpgradeConnectionDialog` (which just routed to billing) is deleted. ### 2. Revenue attribution The upsell `source` is captured two ways: - **Intent** — a PostHog `upgrade_checkout_started` event (`{ source, plan }`) fires on click, matching the repo's existing `{ source }` event convention. - **Revenue** — `source` rides the checkout URL (`?plan=&source=`), and `SubscriptionController::checkout` validates it against the new `App\Enums\UpsellSource` enum and attaches it as Stripe **subscription metadata** (`withMetadata`). When the subscription webhook lands, `PersistUpsellSourceFromStripe` (on Cashier's `WebhookHandled`, so the row already exists) copies it onto a new `subscriptions.upsell_source` column — **write-once** (`whereNull`), so a later `subscription.updated` never overwrites the original attribution. Measuring revenue per point is then a group-by on `subscriptions.upsell_source` joined to invoices, using existing local tooling. ### Scoping notes (from review) - **Paywall & the billing on-page upgrade button are intentionally left untagged** (`upsell_source = NULL`). "Upsell source" means a *feature-gate nudge*; the paywall/billing pages are the baseline upgrade surface, not a nudge — so they form the null/baseline bucket rather than getting their own enum value. - The listener is **synchronous** (not `ShouldQueue` like the sibling Discord listener) on purpose: a single indexed, idempotent `UPDATE` doesn't warrant a queue-worker dependency for attribution. - The PostHog event fires just before a full-page navigation; posthog-js flushes via beacon but the event (analytics only, not the revenue source of truth) could occasionally be lost. Cheap to harden later if the funnel proves lossy. ## Tests - `upgrade-dialog.test.tsx` — renders per-feature copy, checkout link carries `plan` + `source`, click fires the PostHog event. - `SubscriptionTest` — checkout tags valid sources as Stripe metadata and ignores unknown ones. - `PersistUpsellSourceFromStripeTest` — persists from webhook metadata, doesn't overwrite an existing attribution, ignores unknown/absent sources. ## Demo Free user hitting both new upsell points (Connections → "Connect Bank", Accounts → "Connected"): <!-- 📎 PLACEHOLDER: drag in ~/Downloads/upsell-points-connections-accounts.mp4 --> https://github.com/user-attachments/assets/a27435d9-2296-4dc9-ae7f-753b6f7950f0 > Note: the clip ends at the modal (doesn't cross into Stripe) because this local dev env has a pre-existing Stripe tax-rate 500 on `/subscribe/checkout`, unrelated to this change. The `source` reaching the checkout URL is verified in the browser and by the tests. |
||
|---|---|---|
| .agents/skills | ||
| .claude | ||
| .cursor | ||
| .github | ||
| .opencode/skills | ||
| .pi | ||
| app | ||
| bootstrap | ||
| config | ||
| database | ||
| docker | ||
| docs | ||
| experiments | ||
| lang | ||
| public | ||
| resources | ||
| routes | ||
| screenshots | ||
| scripts | ||
| src/lib/crypto | ||
| storage | ||
| templates/coolify | ||
| tests | ||
| .dockerignore | ||
| .editorconfig | ||
| .env.example | ||
| .env.production.example | ||
| .gitattributes | ||
| .gitignore | ||
| .mcp.json | ||
| .php-cs-fixer.dist.php | ||
| .php-version | ||
| .prettierignore | ||
| .prettierrc | ||
| .release-it.json | ||
| AGENTS.md | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| Dockerfile | ||
| Dockerfile.production | ||
| LICENSE.md | ||
| LOCALIZATION.md | ||
| ONBOARDING.md | ||
| README.md | ||
| artisan | ||
| autoresearch-dashboard.md | ||
| autoresearch.jsonl | ||
| autoresearch.md | ||
| autoresearch.sh | ||
| boost.json | ||
| bun.lock | ||
| components.json | ||
| compose.yaml | ||
| composer.json | ||
| composer.lock | ||
| docker-compose.production.yml | ||
| eslint.config.js | ||
| falcode.json | ||
| opencode.json | ||
| package-lock.json | ||
| package.json | ||
| phpstan-baseline.neon | ||
| phpstan.neon | ||
| phpunit.xml | ||
| tsconfig.json | ||
| vite.config.ts | ||
| vitest.config.ts | ||
| vitest.setup.ts | ||
| whispermoney | ||
| worktree.sh | ||
README.md
Deutsch | Español | français | 日本語 | 한국어 | Português | Русский | 中文
Whisper Money
The most secure way to understand your finances.
Whisper Money is a privacy-first personal finance application that helps you track, categorize, and understand your spending—all while keeping your financial data encrypted and secure.
🎮 Try the Demo: Experience Whisper Money with our demo account - no registration required!
💬 Join our Community: Whether you're a user looking for help or a developer wanting to contribute, we'd love to have you in our Discord server! Share feedback, ask questions, discuss new features, or just hang out with fellow privacy enthusiasts.
Features
- 🔐 Privacy-first — Your data is never shared with third parties. You own it
- 🏦 Bank account management — Track multiple accounts in one place
- 📊 Transaction categorization — Automatic and manual categorization
- 🤖 Automation rules — Set up rules to auto-categorize transactions
- 📈 Financial insights — Understand your spending patterns
Tech Stack
- Backend: Laravel 12, PHP 8.4
- Frontend: React 19, Inertia.js v2, TypeScript
- Styling: Tailwind CSS v4
- Database: MySQL
- Cache/Queue: Redis
- Testing: Pest v4
Running Locally
Quick Start (Recommended)
The easiest way to get started is using our automated setup script:
bash <(curl -fsSL https://whisper.money/setup.sh)
After installation, just visit https://whisper.money.localhost in your browser.
Manual Setup
If you prefer to set up manually:
- Clone the repository:
git clone https://github.com/whisper-money/whisper-money.git
cd whisper-money
- Run the setup script:
whispermoney install
Available Commands
Important: You must run
whispermoney installbefore using any other command. If you skip the install step, commands likestartwill not work.
Once installed, you can use the whispermoney command for common tasks:
# Start all services
whispermoney start
# Stop all services
whispermoney stop
# Upgrade to latest version
whispermoney upgrade
# Interactive menu
whispermoney
Development Server
For active development with hot reloading:
composer run dev
This will concurrently start:
- PHP development server (via Portless HTTPS proxy)
- Queue worker
- Log viewer (Pail)
- Vite dev server
The application will be available at https://dev.whisper.money.localhost. In git worktrees, the branch name is automatically prepended (e.g. https://fix-ui.dev.whisper.money.localhost).
Running with Docker (Production Image)
For testing the production Docker image locally:
- Copy the production environment file:
cp .env.production.example .env
- Start the services:
docker compose -f docker-compose.production.yml up -d
The application will be available at http://localhost:8080.
To use a different port, set APP_PORT:
APP_PORT=3000 docker compose -f docker-compose.production.yml up -d
Deploying to Coolify
Whisper Money can be easily deployed to Coolify using our Docker Compose template.
Quick Deploy
- In Coolify, create a new resource and select Docker Compose
- Choose Empty Compose File as the source
- Paste the contents from our template: 👉 whisper-money.yaml
- Deploy!
The template includes:
- Whisper Money application container
- MySQL 8.0 database with health checks
- Persistent volumes for data and storage
- Auto-generated database credentials
Required Environment Variables
| Variable | Description |
|---|---|
RESEND_API_KEY |
Email service API key (for password resets, notifications) |
Note:
APP_KEYandAPP_URLare auto-configured. The container generates anAPP_KEYon first startup if not provided.
Optional Environment Variables
| Variable | Default | Description |
|---|---|---|
DRIP_EMAILS_ENABLED |
true |
Enable drip emails (welcome, onboarding, feedback) |
HIDE_AUTH_BUTTONS |
false |
Hide login/register buttons on landing page |
SUBSCRIPTIONS_ENABLED |
false |
Enable Stripe subscriptions |
STRIPE_KEY |
- | Stripe publishable key |
STRIPE_SECRET |
- | Stripe secret key |
STRIPE_WEBHOOK_SECRET |
- | Stripe webhook signing secret |
Star History
License
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.