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.
Auto-CRUD API
Auto-CRUD is the pattern of generating REST (or GraphQL) endpoints — POST, GET, GET /:id, PATCH, DELETE — directly from a schema definition rather than writing controllers by hand. It enforces consistency (every resource has the same shape), eliminates boilerplate, and pairs naturally with role-based permissions declared at the entity level. PostgREST, Hasura, and Supabase popularized the pattern for self-serve developers.
VULK delivers auto-CRUD through vulk-api-engine. When the generation agent emits a project that needs persistence, it produces an entity manifest (entities, fields, relations, roles) — not handwritten Express routes. The engine reads the manifest, provisions a project database on the managed PostgreSQL service, and exposes endpoints under /api/{projectId}/{entity}. Auth, JWT validation, and field-level permissions are layered on top automatically. The frontend talks to the API via a generated typed client.
See /docs/api/overview.
BYOM (Bring Your Own Model)
A pricing pattern where the user supplies their own API key for the underlying LLM provider (OpenAI, Anthropic, Google, OpenRouter) and the platform passes the model cost through at zero markup. VULK supports BYOM on Pro and above.
Multi-tenant PostgreSQL
How projects can share PostgreSQL infrastructure while using separate databases, schemas or row-access policies, and how VULK's managed backend stores application data.