Before
Keep Hub, Cube, Redis, storage, PostgreSQL major and existing credentials. A self-hosted Cloud bridge
is not required. Prepare the target configuration before maintenance.
First v6 dependency setup
- Docker and one-click
- Kubernetes
These steps add bundled SpiceDB to an existing Compose installation. For external PostgreSQL or
SpiceDB, use SpiceDB operations and your platform’s credentials.The first command must exit successfully. Check all five new service names and the selected images
in the next two outputs. Resolve missing variables, files or YAML anchors before continuing.Follow Docker upgrade → Prepare migrations and permissions
after stopping writers and taking the backup. That step starts the following chain automatically:
1
Download the two release files
Open a terminal in the directory containing your existing Continue only if both downloads succeed.
docker-compose.yml and .env
(usually formbricks/ for one-click). Choose the latest stable 6.0 patch from
GitHub releases.
Reference files: Compose
and database bootstrap.
The commands below download both from the exact tag you select.docker-compose.release.yml is a reference to compare;
keep your existing docker-compose.yml. The script must sit beside it because Compose mounts
./authzed-postgres-bootstrap.sh into the bootstrap container.2
Create the two new secrets
Run this command twice, once for each missing secret:Save the two different results in your existing Replace both placeholders; do not paste
.env:openssl commands into .env. Protect it with
chmod 600 .env. Keep existing values if these secrets are already configured.AUTHZED_TOKENis the shared credential used by Formbricks and SpiceDB; no AuthZed account is needed.AUTHZED_DATABASE_PASSWORDis a new password for SpiceDB’s database login. Keep your existingPOSTGRES_PASSWORD, auth secrets and encryption key unchanged. If.envhas noPOSTGRES_PASSWORDyet, add the password your database already uses; older Compose files may store it directly.AUTHZED_SYSTEM_KEY=formbricksis an identifier, not another generated secret.AUTHZED_INSECURE=trueis only for the private Compose network; external endpoints should use TLS.
3
Add the services to your existing Compose file
Open
docker-compose.release.yml beside docker-compose.yml in your editor:- Copy
authzed-db-bootstrap,spicedb-migrate,spicedb,authzed-initializeandauthzed-opsunder your existingservices:key, including theirdepends_on, mounts and environment blocks. Keepprofiles: ["authzed-ops"]on the operations service. - Copy the referenced
x-formbricks-databaseblock at the top level and adapt its connection URL to your existing database. Copy the release’sAUTHZED_*bindings andSKIP_STARTUP_MIGRATIONsetting into the existingformbricks.environmentblock. Preserve its other settings. - Check
POSTGRES_ADMIN_URLonauthzed-db-bootstrapuses your existing PostgreSQL admin login. Keep the PostgreSQL image major, volumes and mount paths. Match the bootstrap client’s image to that existing major. Connect all new services to the same private network as PostgreSQL and the app. - Pin
formbricks,formbricks-migrate,authzed-initializeandauthzed-opsto your selected Formbricks tag. AddWEBAPP_URLwith your existing instance URL toauthzed-ops.environmentfor the permission preparation step.
.env alone does not add those bindings.
Keep your Hub, Cube, storage and proxy configuration. The one-click updater cannot add these services for you.4
Validate, then continue the maintenance procedure
authzed-db-bootstrapruns the downloaded script inside Docker. It creates thespicedbdatabase and login if missing, and sets that login’s password to your configured value.spicedb-migratecreates or updates SpiceDB’s internal tables;spicedbthen starts.- You run the separate Formbricks preparation command to migrate application data and populate permissions.
AuthZed database bootstrap completed., both setup containers must exit 0,
and SpiceDB must be healthy. Check with docker compose ps -a and
docker compose logs authzed-db-bootstrap spicedb-migrate. Stop on failure; keep the app stopped.Patch actions
Check each patch you cross. You can go straight to the latest 6.0 patch. Patches within 6.0 don’t change the permission schema, so you don’t run permission preparation for them.Upgrade
Follow the runbook for your setup: Kubernetes, Docker Compose or one-click. For this first v6 upgrade, the order matters:- Stop the app and workers, and back up.
- Start only PostgreSQL and SpiceDB.
- Run permission preparation with the 6.0 image. It runs the app’s
database migrations, then creates the permission data. It must end with
upgrade_prepared. - Only then set the v6 acknowledgement (
FORMBRICKS_AUTHZED_V6_MIGRATION_ACKNOWLEDGED=truein.env, orauthzed.migrationAcknowledged: truein Helm values) and start the app and Hub.
Check it worked
- Users can sign in, including existing SSO users, and see only what they should.
- A scoped API key works for what it’s allowed to do and is refused for everything else. A revoked permission stays revoked.
- Embedded Data, existing responses, charts, and old and new uploads work.
- Background jobs run.