Skip to content

Security and shared responsibility

Varity Team Core Contributors Updated June 2026

Security is a partnership between Varity and you. This page explains what Varity protects, what you are responsible for, and how to reach us about a security issue.

  • Encryption in transit: all traffic between you, Varity, and your deployments is encrypted with TLS, with HTTP Strict Transport Security enforced.
  • Isolated secrets: environment variables and credentials are injected at runtime, never built into images, and never written to logs.
  • Account isolation: every account is isolated from every other account.
  • Hardened deploy path: inputs to the build and deploy pipeline are validated to prevent injection and server-side request forgery.

Varity owns

The platform and control plane: edge encryption, routing, the deploy pipeline, secret injection, and patching our own services.

Infrastructure owns

The underlying hosts: physical security, the host operating system, and container-runtime isolation. Varity selects and continuously evaluates providers.

You own

Your application: your code and dependencies, your in-app authentication, the secret values you set, and the data your app stores.

  • Keep your application dependencies up to date.
  • Implement authentication and authorization inside your own application.
  • Treat the environment variables you set as sensitive, and rotate them if they are ever exposed.
  • During beta, keep your own backups of business-critical data.

Found a security issue? Email security@varity.so. Please report it responsibly and do not open a public issue. We aim to acknowledge reports within 48 hours and will keep you updated on remediation.

We are transparent about what is in place today versus what is coming. In active development: platform-managed encryption at rest, tamper-evident audit logging, and team accounts with role-based access control.