HIPAA-compliant hosting

HIPAA-compliant hosting: on AWS, Azure and Google Cloud.

Clarigo Infotech sets up and runs HIPAA-ready hosting for healthcare apps on AWS, Microsoft Azure and Google Cloud. All three providers sign a Business Associate Agreement covering a list of HIPAA-eligible services, but signing it does not make you compliant: how you configure those services is your responsibility. Our HIPAA-trained team builds the environment in your own cloud account with eligible services only, encryption with managed keys, least-privilege access, audit logging, tested backups and monitoring, documents it all, and supports it 24/7.

Share

10+

Years of delivery

600+

Projects delivered

20+

Countries served

25-30

Days to a live MVP

Get a free consultation

Tell us what you need. A senior engineer replies within one working day.

How should we contact you?

No obligation. We reply within one working day.

What we do

What our HIPAA hosting service covers

BAA and service selection

Accept the provider's BAA in your account and design the system so PHI only touches services on its HIPAA-eligible list.

Secure network and access

Private networks, least-privilege roles, multi-factor sign-in and no shared administrator accounts.

Encryption

Encryption at rest with managed keys and TLS in transit for every database, bucket, queue and connection that carries PHI.

Audit logging and monitoring

Cloud audit logs, application access logs and alerts, kept in protected storage where they cannot be quietly edited.

Backups and recovery

Automated, encrypted backups with regular restore tests and a written recovery plan.

Migration and 24/7 support

Move existing apps into the new environment, then patch, monitor and respond to incidents around the clock.

In depth

How we approach HIPAA-compliant hosting

The shared responsibility model

The cloud provider secures its data centers, hardware and the underlying service. You secure what you build on it: who can access what, network exposure, encryption settings, logging, patching and your application code. A BAA covers the provider's part only. A public storage bucket holding PHI is your misconfiguration, not the provider's breach, which is why setup and ongoing review matter as much as the contract.

Eligible services only

Each provider publishes which services are covered by its BAA, and the list changes over time. Before a new service is used for PHI, we check it is on the current list for that provider. Services that are not covered can still be used for parts of the system that never see PHI, such as a marketing site, if the boundary is clear and enforced. We document that boundary so reviewers and new engineers can see it.

Encryption is addressable, but expected

Under the Security Rule, encryption is an addressable specification, so you must implement it or document why an equivalent measure is reasonable. In practice, encryption at rest and in transit is the expected baseline for cloud PHI. Encrypting to HHS guidance also matters for breach notification, because properly encrypted data is not treated as unsecured PHI. A lost backup or exposed disk that was encrypted, with the keys kept safe, is far less likely to become a reportable breach.

Logs, backups and documentation

The Security Rule requires audit controls and contingency planning, including data backup and disaster recovery. We turn on provider audit logs such as AWS CloudTrail, Azure Monitor activity logs or Google Cloud Audit Logs, add application-level access logs, and test restores. HIPAA requires security policies and documentation to be kept for six years, so we write the runbooks as we build.

Process

How it works

Week 1: discovery and PHI mapping

We map every place patient data is created, stored and sent, agree the minimum data each feature needs, and confirm BAAs with every vendor that will touch PHI.

Weeks 2-3: build and integrate

Senior engineers build in short sprints with access control, encryption and audit logging from day one, connect your EHR and other systems, and demo every week.

Week 4: test, security checks and launch

We test with realistic de-identified data, run security checks on access, logging and encryption, fix what they find, then deploy to your own HIPAA-eligible cloud account.

After launch: 24/7 support

The same team stays on with 24/7 support, monitoring, patching and new features, and keeps the security documentation up to date as the product changes.

FAQ

Questions we hear most

Is AWS, Azure or Google Cloud HIPAA compliant?+

Each offers a BAA covering a list of HIPAA-eligible services, but no cloud is compliant on its own. Compliance depends on using eligible services for PHI and configuring access, encryption, logging and backups correctly, which is the customer's responsibility.

Is signing the cloud provider's BAA enough?+

No. The BAA covers the provider's obligations. You still need eligible services, secure configuration, a risk analysis, policies, workforce training and monitoring. We handle the technical setup and documentation and help with the rest.

Whose account does the hosting run in?+

Yours. We build in your own cloud account under your own BAA with the provider, so you keep control of the data, the bills and the access. Our engineers work in it with named, least-privilege accounts that you can review or remove at any time.

Can you move our existing app to HIPAA-ready hosting?+

Yes. We review the current setup, design the new environment, migrate data with encryption in place and switch over with a rollback plan, then provide 24/7 monitoring and support for the new environment.

Is encryption required by HIPAA?+

Encryption is an addressable specification under the Security Rule, so it must be implemented where reasonable and appropriate, or the reason and an equivalent measure documented. For cloud-hosted PHI, encryption at rest and in transit is the expected practice.