Built for systems that handle money and infrastructure.
A hosting operations platform holds customer data, moves money and controls servers. Ledgeron stores gateway tokens instead of card numbers, encrypts gateway credentials at rest, keeps an append-only audit log, and refuses to change a tax invoice once it is issued. Each control below carries its status.
Security is being treated as part of the product architecture, not as a feature added before release.
No card numbers stored
ImplementedLedgeron keeps gateway tokens, never card numbers. Saved cards are charged on the due date, after any client credit.
Encrypted gateway credentials
ImplementedGateway credentials are encrypted at rest, and the code is built to keep secrets out of logs.
Append-only audit log
ImplementedThe audit log can only be added to, and it holds no personal data. A separate record shows what decided each price, rate and tax.
Invoices that can't be changed
ImplementedIssued tax invoices and credit notes can't be changed, and corrections go through credit notes. For tax invoices the database enforces this, with a tamper-evident chain that can be verified.
Money in whole units
ImplementedMoney is kept as whole minor units (cents), never floating point, and the money rules have property tests.
Tested on three databases
ImplementedOver 5,300 automated tests run on MySQL, MariaDB and PostgreSQL for every change. Each rule is proved by breaking it on purpose and checking that a test fails.
Checks on every route by default
PlannedEvery route is required to check login, permission and CSRF by default. No route ships yet: this is the rule the REST API and the screens are built to.
Staff permissions and re-authentication
PlannedPermissions granted per staff member rather than one admin switch, a fresh login before sensitive actions, and refusing when authority is unclear.
How changes are made
Every task gets an independent review before it merges, and every change runs the full test suite on MySQL, MariaDB and PostgreSQL in CI, whether a person or an AI coding agent wrote it. The repository carries written rules for AI-assisted development, and they apply to every contribution.
This website
This site is a separate system from the Ledgeron platform, on separate infrastructure, with no access to client accounts. The early-access form submits to a dedicated, tightly scoped endpoint. The only third-party script is Google Analytics, loaded only if you accept cookies, and a strict Content-Security-Policy limits the site to its own resources and Google's analytics endpoints.
Reporting a security issue
If you believe you have found a security issue in anything we run, email security@getledgeron.com. We read every report. A formal responsible-disclosure policy will be published before the first installation outside GOZEN.
Ledgeron is under active development and has not undergone a formal security audit or certification. A security review is planned before the internal beta. We would rather describe our design plainly than borrow badges, and we keep implementation-level detail off this site on purpose. Audits and certifications will be listed here once they exist.