Multi-tenant PostgreSQL
A database architecture where many customer "tenants" share the same Postgres cluster but are isolated at the schema or row level. VULK uses schema-per-project isolation on AWS RDS PostgreSQL 16 in Frankfurt.
Multi-tenant PostgreSQL
Multi-tenant PostgreSQL is the practice of serving many isolated customers from a single Postgres cluster, using one of three isolation strategies: (1) database-per-tenant (strongest isolation, expensive), (2) schema-per-tenant (good isolation, cheap), or (3) row-per-tenant with tenant_id column + Row-Level Security (cheapest, weaker isolation). The right choice depends on tenant count, blast-radius tolerance, and migration cadence.
VULK runs schema-per-project on a single AWS RDS PostgreSQL 16 cluster in eu-central-1 (Frankfurt). Each project gets its own Postgres schema, so a buggy migration in one project cannot touch another, but all projects share the same instance for cost efficiency. Connection pooling is handled at the engine layer (vulk-api-engine) with PgBouncer. As tenants grow, hot projects are moved to dedicated instances without changing application code.
Auto-CRUD API
A backend pattern where Create / Read / Update / Delete endpoints are generated automatically from a database schema or entity manifest, instead of being hand-written per resource. VULK uses auto-CRUD via vulk-api-engine.
Reverse Trial
A pricing pattern where new users get full access to a paid plan for a short window — at a low introductory price — and downgrade or cancel at the end. VULK uses Reverse Trials at €1.99 / 7d (Builder) and €3.99 / 7d (Pro).