TEDLad platform
Security architecture
Implemented controls and explicit assurance boundaries.
Tenant data isolation
Organization and workspace records use explicit foreign keys, tenant-scoped transactions, and forced PostgreSQL row-level security.
Secret handling
API keys are stored as hashes. Integration credentials, email payloads, backups, and public enquiries use authenticated encryption with rotatable key IDs.
Bounded provider access
Provider requests use fixed adapter endpoints, timeouts, response-size limits, redirect refusal, and safe error categories.
Auditable operations
Mutations, approvals, workflow runs, usage reservations, deliveries, migrations, and recovery actions produce durable evidence.
Fail-closed launch controls
Effectful production capabilities remain prohibited until the exact release and acceptance digest are explicitly configured.
Current assurance scope
TEDLad does not claim a third-party security certification or regulatory certification that has not been independently awarded.