OpenProfit

About OpenProfit

Connect Stripe, OpenAI, Vercel and every other bill. See what each of your apps earns after costs, and get the numbers for your tax return.

Revenue lives in your payment processor. Costs live in a dozen billing pages: AI providers, hosting, databases, email, domains. Each shows its own slice, in its own currency. OpenProfit pulls them together and assigns every line to the product it belongs to.

[Overview: revenue, costs, profit, MRR and subscriptions across three products, with a twelve-month chart and breakdowns by product and provider]

Connect your whole stack

Revenue from your payment processor. Costs from your AI providers, hosting and infrastructure. Paste an API key and two years of history fill in.

Measure what you keep

Revenue minus fees, refunds, AI bills and hosting, for every app you run. The number on screen is the one you keep.

• Net of fees and refunds. Processor fees and refunds come off before any number is shown.
• One currency. Paid in euros, billed in dollars. Everything converts at that day's rate.
• Profit per product. Three products on one OpenAI account, and you still see which one pays for itself.

Every bill in one place

OpenAI, Vercel, Neon, Resend and 10 more providers report what they charged you, by day or month and by project. Subscriptions without an API take ten seconds to add.

• Usage billing. Per-token and per-GB charges come from the provider's own billing data.
• Flat subscriptions. Supabase, domains, anything else. Enter the price once and it counts every month.
• Mapped to products. Point each OpenAI or Vercel project at the product it serves. The rest stays under Unassigned until you decide.

Know when something moves

A Monday email with last week's revenue, costs and profit. An alert the day a bill doubles, a margin drops or a sync fails.

• Weekly summary. Three numbers and the one change worth knowing. Free on every plan.
• Spike alerts. An email the day a bill doubles or a margin drops. Slack and Discord next.
• Public pages. Share a product's numbers on a page anyone can open. You choose what shows.

Open source, yours to run

MIT licensed. One Docker image with Postgres inside, or point it at your own. Your API keys never leave your server.

Key features

• Overview with revenue, costs, profit, MRR and customers for any period, deltas against the previous one, and a twelve-month chart with last year as a reference line.
• Breakdowns by product, by revenue source and by cost provider.
• Connectors that take an API key with the narrowest access each provider offers, test it before saving, and store it encrypted. OpenProfit only reads with it. Two years of history on the first sync, incremental after that. Security lists what each key can do.
• Product mapping per provider sub-unit, with an Unassigned bucket for the rest.
• Flat costs for subscriptions, domains, one-time purchases and anything without an API.
• Multi-currency workspaces with daily rates and a base currency you can change later. Workspaces in Canadian dollars use the Bank of Canada's rates.
• Books: a monthly journal for QuickBooks, Xero or any accounting software, and the year's numbers on the lines of your tax form (T2125 and TP-80, the T2's GIFI schedules, Schedule C or Form 1120).
• Alerts for cost spikes, margin floors and sync failures.
• Weekly email with last week against the week before.
• Public pages per product, server-rendered from the same data.
• Dark mode, keyboard search, and a layout that holds on a phone.
• Self-hosting in one container with Postgres built in, or a postgres:// URL to your own.
• Sign in with email, GitHub or Google.

Connectors

App Store, Google Play and Supabase are next. A connector is one file in src/connectors that implements verify and fetchRevenue or fetchCosts. If you want one that is not here, open an issue with a link to the provider's billing API, or send a pull request.

Getting started

The quickest way is the hosted version at openprofit.dev. Sign in, create a workspace, connect one revenue source and one cost source, and the overview fills in.

Free while your products make under $2,500 a month combined. After that, a flat price that never grows with your revenue. Every connector on every plan.

Self-hosting

One container. Data lives in an embedded Postgres on a volume, so there is nothing else to run.

docker run -d \  --name openprofit \  -p 3000:3000 \  -v openprofit_data:/app/data \  -e SECRET_KEY=$(node -e "console.log(require('crypto').randomBytes(32).toString('base64'))") \  -e APP_URL=http://localhost:3000 \  ghcr.io/morencyr/openprofit:latest

Open http://localhost:3000/login and enter your email. Without an email provider the sign-in link prints in docker logs openprofit. Set RESEND_API_KEY and EMAIL_FROM to send it by mail. Point DATABASE_URL at a postgres:// server to use your own database.

The self-host guide covers updates, Dokploy and Railway. The environment reference lists every variable.

How it works

One TanStack Start app serves the landing page, the docs and the app. A scheduler inside the server pulls each connection on its cadence, converts amounts to the workspace's base currency, and upserts lines by the provider's own ids, so re-running a range never double-counts. The overview is grouped sums over those lines.

src/connectors/   one file per provider: verify, fetchRevenue, fetchCosts, fetchSnapshotssrc/server/       sync runner, FX rates, alerts, weekly email, billing, server functionssrc/routes/       landing, docs, app pages, API routessrc/db/           Drizzle schema for Postgres; migrations in ./drizzle

Postgres everywhere: PGlite embedded for self-host and local development, a Postgres server for the hosted version. Auth is Better Auth. Styling is Tailwind.

Development

Bun 1.3 or later.

bun installcp .env.example .env    # set SECRET_KEYbun run db:seed         # a demo workspace with a year of numbersbun run dev

Sign in once at http://localhost:3000/login, then attach the demo workspace to your user:

bun run db:seed [email protected]

Checks: bun run check (Biome), bunx --bun tsc --noEmit, bun run build. After a schema change, bun run db:generate writes a migration; migrations run when the server starts.

Contributing

Issues and pull requests are welcome. Connectors are the most useful contribution. CONTRIBUTING.md lists the files a connector touches, the data it must return and how to test it against a real account.

Found a security problem? Email [email protected] rather than opening an issue.

License

MIT. The hosted version at openprofit.dev is operated by Lobbystack Inc.