For teams building healthcare apps

The secure data layer for healthcare developers.

Patient records, lab ordering, user management and auth, and audit trails. HIPAA-compliant on day one. You own the app.

  • SOC 2 Type II and one BAA, out of the box
  • Labs and structured workflow encoding, built in
  • Prototype to production in about a month.

Works with your coding agent

Hand your agent one link. It learns the data model, the auth pattern, and about 125 recipes, then checks every request shape against the live API reference before it writes a call.

> Wire my prototype lab results inbox app on 1health for production.

  • Patient Vault: records stored and logged
  • LabLink: orders and results
  • Audit log on every read

Live in production

  • 3

    National health plans

  • 3

    Large health systems

  • 2.7M

    Patients on the platform

  • SOC 2

    Type II, audited today

Where the line is

Your app. Your customers. Your business.

We are the layer underneath, not a competitor on top.

Developer owns

Your app

  • Your product and your brand
  • Your customers and patients
  • Your clinical logic and know-how
  • Your pricing and your revenue
  • Your code, data, and frontend
  • Your name on it, not ours

1health provides

The data layer

Base capabilities of every service

Runs on

AWS

AWS is audited for the servers. 1health is audited for what runs on them: the patient records, the access rules, and the audit logs. You build on the top layer and never touch the base, the same way you write in a high-level language and never write the assembly underneath it.

Your frontend and non-patient data can live on any host: Vercel, Supabase, AWS, or your own.

Our promise to builders

  • Your data stays yours.

    We run it. We don't mine it, sell it, or use it to build anything for anyone else.

  • We don't go after your customers.

    We don't contact them or sell to them.

  • Simple pricing.

    We charge by the patient, not by the API route. Free sandbox, then $1 per patient per year in production.

Compare

A HIPAA database is not a HIPAA app.

1health runs on AWS too. The difference is what is already built and audited on top, so you don't spend a year building it yourself.

  • Compliance

    HIPAA compliant on day one

    AWS
    6 to 12 months
    Supabase
    6 to 12 months
    1health
    Day one
  • Compliance

    One BAA covers the stack

    AWS
    One per vendor
    Supabase
    Paid add-on, Team plan and up
    1health
    Included
  • Security

    Log of who viewed which patient

    AWS
    Build it
    Supabase
    Build it
    1health
    Built in
  • Business rules

    Structured workflows, shareable across organizations

    AWS
    Build it
    Supabase
    Build it
    1health
    Built in
  • Service

    Lab orders and results

    AWS
    Not offered
    Supabase
    Not offered
    1health
    LabLink

When should you use AWS or Supabase instead of 1health?

If you have a compliance team, months of runway, and want to design your own patient records, audit trail and access controls, AWS or Supabase gives you full control. If you want a HIPAA-compliant app in production in weeks, with patient records, lab ordering, user management and auth, and audit logs already built, use 1health.

See the full comparison and sources

Security and compliance

  • What their compliance covers

    AWS
    The infrastructure. AWS states there is no HIPAA certification for a cloud provider; you may only put PHI in the services listed in its BAA. [1]
    Supabase
    The Supabase product boundary. Your architecture, Row Level Security policies, access management, and third-party integrations stay your responsibility. [2]
    1health
    The platform your app runs on. HIPAA compliant and SOC 2 Type II audited today.
  • Business Associate Agreement

    AWS
    Accept the AWS BAA in Artifact, then sign one with every other vendor that touches PHI. [1]
    Supabase
    Available on Team ($599/mo) or Enterprise, plus a paid HIPAA add-on. Not available on Free or Pro. [3]
    1health
    One BAA with 1health covers the platform stack.
  • Audit logs for PHI access

    AWS
    CloudTrail logs calls to AWS services. Who viewed which patient's record is application logging you design and build.
    Supabase
    Connection logging must be turned on; record-level PHI access logging is yours to build. [2]
    1health
    Every read and write of patient data is logged by the platform.
  • Access controls

    AWS
    IAM for infrastructure. Healthcare rules (who may see which patient, under what consent) are yours.
    Supabase
    Postgres roles and RLS. You write and maintain the healthcare rules.
    1health
    Role, organization, and consent rules ship built in.
  • Time to a compliant first release

    AWS / Supabase
    Typically 6 to 12 months to a SOC 2 Type II report, including a 3 to 12 month observation period. [4] HIPAA risk assessment, policies, and vendor BAAs run in parallel.
    1health
    Day one for the platform controls. Your own risk assessment, policies, and training are still yours.
  • Cost to establish compliance

    AWS / Supabase
    First-year SOC 2 program for a small startup runs roughly $20K to $60K in audit and tooling, before engineering hours, which are the largest cost. [4] Our own estimate for a full HIPAA plus SOC 2 program is about $150K in vendors and $150K in team time.
    1health
    Platform controls included.

