Your content. Your PostgreSQL database.
Connect your own PostgreSQL database to SCHMA. Keep your structured content, version history, and pgvector embeddings in infrastructure you own.
SCHMA Studio
Model, edit, and publish
Your PostgreSQL database
Content types and entries
Supabase · Neon · PostgreSQL
Choose a supported provider. Manage hosting and backups on your terms.
Choose the database behind your content.
SCHMA encrypts your connection string with AES-256-GCM in the control plane and provisions all schma_* data-plane tables directly in your database.
Works with Supabase, Neon, Railway & PostgreSQL 15+
Connect a customer-owned PostgreSQL 15+ database with the pgvector extension enabled during onboarding. SCHMA automatically runs idempotent data-plane migrations.
Multi-environment schema isolation on Pro & Max
Isolate staging and development environments inside your database using dedicated PostgreSQL search_path schemas.
Encrypted credentials & Site Lock protection
Connection strings are encrypted at rest and redacted from logs. Free workspaces bind to their initial database; Pro and Max unlock audited database switching.
Bring Your Own Database (BYOD) is included on Free, Pro, and Max. Multi-environment schema isolation and database switching require Pro or Max.
View pricingA few useful details.
Does the SCHMA subscription include my database hosting?
No. You connect a PostgreSQL database that you own and manage through your provider (such as Supabase or Neon free/paid tiers).
Who manages backups?
Because your content lives in your own PostgreSQL instance, you control point-in-time recovery (PITR), snapshots, and backups directly through your database provider.
Keep exploring.
Your next idea deserves a better content workflow.
Start with a model. Bring your team. Build the experience you have in mind.