Flynn cofounder here. The primary difference between Flynn and cloudfoundry, dawn, deis, dokku, octohost, openshift, tsuru, etc is that Flynn is designed to run everything itself, not just 12 factor web apps. Most immediately this means that you can run databases inside of Flynn alongside other apps. In fact we've already wrapped up postgres.
Flynn also tries to be more technology agnostic, for example we don't depend on CoreOS or Docker.
It's worth noting that several of the other platforms including Deis claim to be production ready today while Flynn is still a few months out.
The difference in both features and goals will be a lot clearer in the coming months. What we have today is just the foundation and minimum viable feature set. Once that's rock solid, the real work gets started.
Very different companies and both have been doing their thing for a bit. A small subset of people may confuse them, but it should be very clear right away from seeing their sites that one is what I'll call a "product based company" while the other is an online store.
From the CC license: "NonCommercial means not primarily intended for or directed towards commercial advantage or monetary compensation."
I'm definitely not a lawyer and would like to hear from one interpreting the license for this use case, but it sounds like that could be interpreted to mean not okay to use for a business if it generated a commercial advantage, like HIPAA compliance.
Clarification from your lawyer (published on your site) would be good if you aren't okay switching to a more permissive license.
Suggestion: name them "FREE HIPAA DOCS AVAILABLE AT [URL]" and use a license requiring attribution, should make them hard to resell?
In the simplest sense it's an open source Paas (think Heroku), but with much more flexible technology. It's designed for ops teams who can run a single platform instead of doing custom deployment work for each application and database
The ops team at a company is the group responsible for running and scaling the apps after they've been written. The role varies from company to company, but in general they manage databases, underlying infrastructure, and other technology that power apps.
You could think of them as the sysadmins or IT team that powers especially public-facing services and websites. Think Twitter, HN, etc. The people in charge for making sure there are no fail whales are the ops team.
This is a nitpick, but it really turns me off from coming back to applications, and I'd want to know about it if I were you: after I registered on dashboard.flynn.io, neither the password remembering functionality built into chrome nor my password manager (LastPass) seems to know how to autofill your login form. I haven't looked into why that would be at all, but it's a real nuisance!
"Non-cooperating services often use service discovery information in configuration, such as the backends for a load balancer defined in an HAproxy configuration. A generalized configuration rendering system is used to tie service discovery into most non-cooperating services."
The problem is to generate the config file, which etcd doesn't help.
One thing that I really like with other PasS companies is that they package that content up -- setup, architecture, documentation of a n-tier application (I am assuming you already built something like that for contracting work). How would I create a website with database and caching ect... using your services.