What you can build today.

One query surface across rows, documents and time-ordered events, available now. Similarity, relationships and objects are the next access paths, and are on the roadmap.

Open the playground Read the documentation

Start here

Three steps, no setup.

You can look at the query surface before you talk to anyone. The playground runs the same statements you read on this page.

Pick a data model

Rows, documents or events. Start with the one that removes the most glue, usually rows.

See the models

Run a request

Four sample statements run against data that ships with the page, right in your browser. Nothing to install.

Open the playground

Read the reference

The query surface for what is available today, plus what is deliberately not documented yet.

Read the docs

Capability

What you can build on, and what is ahead.

Solid means available today. Dashed means roadmap, useful as direction, not as something to build against.

Available

SQL

Transactional application data

Relational workloads, tables, joins, transactions.

Records, keys and joins
Consistent reads and writes
Users, orders, inventory

Available

JSON

Application documents

Documents and nested objects, queried alongside rows.

Nested objects stored beside rows
Fields that keep changing shape
One query across both shapes

Roadmap

Key-Value

Direct access

Short-lived state, addressed by key.

Sessions and short-lived state
Lookups beside relational rows
Cache-style access patterns
One key, one value, one address

Available

Time series

Telemetry and events

Events, measurements and history over time.

Time-ordered events and measures
History beside current state
Windowed reads and downsampling

Roadmap

Geo

Spatial data

Where it is, asked like any other predicate.

Nearby and radius queries
Location beside the other models
Region-aware filtering
Distance as a queryable value

In development

Vector

Search and retrieval

Similarity and semantic retrieval.

Semantic and similarity search
Retrieval inside application workflows
Embeddings stored beside the source data
Recommendations and related items

In development

Graph

Connected data

Nodes, edges and traversal.

Relationship exploration
Dependency and impact analysis
Connected-data workflows
Network and knowledge relationships

In development

Objects

Large objects and assets

Large objects and file-like assets.

Files and media assets
Artifacts and datasets
Unstructured binary objects
Assets with queryable metadata

Roadmap Vector, graph and blobs are being explored. There is nothing to run for them yet, and no dates are published.

Example requests

Three requests, three data shapes.

These are the sample statements the playground ships with. Run them there to see the plan form and the result return.

MIXED · ROWS + DOCUMENTS

Mixed workload

5 rows from the sample dataset · rows and document fields read together

Run in the playground

mixed.sql sql

-- structured rows and flexible documents in one query
SELECT c.id,
       c.region,
       c.profile ->> 'plan'          AS plan,
       COUNT(o.id)                   AS orders,
       MAX(o.created_at)             AS last_order
FROM   customers c
JOIN   orders o ON o.customer_id = c.id
WHERE  o.created_at >= NOW() - INTERVAL '90 day'
GROUP  BY c.id, c.region, plan
ORDER  BY orders DESC
LIMIT  5;

JSON · SINGLE DOCUMENT

Document

1 document · nested fields stay queryable

Run in the playground

account.sql sql

SELECT profile
FROM   customers
WHERE  id = 'C10284';

TIME · EVENTS PER WINDOW

Time series

6 windows · sample events bucketed by hour

Run in the playground

events.sql sql

SELECT DATE_TRUNC('hour', ts) AS window,
       COUNT(*)               AS events,
       MAX(latency_ms)        AS p_max
FROM   events
WHERE  ts >= NOW() - INTERVAL '6 hour'
GROUP  BY window
ORDER  BY window;

Request stages

Parsing, planning, executing.

The console shows these three stages as a request runs. They are the real sequence a request moves through, a plan is chosen before anything is read.

Parsing

The statement is read and resolved against the schema of the data layer.

Planning

A plan is chosen across the data models the request touches.

Executing

Operators run over the stored layout and produce a result set.

Note Stage timings shown anywhere on this site are illustrative of the interaction, not measurements of the product.

Access

How to get your hands on it.

The playground is open. Everything beyond it goes through a short conversation, because what you get depends on what you are running.

Available models: SQL, JSON / documents and time series.
Surfaces: SQL statements, document field access, and time-windowed reads inside the same statement.
Access: Capabilities marked available are in the product. Packaging for general download is not finished, so access and evaluation are arranged with the team.
The playground: Runs entirely in your browser against sample data that ships with this site. No connection, no telemetry, no account.

Describe the workload

What you store, what you query, and which part of it is currently spread across more than one system.

Scope one data model

We start with the model that removes the most glue, usually rows, sometimes documents, sometimes events.

Run it side by side

Measure against the existing stack. If it does not hold up, you keep what you already have.

Try the playground Read the docs GitHub [email protected]

GET PLOMID, no packaged download exists yet. Source and release packaging are being prepared; until then the playground, the documentation and the repository are the real entry points.

Continue

Documentation Concepts, the SQL surface, document access and time windows in reference form. Playground Run the sample requests and watch the stages a request moves through. Architecture What sits under the query surface, from interfaces down to storage.