For agencies
Agencies
The question is not whether client isolation is configured. It is whether it can fail.
Isolation is structural, not careful
Every client scoped repository takes the client id as its first argument, and every database index leads with it. There is no code path that reads a client scoped collection without a client. Asking for another client record returns not found rather than forbidden, because forbidden confirms the record exists.
Credentials you cannot leak because you cannot read them
Each client credential is encrypted with AES-256-GCM under a key derived for that client alone. No endpoint returns a plaintext secret, including to you. Reads give a name, a four character preview, and when it was set.
Positioning rules per client
A client that must never be positioned as a particular category carries that rule in its own record. It composes with the universal rules for every piece of content. One client never inherits another client positioning, and changing a rule does not need a deploy.
- Up to 10 client workspaces on Agency
- Unlimited on Scale
- Re-audit any site on demand
- Audit trail export on Scale
Questions
Can one client see that another exists?
No. Not through the API, not through error messages. Cross client reads return 404 rather than 403 for exactly this reason.
Is there white labelling?
Not today. Reports carry our name. If white labelling matters to you, tell us and we will say honestly where it sits rather than promising a date.
Other ways teams use this
Founders
Find out whether AI answer engines can read and cite your site, without hiring a specialist or learning what a canonical tag is.
You publish regularly and someone eventually asks for the sourceIn-house marketing
A claim registry and a seven rule validation gate that blocks unsourced numbers, fabricated quotes and missing disclosure before anything ships.
Run a check first
No signup, no card. See what it finds before you decide anything.