Limits and roadmap - Pawabase

Not managed from code yet

Environment-level settings are done in Studio:

Setting	Where in Studio
Sign-in methods, providers, password policy, MFA, sessions	Users & auth (Configuring Auth)
Secrets	Access → Secrets
API keys	The environment’s API keys page
Custom domains	Settings
Alarms, status page	Project → Activity, Status page
Dashboards	Data / Dashboards
Backup schedules	Project → Backups
Mail provider (delivery) and storage connection	Mail → Delivery, environment settings
Users and their roles	Users & auth → Users

These are mostly secrets and operations, which are kept out of code on purpose. merge mode leaves them alone, so you can manage them in Studio and everything else in code with no conflict.

Behaviours to know

Columns are only added. A deploy never drops or retypes a column (Migrations).
Secrets are write-only, so plan can’t tell if one changed; use --force-secrets to resend.
The visual mail design is Studio-only.
Emulation is a simulation of the plan, not a running backend.

Language support

Infrastructure as code is available for Python today. A TypeScript package with the same concepts is planned; every page shows examples in a language tab so the TypeScript version will appear beside the Python one.

Overview

Back to the start.

Management client

For scripts.