Firms that cannot put the books elsewhere
Where a rule, a client contract or a straightforward preference says the financial data stays on infrastructure you control, this is the answer rather than a negotiation.
Moneman was written against ordinary shared hosting from the first commit. If your site runs on cPanel today, Moneman runs there too.
No queue worker, no supervisor, no daemon to keep alive.
No Redis, no Memcached, no search server.
No Node, no build step, no asset pipeline to run on deploy.
No Docker, no Kubernetes, no container registry.
These are not omissions. Background work runs off the one cron entry, the cache and sessions sit in the database, and the interface is served as plain compiled assets. It is the same code that runs the hosted version — there is no cut-down edition.
Where a rule, a client contract or a straightforward preference says the financial data stays on infrastructure you control, this is the answer rather than a negotiation.
One installation, one corporate account per client, one permission matrix. The isolation boundary is the same one the hosted version runs on.
The intent is that you own what you run rather than rent it. The licence terms are being written down properly rather than improvised in an e-mail — ask and we will send you what exists today, before you commit to anything.
Tell us roughly how many companies and how many people, and we will come back with a price and an installation checklist. There is no sales process to sit through.
Write to ushello@moneman.com