Skip to main content
Reactor protects partner model weights and intellectual property with security controls across storage, access, and transfer. Your models stay confidential, isolated, and under your control.

​
Customer data ownership

Partners retain full ownership of their model weights and container images. Reactor does not access, use, or derive from partner weights for any purpose beyond serving the partner’s own workloads.

​
Data deletion

Partners can delete a model at any time with reactor model delete or the API. Deletion takes effect immediately from the partner’s perspective and cannot be reversed:
  • Model records: The model and its releases leave every read surface at once. The server keeps a tombstone so the name stays reserved, and a deleted model cannot be recovered.
  • Weights and container images: Retained in isolated, partner-scoped storage for audit, then garbage-collected. They are never served, listed, or reused after deletion.

​
Encryption

All data is encrypted in transit and at rest.
  • In transit: All API and data transfer connections are secured with TLS. Presigned URLs embed cryptographic signatures. Raw AWS credentials are never exposed to partners or intermediaries.
  • At rest: Model weights stored in S3 are protected with AES-256 server-side encryption. Container images in ECR inherit AWS-managed encryption by default.

​
Tenant isolation

Partner resources are isolated at the infrastructure level, not just the application level.
  • Storage: Each partner’s weights are stored under a dedicated S3 prefix (reactor-models/<partner>/<model>/<version>/). There is no shared storage namespace between partners.
  • Container registry: Each partner pushes to a namespaced ECR repository with IAM policies scoped exclusively to their namespace. Partners cannot read, list, or write to other partners’ repositories.
  • Runtime access: Model access is deny-by-default. Only explicitly authorized accounts can create sessions with a partner model, enforced at the API layer.

​
Credential security

Reactor uses short-lived, scoped credentials throughout the partner workflow. No long-lived shared secrets are issued. Partners never receive credentials that grant access to other partners’ resources or to Reactor’s internal infrastructure.

​
Secure weight transfer

The CLI uploads weights through scoped presigned PUT URLs. Data flows directly from the partner machine to Reactor’s storage; it never transits the Reactor backend.

​
Access control

Partner models are gated by a deny-by-default access policy. Access is granted per-account and enforced at the session creation API. Even internal Reactor users cannot access a partner model without explicit authorization.

​
Compliance and roadmap

Reactor’s infrastructure runs on AWS, inheriting AWS’s SOC 2, ISO 27001, and HIPAA-eligible infrastructure controls. We are working toward SOC 2 Type I certification for the Reactor platform.