post
Your perimeter is the feature.
Why clear has no credentials to your content — and why that's the whole point.
Most headless CMSes are SaaS — your content sits on their servers, behind their auth, governed by their backup policy. That's a single point of compromise and a single point of vendor risk.
clear is built the other way around. The bucket is yours. Your IAM, your KMS, your audit log. The admin runs inside your perimeter — laptop, VPC, on-prem. We never had your content. A breach of clear is not a breach of you.
Portability is the same property viewed from the other side: if leaving us is one aws s3 sync, we never had leverage over you in the first place.