The Zeroic Journal

Is Supabase HIPAA compliant? What you still add

Supabase signs a BAA and offers a HIPAA add-on. Access rules, logging and the rest of the compliance work stay with you, and here's the list.

On this page 5 sections
  1. What Supabase signs and sells
  2. A High Compliance project sets five things
  3. Is Supabase HIPAA compliant? Not on its own
  4. Your Supabase HIPAA decision guide
  5. How TopUp Care built privacy in from day one

Is Supabase HIPAA compliant? The hosted platform can be, once you sign a BAA with Supabase, add its paid HIPAA add-on (available on the Team plan, from $599 a month, and on Enterprise) and set the project to High Compliance. Supabase’s own documentation leaves access rules, logging and your policies to you.

The mistake we see is treating the BAA as the finish line. It’s the entry ticket. A signed agreement lets you put patient data in the database legally, and it says nothing about whether your app shows that data to the wrong person.

What Supabase signs and sells

Supabase’s HIPAA documentation says plainly: “Customers must sign a BAA with Supabase.” The BAA defines Supabase’s responsibilities as a business associate, and Supabase says it has its own BAAs with vendors that may access patient data, such as AWS. It also says HIPAA controls are audited annually, in the same period as its SOC 2 audit.

Three conditions apply before you can touch patient data:

  • A signed BAA. You request it through Supabase’s form. Supabase’s page says organizations must have it before handling patient data.
  • The HIPAA add-on. Supabase’s pricing page lists it as a paid add-on on Team (from $599 a month) and on Enterprise. Free and Pro don’t include it. The page doesn’t print the add-on’s price.
  • The hosted platform. Supabase states the hosted platform has the controls needed to meet HIPAA requirements, and that those controls are not supported out of the box in self-hosted Supabase.

If you’re prototyping on a Pro plan today, that’s fine with fake data. The moment live patient records go in, you need to be on the upgraded setup.

A High Compliance project sets five things

Once the add-on is on, Supabase’s guide to configuring HIPAA projects tells you to mark the project High Compliance in the project settings. The option appears only with the add-on enabled. The same page lists what the project needs:

  • Point in Time Recovery, which requires at least a small compute add-on.
  • SSL enforcement turned on.
  • Network restrictions enabled.
  • Postgres connection logging kept on.
  • A signed BAA on file for the organization.

After that, Supabase runs continuous checks and raises warnings in the Security Advisor when a setting drifts. Treat those warnings as a pager, not a suggestion. Supabase says the customer applies the recommended controls when the advisor flags one.

Is Supabase HIPAA compliant? Not on its own

Supabase’s shared responsibility model splits the work cleanly. Supabase handles infrastructure, backups, operating system maintenance and encryption at rest and in transit. You handle “access management” and making sure sensitive tables have the right level of access. That second half is where health apps fail an audit, and it’s four jobs.

1. Row level security on every table. Supabase’s RLS guide says to enable RLS on every table in an exposed schema. A table without it is open to any role with a grant. A patient should read their own records, a clinician only their own patients’, and an admin no clinical notes at all. Write those rules as policies, then test them with two accounts. Our guide to why Supabase RLS stops working covers the usual causes.

2. Keys and the service role. A secret key authorizes requests as the service_role Postgres role, which has the bypassrls attribute. One in a browser bundle means every patient record is readable. Keep it in server code and rotate it if it ever leaves. The checks in our Lovable app security checklist apply to any Supabase app, not only Lovable ones.

3. File storage. Scans, lab PDFs and ID photos land in Storage. Supabase’s storage access control docs say public buckets are readable without policies, so every bucket holding patient files should be private and gated by policies.

4. Audit logs. You need to be able to answer who read which record. Supabase’s PGAudit guide shows how to enable it and choose what to log, with caveats worth knowing. Logging everything generates volume that buries important events. By default it records queries but not the rows returned. And Supabase doesn’t support logging query parameters, because they could expose secrets. So decide up front what “who accessed this record” means, and log it at the application level where the database can’t.

