Security at VantyRex
This page describes how we run and release our own systems, how the systems we build for you are protected, and how to report a vulnerability. Your contract states the security terms for your system.
Last reviewed 13 November 2026 · Owner: VantyRex
How we release our own systems
The service that runs our contracts, client portal and billing ships only through a recorded release gate. The gate:
- runs on a clean export of the exact commit being released, verified byte for byte against that commit;
- installs dependencies from the lock file, then runs type checks, lint and the full test suites; a skipped test fails the gate unless it is on a dated, recorded exception list;
- builds the site and the service, and type-checks, tests and synthesises the infrastructure definitions;
- audits dependencies for known vulnerabilities;
- scans the code and its history for secrets;
- builds the service image and proves that it starts.
Each run writes a record of the commit, every step and its result. A deploy is refused unless the commit being deployed holds a complete, passing record from the last 24 hours. After each deploy, an end-to-end check runs against the live service.
How we run our own systems
- Hosting. Our systems run on Amazon Web Services. The regions are listed on the sub-processors page.
- Storage. Encrypted at rest, versioned, with public access blocked and encrypted connections required.
- Databases. Point-in-time recovery and deletion protection are on for every table that holds business data.
- Contract and audit records. Executed contracts are kept in versioned, encrypted storage, and our service has no permission to delete them or change their retention. Changes to contracts and billing are written to a hash-chained audit trail, which is anchored every 100 events to separate storage under a seven-year retention lock that only a privileged override can lift.
- Network. A web application firewall sits in front of our service.
- Secrets. Kept in a managed secrets store, never in code; every release is scanned for them.
- Administrator access. Administrator sign-in requires two separate one-time codes, one by email and one to a registered phone.
- Client portal. Clients sign in without a password, with a one-time code sent to the email or phone on their agreement, and each client sees only their own projects.
- Signed agreements. Each executed agreement is sealed with a cryptographic hash, and both parties receive the executed PDF.
- Logs. Service logs are kept for 12 months; firewall and load-balancer logs for 90 days.
How your system is protected
- Release checks in your contract. The tests, security checks, and accessibility and performance targets for your system are written into your statement of work. Each release is accepted against them, and you receive its record.
- Where your data lives. Your system's data is hosted in the cloud region your law requires, and that region is named in your contract. Before you sign, you receive the list of services your system will use and where each one runs. If no available region meets the requirement you give us, we tell you before you sign.
- Access. We work in your accounts with the access you grant, limited to what the work needs, and you can withdraw it at any time. At the end of a service, our access is removed and confirmed to you in writing.
- Secrets. Your system's secrets are kept in a managed secrets store in your accounts, never in code.
- Penetration testing. If your procurement requires a third-party penetration test of your system, we scope it with you and quote it in writing.
What we do not have
VantyRex does not hold SOC 2 or ISO 27001 certification. We do not run a paid bug bounty. We answer your security questionnaire in writing before you sign.
Reporting a vulnerability
Use the form below. Tell us what you found, where, and how to reproduce it, and give an email address for our reply.
- Please give us reasonable time to fix the issue before you disclose it, access no more data than you need to show the issue, and do not disrupt our service or anyone's data.
Our machine-readable contact is at /.well-known/security.txt.