There is no licence key, no seat counter and no billing code anywhere in the repository, so there is nothing to unlock and no bill to raise. What MicroPyramid sells is the two things the software cannot be: hosting you do not have to think about, and people who know it well.
Unlimited users on every option. Self-host it and the bill is your own server.
The middle and right options are services, priced after a conversation because they depend on your size, your uptime needs and what you are moving off. The software underneath is the same in all three.
$0forever
Self-host it. The complete CRM, with nothing held back.
No account needed to download.
Talk to us
We run it, watch it, and pick up the phone when something matters.
Priced after a call, because it depends on your size and your uptime needs.
Get a quote
Built around your process, with your team trained on it.
Scoped and agreed before anything is built.
We do not publish other vendors' prices, because we would be quoting figures we cannot keep current on plans that change without telling us. Find your own per-seat price on your last invoice and read across.
| Team size | BottleCRMany size | At $15per user, per month | At $25per user, per month | At $50per user, per month |
|---|---|---|---|---|
| 5 users | $0 | $900 | $1,500 | $3,000 |
| 10 users | $0 | $1,800 | $3,000 | $6,000 |
| 25 users | $0 | $4,500 | $7,500 | $15,000 |
| 50 users | $0 | $9,000 | $15,000 | $30,000 |
Every figure here is multiplication, not a claim about anybody's product: headcount times the monthly seat price times twelve. The BottleCRM column stays at zero down the page because there is no per-user fee to multiply.
Self-hosting moves the cost rather than deleting it. Here is what it moves onto you, so the comparison above is one you can actually trust.
PostgreSQL and Django. Row-level security is enforced by the database, so Postgres specifically, and the application user must not be a superuser or the isolation is inert.
Recurring invoices, overdue marking, SLA breach scanning and stale-timer cleanup are eleven scheduled jobs, not page loads. Skip the Celery worker and its beat process and those features silently do nothing.
Backups, upgrades, TLS and the mail provider are yours. This is the part a subscription was buying you, and it is the honest reason managed hosting exists as an option.
A pricing page that only lists what you get is the same omission it accuses subscription vendors of. These are the limits and the gaps, on the page where they matter most.
The software costs nothing and always will. A server, a database and the hours to look after them cost what they cost. On a small team that is usually far less than a seat licence, and it is not zero.
There is no licence key, no tier flag and no metering anywhere in the codebase, so there is no gated feature for us to unlock later. What we sell is people and hosting, which is the only thing that stays honest when the code is public.
Invoices go out and you record payments when the money arrives, including partial ones. There is no gateway and no Pay now button. The word Stripe appears once in the codebase, as a label on a payment you record yourself.
Mail arrives and becomes a ticket, threaded against the account it came from. The CRM sends assignment notices and a satisfaction survey. It does not compose and send mail to a customer, so this is not a replacement for your inbox.
Storage is your own disk, so there is no quota to buy. A single attachment over 25 MB is refused, and a CSV import or lead upload over 5 MB is refused, which is a real limit rather than an unlimited claim.
The importer is built and tested on the backend, with per-row error reporting, and neither the web app nor the phone can reach it. Moving an existing CRM in is one of the things the paid migration covers.
There is no seat counter and no billing code to find, and the repository is open, so that is a claim you can check rather than take.
Yes, and the reason is structural rather than a promise. There is no licence key, no seat counter and no billing code anywhere in the repository, so there is no mechanism by which a feature could be withheld or a bill raised. You pay only if you want us to host it or to build something on top of it.
All of it. Leads, contacts, accounts, the deal pipeline, tasks, support tickets with SLA clocks, invoices and estimates, goals, custom fields, the documented API and the mobile app. The paid options buy hosting and people, not features.
Because hosting and expertise cost real money and the software does not. Selling those instead of selling the code is what keeps the code free, and it means we have no incentive to hold a feature back for a paid tier, since you could read the source and see us doing it.
Yes. It is your database on infrastructure you can take over, under an MIT licence with no contract and no lock-in. If you leave managed hosting you keep running the same software, which is not something a subscription can offer you.
Take your per-seat price, multiply by your headcount, multiply by twelve, and subtract what your own server costs. That is the whole calculation, and it is why the table above has no vendor names in it: we would be quoting prices we cannot keep current, on plans that change without telling us.
A small team runs comfortably on one modest server with PostgreSQL, Redis and a Celery worker alongside the web process. The cost is that server plus whoever looks after backups and upgrades. If that person does not exist on your team, managed hosting is the honest answer rather than a pretence that self-hosting is free.
Take the whole CRM, put every person on it, and never see a per-seat line. When you would rather not run the server, that is the conversation to have with us.
