The Community edition is free, install it from the shell script, the Docker image or your package manager, with the source on GitHub and the documentation covering everything the product carries. Enterprise pricing is agreed directly with our team; Managed Cloud pricing is published when it opens.

What does Enterprise cost?

There is no published figure. Enterprise is agreed with our team against the deployment, residency requirements and support involved. Write to the team with the workload and the boundary, and the number comes out of that conversation.

What happens after we write to the team?

Enterprise deployments start with a conversation about your workload, your residency requirements and what you are consolidating. Security review, procurement and a reference architecture come out of that conversation, you do not need to wait for anything to ship.

Can we evaluate before talking to anyone?

Yes. Install the Community edition on your own hardware, read the documentation and run the playground in your browser. No account, no form, no waiting. Bring the questions that come out of it to the Enterprise conversation.

What can I install right now?

Everything on the download page: a one-line shell install, a Docker image, the public source on GitHub, and the playground in your browser. No account, no form, no waiting.

When does Managed Cloud open?

It follows the deployment fabric work on the roadmap, and its first tenants come from Enterprise partnerships. Registering interest now puts you in that first group and shapes what it looks like.

Three ways in. One layer underneath.

Community is free to install and build on. Enterprise is custom and starts now, with residency, control and a direct line to the engineers. Managed Cloud is usage-based and follows on the roadmap.

Talk to our team Install the Community edition

Two doors open now
Same software, every tier
No account to start

The tiers

Start free. Scale with a conversation.

The same software, the same storage contract. What differs is who operates it, where it runs and who answers when it matters. Two of the three doors are open right now.

For developers and evaluation

Community

Free free to run, on your hardware

Free · install it yourself

Developers and teams evaluating the layer on their own hardware.

The full source with one-command installs, shell, Docker or your package manager. Build against every model the product carries, with the documentation and the browser playground one click away.

One-command install: shell script, Docker image or package
Every shipped data model, no feature gates
Full source on GitHub, read it, fork it, ship it
The playground and the complete documentation
Community support through public channels

Install PLOMID

No account · no form · no waiting

Most organisations start here

For organisations with requirements

Enterprise

Custom agreed with our team

Talk to us now · deployments underway

Organisations with residency, control and support requirements.

Self-hosted deployment inside your own boundary, with residency as declared policy, enterprise support and integration with the systems your business already runs. The deployment fabric is being built with our design partners, and those partnerships are open.

Self-hosted, inside your boundary
Residency and control as product features, by design
Enterprise support with a direct line to the engineers
Integration with existing enterprise systems
Procurement and security review supported now

Reach our team

A conversation, not a checkout

For teams that want it operated

Managed Cloud

Usage-based published when it opens

On the roadmap · shaped with design partners

Teams that want the layer operated for them.

A managed deployment of the same layer, operated to the same storage contract, with capacity, backups and upgrades handled. It opens after the deployment fabric work completes, and its first tenants come from the Enterprise conversations.

The same layer, operated for you
One storage contract, managed capacity
Backups, recovery and upgrades included
Pricing published when it opens
First access through Enterprise partnerships

Join the first-tenant list

Solid, open now Dashed, opens on the roadmap

Included everywhere

One layer, whatever you pay.

Pricing changes who operates the system and where it runs. It never changes what the system is.

Same software

Every tier runs the same layer. There is no fork, no gated edition, no separate codebase to reconcile.

Same storage contract

Rows, documents and events share one durability and recovery path, whoever operates the system.

No feature gates

Every shipped data model is in the Community install. What is roadmap is roadmap everywhere, stated once.

Docs, playground, source

The documentation, the browser playground and the full source are included everywhere, with no account.

Compared

The same layer, three operating models.

Every tier is the same software with the same storage contract. What differs is who operates it, where it runs, and who answers the phone. Select a tier header to isolate its column, open any row for the reasoning.

Question
Start and cost
	One-command install	A conversation with our team	Register interest
Why it mattersThe first step sets the operating model. Installs start on your machines, partnerships start with a conversation.
	Your machines	Your boundary, your region	PLOMID-operated regions
Why it mattersThe boundary decides residency. Your machines, your region, or PLOMID-operated regions.
	Free	Custom, agreed with our team	Usage-based, published at opening
Why it mattersNo published numbers. Free to run, custom by agreement, usage-based at opening.
Run and operate
	You	You, supported by us	PLOMID
Why it mattersWho answers when it matters. You, you with us beside you, or us.
	You manage	Supported by us	Included
Why it mattersDurability is shared through one storage contract; who runs the operation differs.
	Your hardware	Your boundary, planned with us	Managed capacity
Why it mattersSized by your hardware, planned with us for your boundary, or managed as capacity.
Control and trust
	By deployment choice	Declared policy, by design	Region selection
Why it mattersControl as deployment choice, or as declared policy by design on Enterprise.
	Full source on GitHub	Source plus reference architecture	Same layer, operated
Why it mattersThe same code everywhere. Enterprise adds the reference architecture for your workload.
	—	Supported now	—
Why it mattersOnly Enterprise carries procurement and security review support today.
Build and support
	Every shipped model	Every shipped model	Every shipped model
Why it mattersNo gates. Every shipped model is in every tier; roadmap is roadmap everywhere.
	Included	Included	Included
Why it mattersYou learn the same way on every tier: docs and the browser playground.
	Community channels	Direct line to the engineers	Included
Why it mattersPublic channels, a direct line to the engineers, or operation included.

Isolated tier, copper column Open a row for the reasoning

Enterprise pricing is agreed with our team. Managed Cloud pricing is published when it opens.

Enterprise

Enterprise starts with a conversation.

No checkout, no seat count. You bring the workload and the boundary, we bring the reference architecture and a direct line to the engineers.

01

Tell us the workload

What you store, what is split across systems today, and the question you are trying to decide. A specific workload gets a useful answer.
02

Reference architecture and review

A deployment inside your boundary with residency as declared policy. Security review and procurement come out of this conversation.
03

Deploy with a direct line

Self-hosted with enterprise support and integration help, from the engineers building the system.

Managed Cloud · roadmap

Operated for you, when the fabric lands.

The same layer under PLOMID operation: managed capacity, backups, recovery and upgrades to the same storage contract. It opens after the deployment fabric work completes, and its first tenants come from the Enterprise partnerships.

Usage-based · published at opening

Questions

Pricing questions, answered plainly.

Where to go from here.

Talk to our team Start the Enterprise conversation. Install PLOMID Shell, Docker, GitHub, one command each. Read the roadmap What ships, what builds, what is direction.