Uranus is a modern, high-performance engine for HTAP workloads: transactional writes and analytical queries against the same data, with an Arrow-based columnar core. Everything on this site runs the real engine, compiled to WebAssembly, locally in your browser — no server, no signup.

Try it

  • … in the SQL Interface — a query editor with results, run stats, and the optimizer’s plan.

  • Starting from a seeded demo catalog. Data lives in the page: reload and you start fresh.

SQL reference

Types

INT  SMALLINT  BIGINT  FLOAT  DOUBLE  DECIMAL  BOOL  CHAR(n)  VARCHAR  DATE

Statements

CREATE TABLE orders (id INT, customer VARCHAR, total INT, status VARCHAR);
DROP TABLE orders;

INSERT INTO orders VALUES (1, 'ada',  120, 'shipped'),
                          (2, 'grace', 80, 'processing');

BEGIN;
COMMIT;

Queries

SELECT customer, SUM(total)
FROM orders
WHERE status = 'shipped'
GROUP BY customer
ORDER BY SUM(total) DESC
LIMIT 10;

Joins (including self-joins), WHERE, GROUP BY, ORDER BY, LIMIT, and the usual aggregates (COUNT, SUM, AVG, …) are supported. NULLs sort first on ascending ORDER BY.

Catalog

The engine keeps a Postgres-style catalog — pg_class, pg_attribute, pg_type — queryable like any other table. The terminal adds two conveniences on top:

SHOW TABLES;      -- tables in the catalog
DESCRIBE orders;  -- column, type, not_null per column

The browser engine

  • Build: the engine’s C API (currently v7), compiled to wasm64 and served as liburanus.wasm (~10 MB). It runs in a Web Worker; the page talks to it over async RPC. The version shown in the terminal status bar is reported by the engine itself, not hardcoded.
  • Isolation: the engine’s memory is a SharedArrayBuffer, so pages must be cross-origin isolated (COOP/COEP response headers).
  • Storage: two modes. By default in-memory — a page load is the engine’s lifetime, nothing is written to disk, and there is a single connection. Pages that opt in (the SQL Interface and /try/browser/) use an OPFS fixture: a frozen TPC-H or TPC-DS database (SF 0.01; TPC-H ~8 MB, TPC-DS ~29 MB on disk, both gzip-compressed in transit) is fetched once into the browser’s Origin Private File System and opened by the same disk-backed engine as on the server — later visits download nothing, pages fault in on demand, and Reset data (plus Hard reset in the terminal) drops and re-fetches it. The SQL Interface lets you switch between TPC-H and TPC-DS (both stay stored, so switching back is instant) and pick any of their queries (22 and 99); if a fixture can’t load it falls back to its small sample tables. The terminal uses TPC-H.

Known limitations (browser build)

  • No persistence for data you create: reloading the page resets the catalog (the OPFS fixture is read-only preloaded data and does persist).
  • One statement at a time; the prompt is locked while a query runs (typed input is buffered and echoed when the prompt returns).
  • Savepoints are not available in this build.