Any database, one switcher
Postgres, CockroachDB, MySQL, SQLite, MongoDB, Redis, Neo4j, DynamoDB, Apache Kafka, and the filesystem — connect several at once and switch between them from one place. Direct connections open straight from your machine.
Every database, one query workbench.
Connect to any database — SQL (PostgreSQL, MySQL, CockroachDB, SQLite), document (MongoDB), key-value (Redis), graph (Neo4j), object stores, and streaming (Apache Kafka) — browse the full object tree and run queries, all executing on your own machine. Cloud systems connect through least-privilege connectors that run in your own cloud.
In the app
Install the engine
Then open the app & sign in
data.openeng.appThe app gives you a one-time command to start the engine — copy it, run it, and the page connects automatically.
Data features
Postgres, CockroachDB, MySQL, SQLite, MongoDB, Redis, Neo4j, DynamoDB, Apache Kafka, and the filesystem — connect several at once and switch between them from one place. Direct connections open straight from your machine.
The left panel reshapes to each engine — databases → schemas → tables/views for Postgres, collections for Mongo, keys for Redis, labels & relationship types for Neo4j — loaded lazily as you drill in.
A SQL editor with a results grid, a mongo-shell runner, raw Redis commands, and Cypher with a graph view + execution plan. Results render as tables, JSON documents, or a node/edge graph — with NULLs preserved.
Reach RDS / Aurora, Amazon S3, DynamoDB, Cassandra, Google Cloud Storage, Apache Kafka (MSK / Event Hubs / Confluent), and more through a source-only connector Lambda that runs in your own cloud and holds the credentials there — the browser only sees a URL + API key.
Cloud connections are read-only by default — server-side read-only transactions plus a default-to-write statement filter refuse every write, update, and delete — and only a write key you configure grants write access.
Connection strings and credentials stay on your machine (stored 0600) and never cross the network to any OpenEng server. The browser is a thin client over an end-to-end sealed channel.
Walk topics → partitions and read messages from the earliest offset, the latest, or any offset you name — with TLS and SASL PLAIN or SCRAM, whether Kafka runs self-hosted or on MSK, Event Hubs, Confluent, or Redpanda.
Every run this session, newest first — click one to load it back into the editor against its connection and jump straight to the playground.
Point a connection at a SQLite file or a local folder with an in-app file browser that reads your disk through the engine, or browse an S3-compatible bucket through a cloud connector.
Data is a thin browser client of a local engine you run yourself. Your databases and connection strings stay on your hardware: the engine listens only on 127.0.0.1, and the page seals every frame of its session with the engine.
macOS builds are available for Terminal, Kubernetes, and Data; they are older builds pending a rebuild. There is no native Windows build of any engine yet — on Windows, run the Linux engine under WSL. Every engine and platform
The rest of the suite
Every OpenEng app is free — your account works across Terminal, Kubernetes, Data, Git, and Chat.
One platform, two pillars
The engineering apps are one half of OpenEng. The other is OpenEng AI, an agentic ecosystem for open-weight model execution: it downloads, orchestrates, and runs open-weight AI models on your own machine.
Explore OpenEng AI