Sign-in matters too. Supabase Auth supports MFA through an authenticator app or phone messaging, and clinician accounts should require it. Nothing here replaces your own policies, staff training and risk assessment, which Supabase says remain yours.

Your Supabase HIPAA decision guide

Use this to decide where you stand:

Your situationWhat to do
Prototype with fake dataAny plan. Don’t load a single live record.
Consumer wellness app, no clinic customerAsk a lawyer whether HIPAA applies before you pay for the add-on.
Clinic or provider group is your customerTeam or Enterprise, signed BAA, add-on, High Compliance project.
Considering self-hostingExpect to own every control and its evidence. Talk to your auditor first.
Other vendors touch patient data (video, SMS, email)Each needs its own BAA. See the vendor list in our telehealth cost guide.

Budget the platform side before you promise a launch date. Team starts at $599 a month before the add-on and compute upgrades, which matters for a pre-revenue product.

How TopUp Care built privacy in from day one

We built TopUp Care, a telehealth platform for clinicians in Africa. Doctors sent anonymous clinical questions to specialists, referred patients on and discussed cases in specialty chat rooms. It onboarded six hospitals and clinics across four countries, including Liberia, Ghana and Cape Verde, with over 100 doctors on the platform. HIPAA is a US law and none of those clinics were in the US, so it didn’t apply. Patient privacy was still part of the build from the first screen: data was anonymized by design, both identities stayed hidden in a consult, and providers and specialists got separate views.

That order is the one to follow on Supabase: write the roles, then the policies, then the interface. For a US health app, we build to HIPAA requirements on top of that: we choose and configure each vendor with you and document each safeguard alongside your compliance lead. Our page on HIPAA compliant app development covers how we run that build, and hiring Supabase developers shows how we work with the stack.

Frequently asked questions

Does Supabase sign a BAA?
Yes. Supabase's HIPAA page says customers must sign a business associate agreement with Supabase, which defines its responsibilities under HIPAA. You start the request through Supabase's form. Supabase's HIPAA configuration page says organizations must have a signed BAA before handling patient data. Supabase also says it has signed BAAs with its own vendors that may touch patient data, such as AWS.
Which Supabase plan do I need for HIPAA?
The Team plan or Enterprise. Supabase's pricing page lists HIPAA as a paid add-on on Team, which starts at $599 a month, and on Enterprise. It isn't included on the Free or Pro plans. The page doesn't state the add-on's price, so get a quote from Supabase before you budget for it.
Can I use self-hosted Supabase for HIPAA?
Not on Supabase's say-so. Its HIPAA documentation states that the hosted platform has the controls needed to meet HIPAA requirements, and that those controls are not supported out of the box in self-hosted Supabase. If you self-host, you own every control and the evidence for it, so talk to your auditor first.
Does using Supabase make my app HIPAA compliant?
No. Supabase says you must comply with the HIPAA Privacy, Security and Breach Notification Rules yourself, configure your project and follow its Security Advisor. The platform covers encryption and infrastructure. Who can see which record, what gets logged and your internal policies are your job, and a compliant database doesn't fix a leaky app.
Do I need a BAA for a health app that isn't for clinics?
Only if you handle health data for a covered entity, such as a clinic, provider group or health plan. A consumer wellness app sold directly to users can sit outside HIPAA, though other rules may still apply. If a clinic is your customer, expect it to ask for a BAA with you and with every vendor that stores patient data.

References

  1. Supabase - HIPAA compliance
  2. Supabase - Configuring HIPAA projects
  3. Supabase - Pricing
  4. Supabase - Shared responsibility model
  5. Supabase - Row Level Security
  6. Supabase - Storage access control
  7. Supabase - PGAudit

More from the journal

Hear from Prashant within 24 hours.

Prashant Abbi Partner @ Zeroic

Planning a health app on Supabase? An MVP Sprint ships your first version in 5-6 weeks with roles, row level security and audit logging designed in from week one. One fixed price, agreed before we start. Sprints start at $12,000.

See the MVP Sprint, or book a 30-minute call