Platform
One firm, one cell, and no shared content plane
Each firm runs in its own project with its own database, network and identity. The boundary between firms is infrastructure, not a column in a shared table. The boundary between you and us is narrower, and we say so.
Your document system sits outside this boundary and stays authoritative. The cell reads from it and writes back only where you turn that on.
What isolation means here
And what it does not
The honest version, because the version that oversells it is the one that gets found out in diligence.
What holds today
These are properties of the running system, not of a roadmap.
No shared content plane
There is no cross-firm corpus to retrieve from, because there is no shared store of firm content at all.
No training on your content
Not by us, not by a provider underneath us. Instances share code and never data.
Your store stays authoritative
The platform reads from your document system and does not become a competing copy of it.
What we are not claiming
Some of what a security questionnaire asks for is not finished, and the site will not pretend otherwise.
The cell is operated by us
It runs in WYEA infrastructure. It is not a deployment inside your own cloud account or on your own hardware.
Export and deletion are not built
Offboarding is designed and not yet implemented. Ask, and we will show you the current state honestly.
Support access is not client-visible
It is scoped, but you cannot yet watch it in a log of your own. That gap is real and we are closing it.
Start a conversation
Tell us what your people spend the day reading.
Thirty minutes, no obligation. If a shared product would serve you better, we will say so on the call.
The Brief
The week in legal, in four minutes.
Free, national to Orange County, every Wednesday.