Free. No paid edition, no fee on what you bill.
Hardcount is MIT-licensed. Every feature is in the one edition. There is no cloud version, no licence key and no share of your revenue.
What you pay for
- Your server. One server listed at €6.49 a month before VAT in October 2026 (2 shared CPUs, 4 GB memory) handled 12 usage events a second, with bursts to 60, for 20 minutes. It had no errors, and its CPU was 12% busy on average. At 12 a second that is about 1 million events a day. That was the load sent, not a limit. The test used v0.8.0; at that rate the disk fills first. How it was measured →
- Stripe’s card fee on each payment (for example 2.9% + 30¢ for a US card; see stripe.com/pricing), and Stripe Tax’s fee if you turn it on.
- Your time to run it: one program plus Postgres and Redis. What running it takes →
What Stripe Billing’s fee would be
Stripe Billing’s pay-as-you-go plan takes 0.7% of what you bill, on top of the card fee (Stripe Billing pricing). Hardcount uses Stripe to charge the card, and to work out tax if you turn on Stripe Tax.
| You bill each month | Stripe Billing’s 0.7% | Each year |
|---|---|---|
| $10,000 | $70 | $840 |
| $100,000 | $700 | $8,400 |
| $1,000,000 | $7,000 | $84,000 |
Help
There is no paid support or hosted version. Help is best-effort from the maintainer, in GitHub Discussions or by email.
Lock-in, what happens if the maintainer stops, and safety for real money: FAQ →
Try it on your computer
Start Hardcount in test mode and run its demo. Found something rough? Open an issue or a Discussion.