One engine. Many tools.
Each track is an operational tool with a clear who-it's-for — built in-house with the people who use it, or contributed by aligned practitioners. Every one inherits the same DLM engine, signed audit trail and Swiss/EU residency by design.
Back-office assistant
in buildRoutine bookings, bank reconciliation, recurring invoices and document filing. Anything outside its confidence zone is queued for the accountant your organisation already has.
Open →Learning hub
in buildA tutor that can be audited by learner, parent and teacher — and that doesn't drift between sessions. Picks up next week exactly where it left off.
Open →Your track
openCarry expertise entrosana hasn't built for? Propose a track. You bring the domain; the foundation provides the scaffolding.
Open →Build the tool once. Inherit the guarantees.
A track never re-implements the hard parts. The pinned model version, the deterministic retrieval order, the signed audit trail and Swiss/EU residency by design apply automatically — so a new tool starts audit-grade on day one.
How tracks are contributed