# openEMR HIPAA Hosting

**URL:** <https://community.open-emr.org/t/openemr-hipaa-hosting/4757>\
**Category:** OpenEMR Development\
**Created:** [August 11, 2014, 3:45am UTC](https://community.open-emr.org/t/openemr-hipaa-hosting/4757 "2014-08-11T03:45:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [August 11, 2014, 3:45am UTC](https://community.open-emr.org/t/openemr-hipaa-hosting/4757/1 "2014-08-11T03:45:58Z")

</div>

**[moshegorin](https://sourceforge.net/u/moshegorin/)** wrote on [Monday, August 11, 2014](https://sourceforge.net/p/openemr/discussion/202506/thread/0783d3e4/#2cb2):

(I posted this originally in the “Help” forum by mistake but it belongs in the “Developers” forum)

Hi I have researched HIPAA compliant web hosting for several weeks and I would like to share my results with the community.

Based on my research Google Cloud seems to be the best in terms of price, hardware and flexibility. Runner up is [LuxSci.com](http://LuxSci.com)

1. Google Cloud - Google Compute, Storage and Cloud SQL are HIPAA compliant without any changes necessary. They will sign BAA for no extra cost. It looks possible to run openEMR on Google Compute/Storage/SQL (but NOT on Google App Engine because this is NOT HIPAA compliant). Pricing is flexible and it looks like openEMR for a small practice running 24/7 would be around $50 to $100 per month with backups.

Pros: Flexible pricing, no extra HIPAA fees, Google brand name  
Cons: Only 1 data center right now (in midwest); It’s a huge company so don’t expect to get much personal attention/support

1. [LuxSci.com](http://LuxSci.com) - They rent space on Rackspace and other networks to create HIPAA compliant infrastructure and you can host openEMR for only $15/month.

Pros: Very cheap for entry-level plan, small company with support  
Cons: Dedicated servers are expensive, $100 to sign BAA

1. Amazon Web Services - they charge $1,500/month minimum for a HIPAA compliant setup plus all regular fees (for EC2, S3 etc.)

Pros: Lots of data centers around the world  
Cons: $1,500/month minimum for HIPAA infrastructure

1. [Rackspace.com](http://Rackspace.com) - they require you buy a dedicated server for HIPAA compliance which starts at $500/month

Pros: Known for high quality  
Cons: $500/month minimum

1. Other Providers - All of these are small providers that offer HIPAA compliant dedicated servers for $100/month and up.

> **[HIPAA Compliant Managed Cloud - Hosting, Email, SFTP, Storage | VM Racks](https://www.vmracks.com/)**
>
> Leading Provider of Managed HIPAA Compliant Cloud Solutions including HIPAA Compliant Email, Hosting, Cloud Storage, and SFTP. Call 888-558-3645 today.

  
[OnlineTech.com](http://OnlineTech.com)  

> **[Compliant Hosting, Secure Colocation, and Cloud Services | OnRamp](https://www.onr.com/)**
>
> OnRamp provides compliant hosting & secure colocation, private cloud services to help you conquer your compliance challenges.

  
[Firehost.com](http://Firehost.com)

Pros: Small companies so good support  
Cons: Can be expensive & require long-term complex contracts, hardware is not as flexible as Google/Amazon

Please share your comments and experiences, thank you.

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [August 11, 2014, 7:29am UTC](https://community.open-emr.org/t/openemr-hipaa-hosting/4757/2 "2014-08-11T07:29:08Z")

</div>

**[kodusote](https://sourceforge.net/u/kodusote/)** wrote on [Monday, August 11, 2014](https://sourceforge.net/p/openemr/discussion/202506/thread/0783d3e4/#1ab9):

Dear Moshe,

Was Linode included in your evaluation and if so, what is your finding?

Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [August 19, 2014, 3:16am UTC](https://community.open-emr.org/t/openemr-hipaa-hosting/4757/3 "2014-08-19T03:16:14Z")

</div>

**[moshegorin](https://sourceforge.net/u/moshegorin/)** wrote on [Tuesday, August 19, 2014](https://sourceforge.net/p/openemr/discussion/202506/thread/0783d3e4/#1ab9/2cc6):

As far as I know Linode HIPAA compliant.

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [August 19, 2014, 3:21am UTC](https://community.open-emr.org/t/openemr-hipaa-hosting/4757/4 "2014-08-19T03:21:39Z")

</div>

**[moshegorin](https://sourceforge.net/u/moshegorin/)** wrote on [Tuesday, August 19, 2014](https://sourceforge.net/p/openemr/discussion/202506/thread/0783d3e4/#1ab9/2cc6/c2e5):

I mean: “As far as I know Linode is not\* HIPAA compliant”
