Row-level isolation
Multi-tenant workspace isolation is enforced with Postgres row-level security in Supabase.
Security
Each control below is in place in Vertica today. Where you can check one yourself, the card says where.
Access and isolation
Multi-tenant workspace isolation is enforced with Postgres row-level security in Supabase.
Each user can add an authenticator app (TOTP) to their own login, and remove it again.
Where: Settings › Security
Infrastructure
The application runs on DigitalOcean, the database is on Supabase, and DNS and edge delivery use Cloudflare.
Payments use Stripe Checkout, so card data does not touch Vertica servers.
Transactional email is delivered through Resend.
Application controls
An integration key you connect, such as your Mailchimp API key, is encrypted with AES-256-GCM before it is stored.
Where: Settings › Integrations
Membership, billing and support activity is recorded per workspace, including every action Vertica support takes in it. Owners and admins can read it.
Where: Settings › Data & access
Vertica enforces a Content-Security-Policy and additional security headers.
The workspace owner deletes it by typing its ID and confirming. It disappears at once and is purged after 30 days; until then support can restore it.
Where: Settings › Data & access
Vendors
Customer content is sent to AI providers (Anthropic, Perplexity and Firecrawl) solely to produce the output you request. Every vendor that processes customer data is listed below with what it handles; regions are on the vendor disclosure; uptime is on the live status page.
Request access
Registrations are invite-only. Request your demo instance and we'll set up a workspace for your firm.