No inline content path
Metadata-only
Send provider, model, token, cost, and workload labels after your own provider call. Prompts and responses stay out of Varsten.
Security
Choose the data path that matches the workload, keep credentials bounded, and preserve a direct fallback for production traffic.
01 · Data paths
Security starts with how you connect.
Provider key stays local
Production SDK
The Varsten key authenticates the optimized path. Your provider key remains in the application for direct fallback.
Connected provider credential
Base URL evaluation
Varsten processes content in transit and uses a connected provider credential. This path should be reviewed before sensitive use.
02 · Controls
Current operating controls.
Tenant boundaries
Project-scoped credentials and organization ownership checks isolate customer resources across the control plane.
Least privilege
Application roles and infrastructure permissions are scoped to the resources required for their runtime responsibilities.
Auditability
Security-sensitive account, credential, and administrative actions are designed to produce attributable audit records.
Encrypted transport
Public application and API traffic uses TLS. Sensitive configuration is kept out of client-side code and analytics.
03 · Reliability
An outage should not become your outage.
Direct provider fallback
SDK wrappers can bypass Varsten for eligible transport or Varsten-origin failures before output starts.
No unsafe replay
Provider-origin errors, deliberate budget caps, and mid-stream failures are surfaced rather than retried blindly.
Circuit breaking
Repeated Varsten failures open a local breaker so applications do not pay the same failed timeout on every call.
Current posture
Not yet SOC 2 certified.
Varsten is building toward formal assurance but does not claim a SOC 2 report, penetration-test certification, or compliance status that does not exist.
For questionnaires, vulnerability reports, architecture review, or available security materials, email security@varsten.ai.