HIPAA compliant hosting? Cloud platforms that sign a BAA
Cloud platforms and managed hosts that sign a BAA — and the big difference between infrastructure you secure yourself and hosting where the provider runs the safeguards for you.
HIPAA hosting and cloud platforms at a glance
HIPAA hosting means a cloud platform or managed host that signs a BAA — but the BAA covers only its eligible services, and how you configure them stays your responsibility. We compare 7 products in HIPAA hosting and cloud platforms. 5 sign a Business Associate Agreement (Amazon Web Services (AWS), Aptible, Atlantic.Net HIPAA Hosting, Google Cloud, Microsoft Azure). 2 sign one only for certain plans or products (Prisma Postgres, Supabase). Every value links to the vendor's own documentation and shows when it was checked.
| Sign a BAA | Amazon Web Services (AWS), Aptible, Atlantic.Net HIPAA Hosting, Google Cloud, Microsoft Azure |
|---|---|
| Only some plans or products | Prisma Postgres, Supabase |
| Products compared | 7 |
3 more facts
| Compared on | BAA without a sales process, Safeguards managed for you |
|---|---|
| Commissions | None — no vendor pays us |
| Facts checked since | 2026-10-06 |
Comparison
Alphabetical. No vendor pays us for listings, rankings or referrals — methodology.
| Product | Signs a BAA | BAA without a sales process | Safeguards managed for you |
|---|---|---|---|
| Amazon Web Services (AWS) | Yes | Not verified | No |
| Aptible | Yes | Not verified | Yes |
| Atlantic.Net HIPAA Hosting | Yes | Not verified | Yes |
| Google Cloud | Yes | Not verified | No |
| Microsoft Azure | Yes | Yes | No |
| Prisma Postgres | Conditional | No | Yes |
| Supabase | Conditional | No | Not verified |
Found an outdated or wrong fact? Report it
What to check before you choose
- Shared responsibility
- The provider's BAA covers its eligible services; how you configure them is your part. Read the provider's shared-responsibility description before you design anything.
- Only eligible services for PHI
- Large clouds list the services their BAA covers. Keep PHI — including logs, backups, queues and email — inside that list.
- Encryption and keys
- Encryption at rest and in transit are addressable specifications (164.312(a)(2)(iv), (e)(2)(ii)). For cloud hosting we recommend both, and deciding who manages the keys.
- Admin access and logs
- HIPAA requires access control, audit controls and person authentication (164.312(a), (b), (d)). Our recommended way to meet them: least-privilege roles, multifactor sign-in for every administrator, and activity logging you retain and review.
- Backups and restore tests
- HIPAA requires a data backup plan and a way to restore data (164.308(a)(7)); we recommend backups in a separate location and restores you have actually tested.
- Infrastructure or managed hosting
- On infrastructure you patch, monitor and respond yourself; with a managed host the provider runs part of that. Ask which safeguards each side runs.
Common mistakes
- Sending PHI to services outside the BAA — logging, analytics, error tracking or transactional email.
- Copying production patient data into test environments.
- Storage buckets or databases left open to the internet.
How we compare
- BAA without a sales process
- You can put the BAA in place yourself — it is included in standard terms or accepted in account settings — rather than requesting it and waiting for approval.
- Safeguards managed for you
- The provider configures and runs key safeguards — firewalls, encryption, logging, backups — instead of leaving them entirely to your team.
Requirements behind these criteria
- Business associate agreements (BAAs) →§ 164.502(e)
- Encryption of ePHI →§ 164.312(a)(2)(iv)
- Audit controls and activity logs →§ 164.312(b)
- Access control and sign-in →§ 164.312(a)(1)
- Security risk analysis →§ 164.308(a)(1)(ii)(A)