Diaphana
Service

Surveillance software

A public application for an outbreak: map, timeline, cases, contacts, and border measures, in one place.

The public map is at 2026bdbv.diaphana.io/app . It is a Next.js application deployed as a Cloudflare Worker. Application data are a Neo4j property graph of cases, contacts, follow-up, and provenance. Companion Rust crates provide surveillance compute used by the engine.

What you get

  • One picture of the event Overview, timeline, cases, contacts, map layers, and border measures are views of the same record.
  • Readable without the graph When the database is not configured, the application can still serve an approved static snapshot.
  • A private place to change the record Curation — inbox review, approval, rejection, and conflict resolution — is not part of the public map.

How we work

  1. Model the event

    Cases, contacts, follow-up, and provenance are modelled as a property graph.

  2. Serve an approved read

    The public application consumes claims a person has already accepted.

  3. Keep the tools apart

    The map is public. The application that edits the record is not.

Deliverables

  • Public map application
  • Shared schemas for curated entities
  • Separate curation application
Case studies

Related work

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