Jengu

What you're really paying for

When you buy clinical software, you're paying for clinical capability — Lab functions, visit recording, AI assists, billing handoffs. What every existing option also asks you to maintain is everything else: data-residency proof, audit certification, GDPR consent flows, anonymisation pipelines, integration code, a vendor-lock-in exit plan. The capability you wanted gets buried under the work you didn't.

That extra work isn't optional. EU healthcare regulation makes it mandatory; procurement won't pass it without; auditors come back for it every year. So someone has to do it. The question is whether your team carries it, your vendor carries it but in a shape that locks you in, or your vendor carries it in a shape that keeps the door open.

What Jengu is

A shared foundation that clinical modules plug into. The modules are what your clinicians actually use day-to-day; the platform underneath is what makes each module legally and operationally acceptable — multi-tenant isolation, encryption, audit, consent, anonymisation, edge resilience, jurisdictional compliance. None of that is the product you buy. The clinical modules are.

The platform is the substrate; the modules are the value. We charge for operating them — running them at the SLA you need, certifying them under your regulator, integrating with your partners, supporting your clinicians. The code is open: a customer who wants to self-host can. We don't penalise it and we don't subsidise it.

Why customers choose Jengu

1. Working clinical software, not a system to assemble. Lab and Visit Assistant deliver the daily clinical work today, with Insurance and Billing coming. You buy the clinical capability; the regulatory plumbing — encryption, audit, anonymisation, residency — comes with it because it has to.

2. Trust by construction, not by promise. Configuration in your git repository. Data in standard FHIR. Code open under MIT. The on-site appliance is yours. Every clinical operation lands in an audit trail you can query. You can verify what we did, leave with what's yours, and self-host if you want. Read the features page for the testable form of every claim.

3. EU from day one. Per-jurisdiction compliance zones, AI providers chosen per zone, retention floors matching local law, recordings consented under GDPR, language support that starts from EU member-state languages. Not a US product with regional add-ons.

How we work

Eight principles shape every decision in the platform — how we choose third-party components, what we'll and won't build, where honest limits sit. They're collected on Our principles.

The full inventory of what the platform delivers, with the testable form of each claim and the honest limits, is on Platform features.

Where things stand

The implementation status dashboard is auto-generated from feature pages (what is promised), runtime requirements (what is testable), and the latest CI test results (what currently passes). Today much of it is amber — promised broadly, verified narrowly. As the platform ships, it greens out.

Talk to us

For a demo or to discuss whether Jengu could fit your healthcare organisation, write to jengu@jengu.cloud.