Catalyze vs tsuru: What are the differences?

Catalyze: HIPAA-compliant cloud computing for healthcare. Cloud tools for healthcare. We provide a HIPAA-compliant Platform as a Service (PaaS), HIPAA-compliant Mobile Backend (BaaS), and HL7 integration services. Focus on building your digital health app, and not on compliance. Think of us as your healthcare-specific DevOps team; tsuru: Extensible and open source Platform as a Service software. tsuru is an open source polyglot cloud application platform (PaaS). With tsuru, you don’t need to think about servers at all. You can write apps in the programming language of your choice, back it with add-on resources such as SQL and NoSQL databases, memcached, redis, and many others. You manage your app using the tsuru command-line tool and you deploy code using the Git revision control system, all running on the tsuru infrastructure.

Catalyze and tsuru can be primarily classified as "Platform as a Service" tools.

Some of the features offered by Catalyze are:

• Platform includes everything for infrastructure-specific HIPAA compliance: dedicated logging, monitoring, encryption in transit and at rest, backups, disaster recovery, vulnerability scanning, intrusion detection, to name a few
• Mobile Backend includes a compliant datastore, user management capabilities, custom classes, and more
• Audited 3 times, 2 HIPAA and 1 HITRUST

On the other hand, tsuru provides the following key features:

• Fast and secure. The entire process is really simple with no special tools needed, just a simple git push.
• Scaling in Tsuru is completely painless. Just add a unit and Tsuru will take care of everything else.
• Tsuru is built to be extensible. Through services you can provide anything your application needs.

tsuru is an open source tool with 3.14K GitHub stars and 421 GitHub forks. Here's a link to tsuru's open source repository on GitHub.