Development Preview · Not yet generally available
Hosting operations software
built differently.
Ledgeron is a self-hosted billing and operations platform being built for hosting providers that need billing, customer management, services, provisioning, automation and support without stitching together a decade of legacy workflows.
Built for hosting providers · Self-hosted · Security-first · Modular architecture
We have made some decisions you may disagree with. Read them and tell us.
What is Ledgeron?
Most hosting businesses run on a billing system, a control panel, a support desk and a set of scripts that keep them roughly in sync. Ledgeron is being built to replace that arrangement with one self-hosted application: products, customers, orders, billing, services, provisioning and support in one place, under one authorization model and one audit trail.
Billing documents
ImplementedTax invoices can't be changed once issued, and the database enforces it. Numbering has no gaps, credit notes are the only correction, and money is kept in whole cents, never floating point.
Audit and explanations
ImplementedAn append-only audit log that holds no personal data, and a record of what decided each price, rate and tax.
Staff accounts and permissions
PlannedPermissions granted per staff member rather than one admin switch, a fresh login before sensitive actions, and refusing when authority is unclear.
Admin and client screens
PlannedOne modern interface, built around the jobs staff do most. No screen exists yet.
Product status
Updated November 2026
Ledgeron is under active development. Each area below carries its current state. Implemented means merged into the main branch, with automated tests passing on MySQL, MariaDB and PostgreSQL in CI. It does not mean finished or proven in production.
- Clients Implemented
- Product catalog Implemented
- Pricing and exchange rates Implemented
- Promotions Implemented
- Ordering Implemented
- Services Implemented
- Billing documents Implemented
- Automation Implemented
- Payments Implemented Not yet run against live Stripe
- Audit and explanations Implemented
- Tax In development
- REST API Planned
- Staff accounts and permissions Planned
- Admin and client screens Planned
- Client messaging Planned
- Migration from WHMCS Planned
- Installer and upgrades Planned
- Provisioning modules Planned
- More payment gateways, domains and registrars, support desk Planned
- Several billing companies in one install, EU VAT/OSS, e-invoicing Planned
What each area covers, and what each label means, is on the product page.
Development updates
All updates-
November 2026
A new build of Ledgeron
A new build replaces the earlier one under the same name. It runs on MySQL, MariaDB and PostgreSQL, and some areas once implemented are planned again.
-
September 2026 · Earlier build
Billing moves forward
Ledgeron can now create governed draft invoices and transition eligible invoices to issued state, with numbering, timestamps, due dates and customer snapshots owned by the server.
-
September 2026 · Earlier build
AI-assisted development governance
The development repository now includes formal operating rules for AI coding agents: module boundaries, testing requirements and security constraints, under the same review and CI workflow as human contributions.
Built for systems that handle money and infrastructure.
Ledgeron keeps money in whole cents, refuses to change a tax invoice once it is issued, and stores gateway tokens instead of card numbers. Every change runs over 5,300 automated tests on MySQL, MariaDB and PostgreSQL, and every task gets an independent review before it merges.
How Ledgeron approaches security- Over 5,300 automated tests on MySQL, MariaDB and PostgreSQL
- Each rule proved by breaking it on purpose
- Money in whole cents, with property tests
- Tax invoices that can't be changed once issued
- Append-only audit log with no personal data
- No card numbers stored, only gateway tokens
- Gateway credentials encrypted at rest
Roadmap
Full roadmapMilestones, in order, with no dates attached. The roadmap page explains why.
-
Now
Tax
Tax is the area being built now.
-
Next
REST API, staff accounts and permissions
The REST API, and staff accounts with permissions granted per staff member.
-
Then
Admin and client screens
One modern interface for staff and clients, built around the jobs staff do most, plus client messaging.
-
Then
Migration from WHMCS
Import an existing WHMCS install into Ledgeron, reconciled to the cent.
-
Then
Internal beta at GOZEN HOST
Ledgeron runs alongside GOZEN HOST's existing system, matched to the cent, before any live account moves.
-
2027
Controlled early access
Selected hosting providers from the early-access programme evaluate and pilot Ledgeron on their own infrastructure.
-
Later
General availability
Open availability once installation, upgrades and migration are hardened.
Decisions you can argue with
These are choices we have already made. Some of them will be wrong for the way you run hosting. Tell us which, and why, while they are still cheap to change.
Billing before screens
No screen exists yet. Clients, the catalog, ordering, services, billing documents and payments came first.
Would you have started with the screens?
Tell usAn issued invoice never changes
Once a tax invoice is issued, the database refuses to change it. Credit notes are the only correction.
When does your team edit an issued invoice today, and why?
Tell usMoney in whole cents
Never floating point. The money rules have property tests, and each rule is proved by breaking it on purpose.
Where has a billing system lost a cent on you?
Tell usThree databases, every change
MySQL, MariaDB and PostgreSQL, with the full test suite run on all three for every change.
Which one would you run it on, and why?
Tell usNo single admin switch
Permissions granted per staff member, a fresh login before sensitive actions, and refusing when authority is unclear.
What should your support staff never be able to do?
Tell usFour provisioning modules first
cPanel/WHM, Plesk, DirectAdmin and Virtualizor/Proxmox are being designed, with more to follow soon. The connection point they plug into is built.
Which panel or provider is missing from that list?
Tell usAn audit log with no personal data
Append-only, with a separate record of what decided each price, rate and tax.
What question should it answer that yours can't?
Tell usSelf-hosted first
Self-hosted is the design. A cloud edition running the same code is planned.
Would you rather we had started with the cloud edition?
Tell usReconciled to the cent before anyone moves
The internal beta at GOZEN HOST runs alongside the existing system, matched to the cent, before any live account moves. Migration from WHMCS 7.10 and 8.x is planned to the same standard.
What would you need to see before you moved?
Tell usRead more about who Ledgeron is for.
Help shape Ledgeron before general availability.
We are building Ledgeron first for real hosting operations at GOZEN, then expanding into controlled early access. Hosting providers interested in evaluating the platform, giving structured feedback or following development can register interest now.