VectorKan
Multi-tenant data isolation and TenantId enforcement
Database query filtering
Every tenant-specific table in PostgreSQL contains a non-nullable TenantId foreign key. In the application's VectorDbContext, global query filters are automatically applied to all queries:
// Applied automatically across all tenant-scoped queries
builder.Entity<TEntity>().HasQueryFilter(e => e.TenantId == CurrentTenantId);API and portal isolation
Even public customer intake portals and API keys are scoped strictly to their respective tenant. A request token or API key can only resolve data belonging to its originating workspace.
More guides in Security & governance
An overview of VectorKan's security architecture, HTTPS encryption, STQC & CERT-In aligned headers, multi-tenant boundaries, and password hashing.
Configure password policies, session security, lockout thresholds, and two-factor authentication (2FA).
Details on TLS encryption, cipher suites, HSTS preloading, and CSP protection across VectorKan web and API endpoints.
Learn how production database backups, point-in-time recovery, and multi-zone persistence protect your workspace against data loss.
Learn what happens when an account or workspace is deleted, data purge timelines, and retention rules.