temetrotemetro
Our story

Built in Djibouti, for clinics everywhere

temetro started with a simple, frustrating observation about the software that runs everyday healthcare.

The problem in front of me

I live in Djibouti. Spend any time around the hospitals and clinics here and you notice the same thing again and again: the systems that hold patient information are years, sometimes decades, behind modern practice. Records live in paper files or in brittle, locked-down programs that no one can extend. Information is hard to find when it matters, easy to lose, and almost impossible to move from one place to another. Clinicians spend their energy fighting the tools instead of caring for patients.

It is not just here

The more I looked, the clearer it became that this is not a Djibouti problem. Across many countries in Africa, clinics are asked to choose between expensive systems built for somewhere else and no real system at all. Patient data ends up trapped inside a vendor, scattered across tools, or simply on paper. When software does exist, it rarely respects the people whose data it holds. That gap is exactly where a different kind of tool can help.

What temetro is

temetro is an open-source workspace for patient care. It brings records, scheduling, prescriptions, notes, and tasks into one place, with a built-in AI chat that lets you ask for what you need in plain language and get clean record cards back. It is designed to run on your own infrastructure, so a clinic keeps control of its data instead of handing it to someone else. And it is built toward a future where the record can belong to the patient: stored on their own device, changed only with their approval.

  • Open source

    Every line is readable. Any clinic, anywhere, can run it, audit it, and shape it to how they actually work.

  • Self-hostable

    Run it on a single machine in the clinic or in a private cloud. Patient data stays inside your own network.

  • Patient-owned data

    The model we are building toward keeps a patient's record on their own device, where changes need their approval.

  • Role-based access

    Owner, clinician, reception, pharmacy, and lab each see only what their job needs. Nothing more.

Where we are

The platform is in beta and openly in development. The workspace is real and you can run it today, while parts of the vision are still being built in the open, including the patient-owned wallet app, a separate companion still in early alpha. If any of this sounds like a problem you know, we would love your help.