Architecture

Designed for reality.

Choose the deployment model that fits your environment, from a single provider's machine to a self-hosted hospital deployment.

Deployment logic

The core idea is simple: keep data close to care, and only widen access where the organization truly needs it.

Independent provider

Single-doctor and personal-practice deployments with local-only storage.

  • 100% local storage
  • Encrypted on device
  • Full extraction tools
POPULAR

Small clinic / team

Local network syncing and role-based access without remote servers.

  • Local network syncing
  • Role-based access control
  • Strict data partitioning

Hospital deployment

Self-hosted compartmentalization for teamwise and departmentwise collaboration.

  • Secure compartmentalization
  • Collaboration suite access
  • Community support

Deployment Matrix

Different users, different operational shapes.

The core product stays the same, but the deployment story changes depending on whether you are an individual, a small team, or a larger institution.

Available now

Local-only deployment

Best for one clinician or a patient-led use case. Everything stays on the device, with local backup and export tools.

  • No remote server dependency
  • Fast retrieval and offline use
  • Clear ownership boundaries
Available now

Locally distributed team deployment

Designed for a clinic or team that needs collaboration while keeping the data within a local trust boundary.

  • Role-aware access and partitioning
  • Shared local sync and handoff
  • Simple expansion as the team grows
Phased later

Hosted hospital deployment

This is the path for a later stage of the product once the governance, support, and operational model are mature enough for formal hosting.

  • Dedicated hosting and deployment support
  • Department-level compartmentalization
  • Institutional policy alignment

Data Flow

Capture on the edge, review in context, export when needed.

The system is shaped to be useful even if the only reliable device is a phone or tablet. That means the pipeline needs to be simple, local, and resilient.

1

Capture

Data enters from messages, photos, scans, dictations, or manual entry.

2

Normalize

The app extracts fields, attaches source context, and turns inputs into structured records.

3

Partition

Data stays isolated according to patient, provider, clinic, or department rules.

4

Review

The care team can inspect summaries, timelines, and outstanding items without hunting through raw inputs.

5

Export

When a user needs to share information, the system can hand it off in a controlled way.

Design rules

Offline first

Core functionality should remain usable even when the network is poor or absent.

Local trust boundary

The default assumption is that data stays where the care team can control it.

Phased hosting

Hospital hosting comes later, after there is a stable product and a support model.

Composable modules

Different regulatory regimes can enable or disable capabilities without rebuilding the whole app.