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.
Multi-tenant PostgreSQL
Multi-tenant PostgreSQL means that multiple projects or organizations share database infrastructure. Data can be separated into databases, schemas or rows with access policies. Each approach needs authorization, credential management and operational controls appropriate to the application.
VULK's managed application backend provisions a separate database per project on a shared PostgreSQL service hosted on Hetzner in Falkenstein, Germany. The backend API resolves the project and applies its authentication and table-access policies. Each project database lives on the shared PostgreSQL service, and the application's policies set which tables are public and which require authentication.
The main VULK database on AWS RDS in Frankfurt stores platform records, Studio conversations and project source. Its location and backup configuration describe that main database; an application's managed database is the separate Hetzner service described above. External backends and integrations have their own scope.
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 SaaS pricing pattern where new users start on the full paid plan at a low intro price for a fixed window, then continue at the standard rate. VULK can start selected plans with a short paid entry period, switched on and off per plan.