Building a data layer from the storage up.
PLOMID, Platform for Modern Intelligence and Data, exists because applications and the AI clients beside them stopped fitting into one data model, and the answer to that should not be a shelf of databases.
The data layer is the last place still assembled by hand.
Compute, deployment and networking all moved behind a common abstraction. Data did not: it stayed split by shape, with the integration work pushed onto whoever is building the application.
The bet behind PLOMID is that the split is a historical accident rather than a requirement. Rows, documents and events are different ways of shaping data, not different physics.
If they can share one storage contract and one planner, then the integration layer between them stops being something every team rebuilds. That is the whole thesis, and it is falsifiable: either the layers hold, or they do not.
Everything on this site is written against that standard. Capability status is stated plainly, and the parts that are still design are named as still design.
- Name
- PLOMID, Platform for Modern Intelligence and Data.
- Building
- Unified data infrastructure: storage, query, and the layers between them.
- Today
- SQL, documents and time series over one data layer.
- Direction
- Vector, graph, blobs, and the deployment fabric.
Six rules we hold the work to.
Principles are only worth writing down if they can be violated. Each of these can, and would be visible from the outside if it were.
Infrastructure before the surface
Foundational systems get engineered before the layer that markets them. The storage contract is written before the query console looks nice.
Familiar interfaces first
Where a familiar interface already exists and works, use it. SQL is not a legacy burden; it is the shortest path between an engineer and an answer.
One storage contract
Every data model inherits the same durability and recovery rules. When a model needs an exception, that is a signal the design is wrong somewhere.
State status plainly
Available, in development and roadmap, three words, used the same way on every page, in every sentence that touches a capability.
Invent nothing
No logos we have not earned, no quotes we have not been given, no benchmarks we have not run, no numbers we cannot show.
Control is a feature
Where data lives and who operates the system are part of the product, not terms in a contract.
Three commitments that shape the work.
The way PLOMID is built is stated as plainly as what it is: what the company is making, how it approaches the engineering, and how to reach the people responsible for it.
From the storage layer up
Work starts at persistence: layout, durability, recovery. If that layer is not solid, everything above it is a liability.
Small and deliberate
One system with few moving parts is easier to reason about than a fleet of specialised services. That preference shapes the software and how it is built.
Publish what is true
This site is written to be checkable. If a claim here cannot be verified against the product, it does not belong on the page.
Building a database is a long game.
The work sits in storage layout, planning, execution and the boundaries between them. The problems, the principles and how to apply are on the careers page.
PLOMID is a systems problem before it is a product problem. Most of the real work is the kind a user never sees and always depends on — which is exactly why it is worth doing, and why the careers page describes it in the architecture's own vocabulary.
- Open roles
- Published on the careers page, each with the problem it exists to solve.
- Where the work is
- Storage and layout, query planning, execution, developer tooling, and the deployment fabric.
- How to reach us
- Write to [email protected] and say what you would build first.
For investors, press and partners.
Three routes in for the people outside the codebase. Each says what the company is, who to write to, and what it will not claim before it can be shown.
Explore the project. Follow the work. Build with us.
PLOMID is built in public where it can be. Watch the work land on GitHub, follow along on the channels below, or write to the team directly.
Discord and Slack open when the channels do, the icons wait for real invitations, not placeholders.
Built in India. For the world.