Blog
Run your backend on AWS Lambda, step by step
Run your backend on AWS Lambda as one container image. Config and functions load from S3, Postgres can live anywhere, and your frontend keeps supabase-js.
Dev, staging and prod from one instancez.yaml file
Promote one instancez.yaml from dev to staging to prod: per-environment values and secrets from env vars, migration previews, a drop guard and typed clients.
Declarative Postgres migrations without migration files
How instancez migrates Postgres from one YAML file: diff and apply, previewing the plan, renamed_from for renames, a guard on drops and a lock timeout.
RLS policies in YAML, checked in CI with inz vet
Write Postgres row-level security as YAML in instancez.yaml, then run inz vet in CI to catch open policies before they ship, including agent-written ones.
-
Run your backend on AWS Lambda, step by step
-
Dev, staging and prod from one instancez.yaml file
-
Declarative Postgres migrations without migration files
-
RLS policies in YAML, checked in CI with inz vet
-
Switch from Supabase to instancez: CLI and code examples
-
Local Supabase without Docker: inz dev --embedded-pg
-
Supabase alternatives in 2026: 8 backends compared
-
A backend for coding agents: one YAML file to review
-
Self-host a backend in one binary: VPS, Docker, Kubernetes
-
One YAML file backend: tables, RLS, auth and functions
-
Get started with instancez, a self-hosted Supabase alternative