Products · Portfolio

One platform. Five products.

A database, a workbench, an MCP integration layer, and two applications that turn a working environment into queryable state. Each with a real destination and an honest maturity line.

Portfolio

Three families, one foundation.

Products are named PLOMID software. They are not solutions and not industries: a solution is a workload the platform carries, an industry is an environment it runs in, and a product is something you install, open, or pilot.

5 products
PLOMID products, with family, purpose and maturity.
Product Family What it is Maturity Next step
PLOMID Platform Core data infrastructure One database for rows, documents, time-ordered events and vectors. Open beta Download PLOMID
PLOMID Studio Platform tools The desktop workbench for a PLOMID database. In development Follow the build
PLOMID-MCP Platform tools Connect AI clients and agents to a PLOMID database over MCP. Engineering preview Read the docs
PLOMID Cabin Industry applications In-cabin occupant intelligence, at the edge. Pilot program Talk about a pilot
PLOMID Resolve Industry applications Evidence-linked vehicle failure investigation. In development Talk about a pilot
Relationship

How the products fit together.

One dependency, stated four ways: everything reads and writes the same layer.

Foundation

Platform holds the data

One parser, one planner, one execution path and one storage contract across SQL, JSON, time series and vectors — so an application and an AI client read the same layer rather than two copies of it.

The platform

Workbench

Studio is a client

It works directly against a PLOMID database and runs on the desktop, so the database does not need a hosted console to be operable.

Studio

Agent access

MCP is an integration boundary, not a second store

PLOMID-MCP turns the database's supported SQL interface into standard MCP tools, with validation, policy and bounds at the adapter. The database stays independent and remains the system of record.

MCP

Applications

Cabin and Resolve keep no second database

Cabin writes occupant state and events from the edge and reads them back through its engineering console; Resolve records an evidence-linked investigation. Both keep PLOMID as the system of record.

Cabin · Resolve

Not sure which one you need

Start from the platform.
Or from the problem.

Choosing a database starts at the platform. Knowing the operational problem starts at a product. Either way, the first conversation is the same one.