Diaphana
Diaphana, LLC

Public information that can be checked

We build software that keeps a public record attached to the documents behind it. The published work is an interactive account of the 2026 Bundibugyo virus outbreak.

Open the map Read the case study
  • Public Outbreak map
  • Human Approved claims
  • Open Source code
What we build

Records, software, and the sites around them

Three kinds of work, shown by the outbreak project rather than by a catalogue of clients.

Surveillance software

Map and timeline software for a public-health event, with the sources kept in view.

  • Map, timeline, cases, and contacts
  • Border measures on the same record
  • English-language public application

Source-backed data

Provenance, human approval, and visible conflicts for data that will be read by the public.

  • Every claim points at a source
  • A person approves the public read
  • Conflicts stay visible until resolved

Public sites

Company and project sites hosted on Cloudflare, written so a reader can find the work and the contact address.

  • Static HTML on Cloudflare
  • No third-party scripts by default
  • A direct email address

All services

Published work

The 2026 Bundibugyo virus dashboard

A public map of cases, contacts, border measures, and the sources behind them.

Case study

The company

A record is only as good as its sources

Diaphana, LLC is a United States company. The work we publish is software for public-health information, with a person between a source and what the public sees.

  • Sources stay attached A figure on the map points back to the official release, news report, or paper it came from.
  • Approval is human Automated extraction does not publish on its own. A curator accepts or rejects a claim first.
  • Conflicts stay on the page When two sources disagree, both claims remain visible until someone resolves them.

About Diaphana

How the work is judged

Four rules for a public record

  • Primary sources

    Published figures stay linked to the official release, news report, or paper they came from. A number without a source is not ready to show.

  • A person approves the claim

    Automated extraction does not publish on its own. A curator accepts or rejects a claim before it becomes a public read.

  • Disagreement stays visible

    When two sources assert incompatible values, both remain on the record until a person resolves the conflict.

  • Public where it can be

    The outbreak map and its source code are public. Curation tools that change the record stay private.

Method

From a document to a public read

This is the path used on the outbreak dashboard.

  1. Gather the sources

    Start from official releases, government notices, news reports, and published papers. Each snapshot keeps its origin.

  2. Review the claims

    A person reads what was extracted, then approves or rejects it. Unapproved material does not appear on the public map.

  3. Publish the approved read

    The public application shows cases, contacts, border measures, and the sources behind them. The private curation app is separate.

  4. Leave conflicts in view

    If sources disagree, both claims stay linked until a curator marks one side, the other, or neither as resolved.

Questions

Before you write

What does Diaphana build?
Software that keeps public information attached to the documents it came from. The published product is an interactive record of the 2026 Bundibugyo virus outbreak.
Where is the outbreak dashboard?
The public map is at https://2026bdbv.diaphana.io/app . The source is at https://github.com/diaphana-io/2026bdbv-dashboard .
Who verifies the data?
A person does. Production reads use human-approved claims from official releases and news. When sources conflict, both claims stay visible until someone resolves them.
Contact

Write to Diaphana

For questions about the published work, or about software in the same line, write to matt@diaphana.co.

Email matt@diaphana.co See the work