Studio is the fastest way to explore and change a project. Tools are for when you want changes to be code: reviewed in a pull request, repeatable across environments, and applied by a pipeline instead of by hand.
Infrastructure as code is available for Python today (pawabase-iac). Every example is written in a tab so a TypeScript tab can sit beside the Python one when that package ships; the concepts, commands and files are the same.

​
Studio and code are the same thing

A definition made in Studio and the same definition made in code are identical data. You can:
  • Start in Studio, move to code: build something visually, then recreate it in code and use pawabase plan to confirm there are no differences.
  • Start in code: deploy, then open Studio to see what was created and watch it run.
  • Mix: keep some things (users, secrets, provider keys) in Studio and the rest in code. merge mode (the default) never deletes what your code doesn’t mention.

​
Which tool for which job

Infrastructure as code

Your backend, in Python.

Quickstart

Deploy something in ten minutes.

Management client

Scripts with a secret key.

CI/CD

Deploy on merge.