Skip to content

Security

Security, built into every layer.

Row-level security on the tables Vorx writes, encrypted backend credentials, and a security scan before every publish — on every plan, without configuration.

Application security Data security Infrastructure security Pre-publish scan

Secured on every front

Independent layers of protection work together to reduce risk at every level.

Application security

Secure as it's built

Every table Vorx writes gets row-level security, and secrets stay server-side. Before every publish, a security scan runs. A live credential in the built app, a table with row-level security off, or a sign-in check kept inside the page stops the publish. Other findings are shown to you first.

Data security

Locked down by default

Your app's backend credentials are encrypted (AES-256-GCM). The secrets you add are write-only: Vorx keeps their names, not their values. You can restore your app's code to an earlier checkpoint.

Infrastructure security

The same stack, whatever you pay

Every app with a backend gets its own database, in its own Supabase project. Every plan gets the same setup, including the free one, because running two standards would mean one of them is the worse one.

Pre-publish scan

Checked before you ship

Before every publish, Vorx checks the live database for tables without row-level security or open to the public key, scans the built app for exposed secrets and credentials, flags common XSS patterns in the source, catches a sign-in check kept inside the page, and audits the app's dependencies for known vulnerabilities — the mistakes a generated app is most likely to make.

Your work stays yours

The things that matter most to your business never leave your control.

Not used to train our models

Vorx does not train AI models on your code, prompts, or workspace data. To answer a request, they are sent to the AI model providers named on our Subprocessors page, which handle them under their own data policies.

Where your data lives

Your workspace and project data is stored on Google Cloud in the United States, and app databases we manage run on Supabase in the United States by default. Every provider that handles your data is listed on our Subprocessors page.

Separate by design

Every app with a backend has its own database, and every table Vorx writes has row-level security scoped to your organisation.

The controls you get today

We're an early-stage company, so we'd rather be straight with you about what exists now. Everything here is in the product today, on every plan.

Role-based access

Role-based permissions for viewing and editing, so the right people have the right access.

Pre-publish security scan

Every publish is scanned before it goes live, and you see what the scan found.

Secrets stay server-side

Backend credentials are encrypted. The secrets you add are write-only: Vorx keeps their names, not their values.

A database per app

Every app with a backend gets its own database, in its own Supabase project.

Shipping your first app? You're already covered.

Every app you build on Vorx gets the same protections as every other — from your very first publish, with nothing to configure.

  • A security scan runs before every publish
  • Role-based access controls limit who can view, and who can edit and publish
  • Version history lets you restore your app's code to an earlier checkpoint

Talk to us about security

Need details for a vendor review or security questionnaire? We're happy to walk your team through how Vorx protects apps and data.

Encrypted backend credentials
A database per app
Secrets stay server-side
Pre-publish security scan
Contact us about security

Frequently asked questions

Your workspace and project data is stored on Google Cloud in the United States. App databases we manage run on Supabase in the United States by default, and live previews run on Fly.io in the United States. Every provider that handles your data, and what it does, is listed on our [Subprocessors](/subprocessors) page.

Every app with a backend gets its own database, in its own Supabase project. Every table Vorx writes has row-level security scoped to your organisation, and the pre-publish scan checks that it is still switched on.

Your app's backend credentials are encrypted (AES-256-GCM) in Vorx's database. The secrets you add go to your app's backend provider and are write-only: Vorx keeps their names, not their values, and the pre-publish scan looks for credentials left in the built app.

Yes. A security scan runs automatically before every publish. It checks the live database for tables without row-level security or open to the public key, scans the built app for exposed secrets and credentials, flags common XSS patterns in the source, catches a sign-in check kept inside the page, and audits the app's dependencies for known vulnerabilities. A live credential, a table with row-level security off, or a sign-in check kept inside the page stops the publish; other findings are shown to you first.

Vorx does not train AI models on your prompts, code, or workspace data. To generate and edit your app, they are sent through OpenRouter to the model providers listed on our Subprocessors page, which process them under their own data policies.

Email [legal@vorx.com](mailto:legal@vorx.com) with what you found and how to reproduce it. Please give us a reasonable chance to fix it before you share it publicly. Our contact details for security researchers are also published at [/.well-known/security.txt](/.well-known/security.txt).

Yes. If you need details for a vendor review or security questionnaire, contact us and we'll walk you through our practices.

Know what you are shipping

Row-level security on every table Vorx writes, and a scan before every publish. Read the code, check the rules, decide for yourself.