Security at Akroly
Akroly manages security settings for your Cloudflare accounts, so we hold ourselves to a higher bar. This page summarizes how we protect you. Our full threat model is available to customers on request.
Access to your Cloudflare account
- We connect through Cloudflare's official OAuth (Authorization Code with PKCE). You see every permission on Cloudflare's consent screen and can revoke access at any time.
- Read-only first. Write permissions are requested once, only when you first press "Fix it", and only for the settings Akroly can change.
- Tokens are encrypted at rest with per-customer envelope encryption (AES-256-GCM). The master key lives in Cloudflare Secrets Store, never in our database. Tokens are used only server-side and never reach your browser, our logs or any AI model.
- Refresh tokens are rotated under a lock; if Cloudflare ever reports token reuse, the connection is locked and you are alerted.
Your team's sign-in
- Sign in with Google, Microsoft, a passkey or a single-use email link. Enterprise SSO per organization.
- Admins must use a second factor (passkey or authenticator app) to approve changes; sensitive actions such as rollback or disconnect ask you to verify again.
- Sessions use HttpOnly, Secure cookies with CSRF protection, strict Content Security Policy and rate limiting.
Changes
- Every change shows a preview and diff first, runs pre-flight safety checks (for example, your origin certificate is validated before SSL Full (strict)), is verified afterwards and can be rolled back in one click.
- Every sign-in, approval and change is written to an append-only audit log.
AI assistant
- The assistant never sees your tokens and cannot call Cloudflare. It can only propose allow-listed fixes, which go through the same preview, approval and audit. Text in DNS records and logs is treated as data, never as instructions.
Platform
- Runs on Cloudflare Workers, D1, Durable Objects and Queues. Strict tenant isolation on every database query, tested automatically. Pinned dependencies and secret scanning in our pipeline.
Report a vulnerability
Email security@akroly.com. See security.txt. We do not take legal action against good-faith research.