Your database.
Your infrastructure.
Connect SCHMA to your PostgreSQL database. Model and manage structured content while keeping your data in infrastructure you control.
Your data shouldn't be tied to your CMS.
Traditional content management systems treat your database as proprietary storage, metering database size and restricting direct access. SCHMA is built on a different model: your database stays in your infrastructure, and SCHMA provides the workflow layer around it.
Decoupling the content workflow plane from persistent database storage transforms reliability, cost predictability, and developer autonomy.
Infrastructure sovereignty
You control the PostgreSQL database that stores your content. Host on Supabase, Neon, AWS RDS, Railway, or self-hosted servers with root access, firewall rules, and your own hosting accounts.
Capacity independence
SCHMA does not impose a database-size quota on customer-owned PostgreSQL. Storage limits, row counts, and IOPS are governed entirely by your database provider—with no markups or artificial caps.
SQL coexistence
Content lives in standard relational tables inside your schema. Editorial teams manage structured content in Studio, while developers query tables directly using standard SQL, ORMs, and existing tools.
Your database. SCHMA's content workflow.
Your PostgreSQL instance stores all content payloads and revisions as standard relational tables. SCHMA connects over encrypted TLS to orchestrate schema modeling and editorial workflows, while serving published content through an edge-cached delivery layer that shields your database from frontend read volume.
Customer PostgreSQL
Your HostSCHMA Engine
Control PlaneConsumers & Frontends
Client TierCustomer PostgreSQL
01 / PersistenceSCHMA Engine
02 / OrchestrationConsumers & Clients
03 / Client TierIf you disconnect SCHMA, your content remains in standard PostgreSQL tables in your database. Zero proprietary conversion or export lock-in.
SCHMA stores connection credentials encrypted at rest and never assumes exclusive custody or operational restriction over your database instance.
Join content tables directly with internal user or product records using standard SQL queries without routing through CMS APIs.
Your database. Your limits.
SCHMA supports two database ownership models: connect your own PostgreSQL infrastructure with zero database-size quotas from SCHMA, or use managed PostgreSQL provisioned by SCHMA with plan allocations. Media storage and delivery API requests are accounted separately.
Customer-Owned PostgreSQL
Unmetered StorageConnect your existing cloud or self-hosted database. You retain direct SQL query access, complete data custody, and provider-managed backups.
SCHMA-Managed Storage
Turnkey HostingTurnkey hosting for teams who prefer not to manage external PostgreSQL infrastructure. Automatically provisioned and maintained by SCHMA.
Storage capacity, disk limits, compute, and IOPS auto-scaling are governed strictly by your database provider (Supabase, Neon, AWS RDS, Railway).
Automated TLS setup, schema migrations, and daily maintenance without configuring external cloud database infrastructure.
Zero database-size quota on Free and Pro. Pro adds host migration tooling, multiple connection targets, and audit logging.
Fixed database storage allocations: 100 MB on Free and 1 GB on Pro.
You retain direct SQL query access via psql, Prisma, Drizzle, and BI tools. If you disconnect, data stays in your database.
Export structured content records anytime via delivery APIs and standard JSON formats with zero platform lock-in.
SCHMA requires a customer-owned PostgreSQL 15+ database with the pgvector extension installed and enabled, and standard SSL/TLS. Supports direct port 5432 or transaction poolers on port 6543.
Provisioned automatically with managed connection poolers and zero external networking configuration required.
Media library assets (images, documents, and static uploads) are served from global CDN object storage and accounted separately from PostgreSQL database storage. Media uploads do not consume database disk space.
Published content queries are edge-cached globally with standard cache headers. REST (/v1/delivery/entries) and GraphQL endpoints share workspace monthly request allowances.
From connection to delivery.
A practical technical progression that fits directly into your developer stack without proprietary wrappers or opaque abstractions.
Connect your database
Provide your PostgreSQL connection string over SSL during workspace initialization. SCHMA creates dedicated public.schma_* tables, leaving your application schemas untouched and ready for content modeling.
Model structured schemas
Define content types visually in Studio using canonical field types, validation rules, and relations. Staged migrations generate dynamic editorial forms for your team.
Author and publish entries
Editorial teams compose content with live drafts and immutable version history written to your PostgreSQL instance. Committing entries invalidates the edge cache for instant delivery.
Deliver via edge APIs
Query published content using the @schmadev/client TypeScript SDK, REST (/v1/delivery/entries), or GraphQL endpoints with global edge caching and automatic type safety.
import { createClient } from "@schmadev/client";
// Initialize client with environment credentials
const schma = createClient({
apiKey: process.env.SCHMA_DELIVERY_KEY!,
workspace: "production",
});
// Fetch published entries backed by your PostgreSQL database
const { data: articles } = await schma.delivery.listEntries({
type: "article",
limit: 10,
populate: ["author"],
});
console.log(articles[0].title); // Fully typed responseClear ownership. Clear responsibilities.
An explicit division between the database infrastructure you operate and the content management and delivery services SCHMA provides.
Customer responsibilities
Infrastructure DomainDatabase hosting, compute, networking, and data governance
SCHMA responsibilities
Control & Delivery PlaneContent orchestration, schema migrations, and edge delivery
You operate the database host account (Supabase, Neon, AWS RDS, Railway, or self-hosted) and manage storage capacity, compute resources, and disk scaling.
Database connection strings are encrypted at rest using AES-256-GCM and accessed solely to perform authorized content operations.
Database backups, WAL archiving, retention policies, and disaster recovery procedures are configured and executed by your database provider.
SCHMA applies non-destructive, idempotent DDL updates confined strictly to dedicated public.schma_* content tables.
You configure SSL enforcement, IP allowlists, firewall perimeters, and connection routing (direct port 5432 or transaction poolers).
Published content is cached and served across global edge nodes with standard cache headers (s-maxage=60), insulating your database from read spikes.
You maintain full control over custom application schemas, user permissions, and direct SQL queries without CMS interference.
Content events dispatch outbound webhooks with cryptographic HMAC-SHA256 signatures, timestamp verification, and exponential retry handling.
Frequently asked questions.
Your database. Your workflow.
Your next step.
Connect your PostgreSQL database to SCHMA and manage structured content within the infrastructure you already run.