Hacker News Reader

As someone building a healthcare application, it seems kind of risky to base my entire backend on a third party service that could change, go out of business, make their prices prohibitively expensive, etc. It would be really nice if there was a way for me to have a HIPPA compliant architecture while still using open source technology so if I need to switch off your platform I'm not stuck re-writing my entire backend.

View on HN

I agree that you should not be tied to any solution that you choose. From what you're describing, it seems as though you'd like the entire backend to be portable. From a BaaS perspective, as you can imagine, that's a bit challenging. What we have done there is to document our APIs well and will shortly give you the ability to export your data as well. What you might be more interested in is our PaaS solution (https://www.catalyze.io/platform-as-a-service/) - that will allow you to use Heroku buildpacks to deploy you service onto our compliant infrastructure = so essentially if it works on Heroku, it will work on the Catalyze PaaS (or vice versa). We're hard at work on this and have a couple customers using it. We hope to have a public release very very shortly.

Reply on news.ycombinator.com