Last updated November 16, 2026
Security at Blayde
Blayde makes changes in other companies' cloud accounts, so it's built around one idea: no one, human or AI, gets more access than the approved job needs, and everything is checked and recorded.
Access to your accounts
- No permanent keys. Blayde reaches your AWS account only through roles you deploy from our published templates, using short-lived sessions and your organization's own external ID. Delete Blayde's stacks and uninstall its GitHub App, and Blayde can reach nothing.
- Read-only by default. Audits use a role that cannot change anything. Deploy plans are made with the deploy role and change nothing until you approve. The deploy role is broad (AWS PowerUserAccess), but every role it creates for your app sits inside a fence you can read, and Blayde applies only the plan you approved. Access fixes use a role that can only delete users and require multi-factor.
- GitHub, one repository at a time. Blayde's GitHub App receives tokens scoped to the single repository a job needs, expiring within an hour.
Approvals and separation of duties
- Every change needs a person's approval, signed in with multi-factor authentication. The approval is tied to the exact plan; change the plan and it needs approving again.
- The AI that plans never approves. The identity that makes a change never verifies it: a separate read-only identity checks the result. Access fixes are compared against a snapshot taken before; deploys are checked for their resources, the roles they made and that the app answers.
- Access-fix plans also get a second opinion from OpenAI and xAI's Grok.
- Every request, plan, review, approval, change and check is recorded, and you can export the record.
Your data
- What Blayde builds lives in your accounts. Blayde keeps the project record and, for each deploy, a copy of the commit and its plan.
- Builds run in isolated, short-lived containers that never hold Blayde's GitHub App key or any AI key. They get only a one-hour token for the one repository, from a broker that checks every request against the job, its budget and its time limit.
- Anything that looks like a secret is removed from what you type before an AI model sees it. We never use your data to train models.
- Private organizations run on Claude through Amazon Bedrock only, so data stays in AWS.
- Data is encrypted in transit (TLS) and at rest (AWS-managed encryption).
Our own platform
- Infrastructure is defined in code and changed only through reviewed pull requests, with automated security scanning (secret scanning, infrastructure policy checks) on every change.
- Production is separate from development, and changes to it need their own approval.
- The website runs no third-party scripts and is served with a strict content security policy.
Certifications
Blayde does not yet hold an independent certification such as SOC 2 or ISO 27001. We won't claim one until an auditor has issued it, and we'll list it here when that happens. Until then, we're glad to answer your security questionnaire: security@blayde.app.
Reporting a vulnerability
If you believe you've found a security problem in Blayde, email security@blayde.app with the details. We'll acknowledge it within two business days and keep you updated. Please don't access other customers' data, disrupt the service, or make the problem public before we've fixed it. We won't take legal action against good-faith research that follows these rules.