Business rules

  • Healthcare data model

    AWS
    Bring your own schema. HealthLake stores FHIR but does not define your app's model.
    Supabase
    Postgres. Bring your own schema.
    1health
    One data model for patients, providers, organizations, encounters, orders, and results.
  • Sharing PHI with a partner organization

    AWS
    Build it. Export to them, import their changes, and reconcile, or build them a login to your system.
    Supabase
    Build it.
    1health
    A partner invited into a workflow reads and writes your primary record inside that workflow. No copy, no export, no reconcile step.
  • Structured workflow encoding

    AWS
    Step Functions and queues; the definition, versioning, and data model are yours to design.
    Supabase
    Edge functions and cron; the workflow definition is yours to design.
    1health
    Workflow templates with version control, custom data on every step, isolated state for journeys in flight, and webhooks on each submit. Shareable across organizations.

Healthcare services

  • Lab ordering and results

    AWS
    None
    Supabase
    None
    1health
    LabLink: universal test catalog, order capture, standardized results.
  • Connections: HL7, FHIR, Direct, fax

    AWS
    Build or buy from an integration vendor; each connection is yours to run.
    Supabase
    None
    1health
    Conduit, part of the platform. Connections are made once and reused by every app.
Definitions
HIPAA-eligible vs HIPAA-compliant
Eligible means the vendor is allowed to hold PHI once you sign a BAA. Compliant means the controls are built, operating, and proven by an independent auditor. Eligible is where you start. Compliant is what you have to produce.
Business Associate Agreement
The contract that lets a vendor touch PHI. On AWS or Supabase you sign one with them and then one with every other vendor in your stack. On 1health, one BAA covers the platform.
Audit logs
A tamper-evident record of who accessed which patient's data and when. Eligible infrastructure gives you a place to store logs. 1health writes them for every PHI access.
Access controls
Each user sees only the PHI they are allowed to see. Eligible infrastructure gives you raw auth and roles. 1health ships the healthcare rules: role, organization, and consent.
Cross-organization data flow
Moving PHI safely between a provider, a lab, and a health plan, each a separate legal entity. Eligible infrastructure gives you nothing here. On 1health it is native, and it is where most of the value in healthcare lives.
What stays yours
Your own risk assessment, your team's policies and training, and how your app uses the data. 1health gives you the platform controls. You still run your business responsibly.
Sources
  1. AWS, HIPAA Compliance: no HIPAA certification exists for a cloud service provider; PHI should only be processed in HIPAA-eligible services defined in the BAA; a SaaS partner signs a BAA with AWS and its own customers may need a separate BAA with the partner.
  2. Supabase, Shared Responsibility Model: BAA requires at least the Team plan; customers mark projects as HIPAA projects, enforce MFA, enable point-in-time recovery, and keep connection logging on; application architecture, access management, and integrations remain the customer's responsibility.
  3. Supabase pricing and community discussion: HIPAA add-on priced separately on Team or Enterprise plans; not available on Free or Pro.
  4. Drata, SOC 2 compliance cost, and industry guides: first-year SOC 2 for a small startup from about $25K; Type II observation 3 to 12 months; total process 6 to 12 months. Internal engineering time is consistently reported as the largest unlisted cost.

Figures as of October 2026. Vendor terms change; check the linked pages before relying on them.

Services

Start with the core. Add what you need.

  • Core

    Patient Vault

    Secure storage for patient records. Every read and write logged. Share a record with a partner inside a workflow and they work on your record, not a copy.

    About Patient Vault
  • Core

    Workflow Builder

    Move work between people and organizations. Structured encoding of steps for scale and tracking.

    Workflow principles
  • Core

    Conduit

    Data in and out: health systems, health plans, and labs over HL7, FHIR, Direct, and fax. Part of the platform, not priced separately.

    Talk to us about Conduit

Your first screen in 30 minutes.

  1. Get a demo key

    Free. Sandbox data included. No sales call.

  2. Connect your coding agent

    One link teaches it the data model and the recipes.

  3. Ship against demo, then go live

    Same code. Swap to a production key when you're ready.

Questions first? Read the FAQ.

Running an accelerator or incubator? Start here.

Figures on this page as of October 2026.