Get in touch
Pilots, certification, integrations, or a walkthrough — email jengu@jengu.cloud and we'll respond within a working day.
Commercial conversations
For pilots, certification cover under your jurisdiction's medical-devices regulator, custom integrations, or vendor-managed deployments — email jengu@jengu.cloud.
We're particularly interested in:
- EU clinics and small hospitals evaluating a foundation that takes the EU regulatory environment seriously from day one.
- Module developers who want to build clinical features on top of the platform's multi-tenancy, anonymisation, audit, and edge-cloud resilience without re-implementing them.
- Researchers who need anonymised clinical data with proper consent semantics and zone-aware compliance.
Open-source / self-hosting
The platform code is MIT-licensed (see
LICENSE)
and a documented self-hosting bundle lives at
deploy/self-host/.
For self-hosters running the open-source code, the GitHub issue tracker
is the support channel:
- Platform: github.com/jengu-net/jengu-platform/issues
- Lab module: github.com/jengu-net/lab/issues
- Visit Assistant module: github.com/jengu-net/jengu-visits/issues
The open-vs-closed line — what's vendor-managed, what self-hosters take on — is documented in arc42-007-deployment/self-hosting.md. The vendor does not carry support obligations for self-hosted deployments.