HexDB

Search HexDB

Find a feature, an API example, a step, a FAQ answer or a term, then jump to it.

Playground

Try a Live Lattice.

Four hexes run on Fly.io as a lattice called Playground, in four regions on two continents (Ashburn, Chicago, San Jose and London), so a whole region can go down without losing data, and a fifth, the Oracle (in Secaucus), answers its AI questions and keeps no data. It's loaded with about 85,000 documents (products, customers, orders, payments and shipments) and a files tessellation holding a whole album: Codex Animae by Ashes Gone, 15 WAV masters, three full-length music videos and the artwork. Sign in to the admin UI, query the lot in GraphQL or SQL, run the saved functions, edit the sandbox and watch its changes flow through a stream while the other three hexes keep up. The sandbox is reset every hour.

lattice · playground

The Lattice

Open the Admin UI

Everyone shares this login. It can read everything, write to the sandbox tessellation and watch the lattice; nothing else. Whichever hex is nearest you answers, and your writes go on to the Overseer.

User
playground
Password
········
Open the Admin UI

Things to Try

  • Dashboard

    The lattice card lists every hex, the Oracle included, with its role, region and replication lag. Vertex health shows the six memory vertices.

  • Queries

    Switch between GraphQL and SQL, pick an example and press Ctrl+Enter: revenue by country, payments by method, or a SELECT with ? parameters. Aggregations run over the whole tessellation.

  • Lookups

    Find an order by order_no, then its payments and shipment by order_id. Those fields are indexed; a filter on status scans instead, so compare the timings.

  • Functions

    Run the saved ones: find_order by number, orders_by_status, revenue_by_country since a date, and place_sandbox_order, a transaction that writes to the sandbox. Each runs with your permissions.

  • Streams

    Open sandbox-events: you're subscribed live, the way your own code would be. Change a sandbox order on the Documents page (in another tab) and watch the change arrive, or publish a message yourself. Subscribe from your code shows the same thing with curl, a WebSocket, a consumer group or a webhook.

  • Queues

    Open sandbox-jobs and be a worker: Receive takes up to three jobs, each leased to you for 60 seconds. Acknowledge one and it's done; release it, or let the lease run out, and it goes back for the next worker; after three tries it lands in sandbox-jobs-dead. Send your own, and see the worker loop in curl or Node.

  • Files

    Open the Files page and browse media: play a WAV master from the list and seek through it, watch a music video, open the artwork, or search for "mermaid". In Queries, SELECT track, title, meta.duration_ms, meta.sample_rate FROM media WHERE artist = 'Ashes Gone' AND content_type = 'audio/x-wav' ORDER BY track.

  • Scanned text

    In Files, open media then ocr-samples: scanned letters, orders and reports from 1939 to 1969 whose text HexDB read with OCR (Tesseract). Open one to see what it read, or search media for "Peace Corps" or "Crusade". Typed and printed pages read well; the handwritten note doesn't, so nothing is kept for it.

  • Configuration

    Open Configuration at the bottom of the sidebar: AI and sharing settings for the whole lattice, write-only secrets, AI usage and token estimates, each hex's applied version, and the version history. It's read-only here.

  • Documents

    Pick sandbox, filter with JSON such as { "status": "paid" }, open one and change it. The write is forwarded to the Overseer if you are on a replica. The big tessellations are read-only.

The music in the media tessellation is Codex Animae by Ashes Gone, on Spotify.