Does the playground connect to a real PLOMID system?

No. Every request runs entirely in your browser against a fixed dataset that ships with the site. There is no server, no account and no telemetry.

Why do the same queries sometimes return in a different order?

The samples demonstrate the interaction model, statement, parse, plan, execute, result, not deterministic engine behaviour. Ordering semantics belong to the product, not this demonstration.

Can I try my own SQL here?

The playground runs the four prepared samples only. When packaging for general download is finished, the product will be the place to run your own statements.

Where do I read about what the statements mean?

The documentation covers the SQL surface, document access and time windows for the models available today.

Run the samples.

Four requests over a fixed sample dataset, computed in your browser. Choose one, run it, and follow the stages a request moves through, from statement to result.

Run the first sample Read the documentation

Samples

Pick a request.

Each sample shows a different shape of data being queried through the same surface.

Mixed workload mixed.sql Run Aggregation regions.sql Run Document account.sql Run Time series events.sql Run

Statement

Parse

Plan

Execute

Result

PLOMID · query console sample dataset · computed locally

mixed.sql sample dataset

-- 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;

ready 0 ms · sample

MIXED · ROWS + DOCUMENTS 5 rows

id	region	plan	orders	last_order
C10284	EU	enterprise	14	2026-09-18
C10591	APAC	scale	11	2026-09-17
C11108	EU	enterprise	9	2026-09-19
C11620	US	team	7	2026-09-15
C10922	US	scale	6	2026-09-12

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

Note Results are computed in your browser from the fixed sample dataset. Nothing here measures the product.

Scope

What this is, precisely.

A demonstration that is honest about its own limits is more useful than one that implies more than it shows.

The dataset: A small fixed sample that ships with this site: customers with rows and a document, orders, and time-ordered events.
Where it runs: Entirely in your browser. There is no connection to a PLOMID system, no account and no telemetry.
What it demonstrates: The interaction: pick a statement, watch parsing, planning and execution, read the result shape.
What it does not demonstrate: Performance, scale, concurrency or storage behaviour. It is a demonstration of the surface, not a measurement of the product.

Vector, graph and blobs are on the roadmap, there is nothing to run for them yet.

Questions

Before you run it.

Continue

Documentation The reference behind these samples, including what is not documented yet. Developers The query surface and how access to the platform works. Roadmap Which data models are in the product and which are on the roadmap.