execution isolation
The execution architecture uses per-job Firecracker guests with declared resources and a controlled dependency path. A fresh execution boundary is part of the workload contract.
security overview
Sorus uses isolated execution, scoped credentials and controlled network access. Request release-specific evidence and data-handling terms during beta onboarding.
tenant and caller identity
Customer operations are attributed to a tenant and principal. People and agents use separate credentials; roles and scopes limit what callers can do.
source and artifacts
The client selects source explicitly under the source-transfer rules. Retrieved artifacts are verified and never silently overwrite an existing destination. Don't upload credentials as source.
network access
The candidate execution scope does not offer unrestricted outbound internet. Check dependency, registry and service requirements before moving a job.
what to establish before production use
Ask for the qualified release scope, hosting and processing locations, data-handling and deletion terms, incident contact, subprocessors and any contractual requirements your company has.
SOC 2 certification, audit attestation and an availability SLA are not offered on this site. Confirm any required commitments in your beta agreement.
Read the customer security guide, or contact Sorus to discuss an evaluation. For a suspected vulnerability, begin with a brief description and request a private reporting channel. Do not send credentials or an exploit containing customer data in an initial message.