Eleven modules that share one customer record, one API and one bill of zero. Each has its own page below, and each of those pages says what it does not do as plainly as what it does.
Self-hosted, MIT licensed, unlimited users. Nothing on this page is behind a paid tier.
A lead becomes a contact, the contact belongs to an account, the account carries the deal, the deal turns into an invoice, and the ticket that arrives afterwards already knows all of it. That chain is the product. The modules are just where you stand on it.
Get leads in, work them down, hand the good ones to an account. Four ways in, duplicate detection on the way, and a conversion that runs once.
Read the detailBuild a form in Settings, paste one line on your own site, and what people fill in becomes a lead or a support ticket here. No key on your page, no account for the visitor.
Read the detailEvery person you deal with, searchable in one box, with the fields your business actually uses rather than the ones a vendor decided on.
Read the detailEvery deal, person, ticket and invoice attached to a company, on one page. Flat, searchable, and honest about what it does not model.
Read the detailPipelines and stages you define, each stage with its own idea of how long is too long. Drag a deal forward when it moves, and turn a won one into an invoice.
Read the detailEvery deal, ticket, lead and account carries its own work. Three views of one queue, on the same records as the rest of your CRM.
Read the detailMail or a web form arrives, becomes a ticket, and already knows which account it came from. Replies go back out as threaded email, and your answers can live in a public help center.
Read the detailA board, hierarchy, merges, approvals, macros, time tracking, and the numbers behind all of it, satisfaction included. Put the whole support team on it and the bill does not move.
Read the detailQuote it, bill it, chase it, record it. On the same customer record as the deal it came from, with no per-invoice fee.
Read the detailSigned webhooks to Slack, Zapier, n8n or your own code when something happens, and CSV import and export when the data has to move in bulk.
Read the detailOne Flutter codebase for iOS and Android against the same API as the web app. Every module, the boards and the admin settings included, built and signed by you.
Read the detailThese are not modules and they do not get their own page. They apply everywhere, and they are the reason the eleven above behave like one product rather than eleven.
Your org defines the schema, no code and no migration. They render on the web forms and the phone forms, filter in list views, and come back through the API. Retiring a definition is a soft delete, so the values already recorded stay readable.
JWT-authenticated, every entity, with a generated OpenAPI schema and both Swagger and Redoc served by the backend itself. The mobile app is a client of it, which is the only guarantee that matters: the API is not a side door, it is the door.
Postgres row-level security, keyed on the organisation in your token and applied by the database rather than by application code. A query that forgets its filter returns nothing instead of returning someone else.
Files on leads, contacts, tasks and tickets from either client, and on deals from the phone. An account takes an attachment through the API with no screen calling it yet, and an invoice does not take one at all.
Admin and User. That is the whole list, and saying so is more useful than a permissions grid you would have to test. A self-hoster's Django superuser counts as an admin in every organisation they belong to. Access is decided by role plus ownership plus organisation, and the checks live in the API rather than in the interface.
Filter leads, contacts, accounts, deals, tickets or invoices the way you work them, save it under a name, and open it again with one tap. A view saved on the web opens on the phone. Views are private to whoever saved them.
Sign-ins, organisation switches, refused requests and paused webhooks, newest first and filterable by event, person and date, in Settings on the web and the phone. Read-only, and closed to API tokens.
A record in your own organisation that you are not allowed to open answers exactly like one that does not exist, on every API call. Nobody learns that an id is real by being refused it.
Ticket analytics by agent and by queue with customer satisfaction beside them, a weighted pipeline total, and a real accounts-receivable aging report with buckets rather than a single overdue flag. Not a dashboard builder.
Every one of these was on this page until we checked it against the source. They are listed rather than quietly deleted, because the gap between what a CRM claims and what it does is the thing that costs you a month.
This page used to promise all three. None exists. Leads have a source, a status and an owner, and moving one forward is something a person does.
A task has a due date and the list sorts by it. Nothing emails you, and nothing repeats a task on a schedule.
Invoices go out and payments get recorded when the money arrives, including partial ones. There is no Stripe integration, no gateway, and no "Pay now" button.
Tasks live in the CRM and on the phone. There is no iCal subscription for Google or Apple Calendar.
Run it on your own server, put the whole team on it, and change anything you like. The licence is MIT and the price is nothing, at every size.
