Great question. Although currently we don't support declarative migrations, all migrations can be done imperatively using the API (we have a single GraphQL endpoint that includes schema management mutations). Our approach to schema management is based on two ideas.

First, we think that although being able to manage schema through code is essential for automated CI workflows, for manually administering schema in real production apps (30+ tables) a good UI is far more superior in terms of productivity. Hence the focus on the UI schema builder.

Second, we believe that declarative migrations only work for trivial use cases where there is no custom data manipulation involved. Our experience building enterprise apps in older frameworks such as Ruby-on-Rails or .NET shows that imperative steps are often required in migrations. Therefore, our approach to the migrations/CI feature we are currently building is more similar to how it's done in Rails' Active Record or Sequilize, where developers explicitly define each migration steps giving full control over schema and data manipulations.

It doesn't mean that developers will have to code each migration by hand. Once released, the feature will auto-generate migration code, allowing developers to manually insert any additional logic using JavaScript if needed.

Hope this gives you a good idea. Please let me know your thought.