Trust center
Control before autonomy.
The technical controls behind how To200 reads code, changes branches, handles credentials, verifies fixes, and records every consequential action.
Built into the repair loop.
Change isolation
Every implementation stays on a branch. To200 records the sandbox and repository checks available before it opens a pull request.
Evidence before trust
Each repair records the likely root cause, checks attempted, results, confidence, and anything that remains unverified.
Tenant boundaries
Supabase Row Level Security scopes customer reads and writes; engine tables are service-role write-only and member read-only.
Credential handling
Integration secrets remain server-side in Vault-backed storage and are never returned through member-facing reads.
Enterprise identity
Supabase SAML routing and workspace-scoped SCIM provisioning support centralized access lifecycle management.
Lifecycle controls
Workspace retention policies purge expired operational data while audit-chain anchors preserve integrity evidence.