Security
Orbit processes your source code and interacts with your staging environments. We take that responsibility seriously. Here is exactly how we protect your data.
Encryption at Rest and In Transit
All data is encrypted in transit using TLS 1.3. At rest, database storage is encrypted via the hosting provider's disk encryption. Secrets stored in Orbit's vault (API keys, staging credentials, environment variables) are encrypted using AES-256-GCM with unique initialization vectors per secret. Secrets are never logged, never displayed in plaintext in the UI, and are decrypted only at the moment of test execution.
Ephemeral Test Execution
Browser tests run in isolated, ephemeral sessions via Playwright. Each test run gets a clean browser context that is destroyed after execution completes. No persistent browser state, cookies, or sessions carry over between runs. When using cloud browsers (Browserbase), sessions are fully sandboxed and terminated on completion.
Tenant Isolation
Every database table includes a workspaceId column enforcing strict row-level tenant isolation. No API endpoint can access data from a workspace the authenticated user does not belong to. Source code, test results, embeddings, and secrets are completely isolated between workspaces.
Webhook Verification
All incoming webhooks (GitHub push events, PR events) are verified using HMAC-SHA256 signature validation before processing. Webhooks without a valid signature are rejected. Outgoing webhook payloads to your integrations (Slack, Linear) are sent over HTTPS and contain only the minimum data necessary.
AI Provider Data Handling
Code snippets are sent to Anthropic and OpenAI for analysis under their respective API agreements, which prohibit using API inputs for model training. We send only the minimum context needed for each task (not your full repository). AI provider interactions are logged for debugging but do not include raw source code in persistent logs.
Authentication and Access
Orbit uses GitHub OAuth for authentication with JWT-based session tokens. Repository access is scoped to the permissions you grant. You can revoke Orbit's access at any time from your GitHub settings, which immediately disables repository syncing.
Infrastructure
Orbit runs on Railway's infrastructure in the United States. The database (PostgreSQL) and application are hosted in Railway's managed environment with automated backups, network isolation, and encrypted storage. All services communicate over private internal networks where possible.
Responsible Disclosure
If you discover a security vulnerability in Orbit, we ask that you report it responsibly. Please email hello@sunrisesystems.co with details of the vulnerability. Do not publicly disclose the issue until we have had a chance to investigate and address it. We commit to acknowledging reports within 48 hours and providing a resolution timeline within 5 business days.
Compliance Roadmap
Orbit is an early-stage product and does not currently hold SOC 2 or ISO 27001 certifications. As we grow, formal compliance certifications are on our roadmap. Enterprise customers with specific security requirements can reach out to discuss custom arrangements including dedicated infrastructure, audit logs, and data residency options.