Control over where the data lives.
Deployment, residency and operational ownership are design decisions, not add-ons. The layer that carries them, the deployment fabric, is on the roadmap, and this page says so.
Three questions every infrastructure decision has to answer.
They are boring questions, and they are the ones that decide whether a platform can be adopted at all.
Residency
For some organisations the location of data is a legal requirement, not a preference. That constraint has to be designed for, not bolted on.
Ownership
Someone has to operate the system at three in the morning. Being able to point at who, and where, is part of the product.
Exit
A data layer you cannot leave is not infrastructure, it is a dependency. The shape of that exit is decided by the storage contract, not by a marketing page.
One layer between your data and everywhere it could live.
Location, control, replication and access are the four questions the visual answers. The destinations it points at are direction, and are drawn that way.
location · control · replication · access
On-prem The system runs on hardware you control, in a location you choose. This is the destination the deployment fabric is designed around, and it is not available yet.
Edge A smaller footprint close to where the data is produced, for latency or connectivity reasons. Direction only — nothing here is runnable today.
Cloud A managed topology, where the hardware is operated for you. Being explored; not available.
Anywhere The end state: the same layer, placed by declared policy rather than by whatever the software happens to support. Long-term direction.
Seven questions, answered honestly.
Seven questions every control story has to answer, stated plainly. What is still direction is marked as direction further down this page.
Data location
There is one system and one place your data lives, so there is no ambiguity about which copy is authoritative.
Data residency
Region and residency boundaries as declared policy, part of the deployment fabric being designed.
Ownership / control
Who operates the system, and where, is part of the first conversation rather than a plan tier on a pricing page.
Access
One system to reach, with access decided between you and the people running it, there is no separate fleet of stores to reason about.
Replication
Where copies may exist, how many, and what keeps them consistent. This is a designed property, not a side effect of setup.
Jurisdiction
Which infrastructure and which data may fall under which rules. Tied directly to residency, and equally unfinished.
Portability / exit
One storage contract means the shape of the exit is a property of the design rather than an export tool bolted on afterwards.
What you can rely on now.
Four things that are true today, not aspirations. Everything below this section is marked as direction instead.
One system, not a fleet
PLOMID runs as one system with one storage contract. Fewer components means fewer places where a copy of your data can quietly exist.
No account to try the surface
The playground runs entirely in your browser against a dataset that ships with this site. Nothing you type there is sent anywhere.
This site collects nothing
No analytics, no cookies, no trackers, no third-party scripts beyond the web font. If that changes, it will be stated here first.
Access is a conversation
Where the system runs, and under whose operations, is part of the first conversation rather than a plan tier on a pricing page.
The deployment fabric.
This is the layer that decides where the system is allowed to run and what a region means. It is being built, and it is not available to use.
Where the system runs, and where data is allowed to be.
Designing it late would mean retrofitting boundaries into a system that had already assumed a single location. That is why it is a named layer with its own responsibility rather than a configuration flag.
- Self-hosted and cloud topologies
- Region and residency boundaries
- Replication as policy, not accident
- Status
- Roadmap
- In the product
- Self-hosted and cloud topologies are not yet available.
- Residency
- Region and residency boundaries are not yet enforceable in the product.
- What we will not do
- Publish residency guarantees before they can be demonstrated.
- On-prem your hardware
- Edge close to the source
- Cloud managed
- Anywhere chosen by policy
All four are direction, none is available to use today.