Disclosure - I’m one of the engineering team at OiO. Now, that aside… :) With the definition of “lock-in” that you’re using, it’s very difficult to find any se

Disclosure - I’m one of the engineering team at OiO. Now, that aside… :) With the definition of “lock-in” that you’re using, it’s very difficult to find any service that doesn’t cause the user to be “locked in”. There is always a cost to migration from one service to another. That cost might be code changes to support a new API or it might be capital expenditures to spin up a cluster of a bunch of different databases to provide the same functionality, or it might be the cost of hiring a specialized team of ops engineers to run said cluster..or all of the above. :) So, yes, there is a significant tradeoff if you choose to use OiO - you are trading off the cost of building and maintaining a large system of databases for the convenience and speed of development. Even if we open sourced all the code to run the IaaS portion of our system, you’d still have to find the hardware and manpower to run it...and keep it running over the long term. Once you’ve built up your own expertise, you would pay AGAIN if you chose to migrate to something else. There is no free lunch. Every action entails choice and consequence, but Orchestrate is committed to ensuring data portability and freedom to our users as much as possible, with the hope that they will love it enough to stay and use for a long time to come.