Are there any plans on the roadmap to enable strict and solid data separation for development apps vs productive apps on a single Tulip instance or are you moving away form this idea in favor of the more classical n-dedicated-instances idea?
The idea would be for every table that is created in an instance Tulip would automatically also create a development mirror with the same configuration.
Apps in development would only use the development schema and data while productive apps would use the productive one.
This of course would require to keep track of any outstanding migrations, i.e. if an app depends on certain table changes, the user would first need to initiate those specific table migrations to move the from the development schema to the productive one.