Which databases can I run locally with TableHub?

TableHub can spin up local PostgreSQL, MongoDB, and Redis via Docker. It can also open local SQLite files. Once a database is running, you query it in the same app with a built-in AI agent that works across both SQL and NoSQL.

Yes. TableHub is completely free and cross-platform on macOS, Windows, and Linux. Spinning up local databases, the query editor, the AI agent, and result charts are all included with no paywall.

Local databases, one click

Spin Up Local Databases with Docker — From One GUI

Q: Do I need Docker installed?

Yes. TableHub uses your local Docker installation to create and run the containers, so Docker must be installed and running on your machine. TableHub does not bundle its own container runtime — it drives the Docker you already have.

Need a fresh Postgres, MongoDB, or Redis instance to test against? TableHub spins one up via Docker in a single click — no docker-compose files, no YAML, no separate launcher — then lets you query it immediately with a built-in AI agent. Free, and native on macOS, Windows, and Linux.

Download TableHub — Free See all features

TL;DR — TableHub is the only free, cross-platform app that both creates a local database via Docker (Postgres, MongoDB, Redis) and queries it with an AI agent in the same window. Pick an engine, TableHub pulls the image and starts the container, and it shows up as a connection you can query right away — no compose files, no glue tools. (Requires Docker installed.)

The problem: three tools for one job

Getting a throwaway database running locally is more annoying than it should be. The usual stack looks like this:

A launcher (like DBngin) to start a Postgres or Redis instance — but it can't query anything.
A pile of docker-compose files if you want reproducible containers — YAML you have to write, version, and remember the ports for.
A separate SQL client (TablePlus, DBeaver, DbGate) to actually connect and run queries — which can query databases but can't create them.

So you're stitching together a launcher, a container runtime, and a client just to answer a quick "what happens if I run this migration?" question. TableHub collapses all three into a single app: create the database, connect to it, and query it — with AI help — without ever leaving the window.

TableHub vs. the alternatives at a glance

Capability	TableHub	DBngin	Plain Docker + a client
Spin up local DB	One click	One click	Manual YAML / CLI
Docker-based	Yes	No	Yes
Query editor built in	Yes	No	Separate app
AI agent	Yes	No	No
Postgres / Mongo / Redis	Yes	Postgres / MySQL / Redis (native)	Depends
Cross-platform	Yes	Mac-only	Yes
Price	Free	Free	Free

DBngin runs databases natively (not via Docker) and hands querying off to TablePlus — it has no query client and no AI. Query-only clients can connect to an existing container, but none of them can create the database for you. TableHub is the one tool that does both.

How it works

Pick a database engine — choose PostgreSQL, MongoDB, or Redis from TableHub. No compose file, no port juggling.
TableHub pulls the image and starts the container using your local Docker. The lifecycle is managed for you — start, stop, and remove from the UI.
It appears as a connection in TableHub the moment it's ready. The credentials are set up locally and stay on your machine.
Query it with AI and charts — ask the built-in agent in plain English to write a query, have it explain an existing query, and visualize the results as a chart. This works across SQL and NoSQL, so the same workflow covers Postgres and MongoDB alike.

Query with an AI agent — across SQL and NoSQL

Once the database is running, you don't have to remember exact syntax to be productive. TableHub's built-in AI agent writes queries from natural language and explains existing queries in plain English. Because it works across both SQL and NoSQL, the same "describe what you want" flow applies whether you're on PostgreSQL or MongoDB. Results render in a table you can turn into a chart for a quick visual read — useful when you're exploring a fresh dataset and just want to see the shape of it.

Fast, local, and private by default

TableHub is a native app — it starts in about 2 seconds and typically uses around 150MB of RAM, so it stays out of your way. The connection to your local database is direct, and your credentials stay local — nothing about your local containers is routed through TableHub's servers.

Requires Docker — the honest note

To be straightforward: TableHub uses your local Docker installation to create and run the containers. It does not ship its own container runtime. So Docker must be installed and running on your machine for the one-click spin-up to work. If you already have Docker (as most developers do), there's nothing else to set up — TableHub drives it for you. If you prefer databases that run natively without Docker, a launcher like DBngin fills that niche, but you'll still need a separate client and you won't get the AI agent.

Frequently asked questions

Do I need to write docker-compose files?

No. TableHub creates and manages the container for you when you pick an engine. There's no YAML to author or maintain and no separate launcher to open.

Which databases can I run locally?

PostgreSQL, MongoDB, and Redis via Docker. TableHub also opens local SQLite files. Once running, you query any of them in the same app.

Is this free?

Yes — completely free and cross-platform on macOS, Windows, and Linux. The spin-up, the query editor, the AI agent, and charts are all included.

Do I need Docker installed?

Yes — TableHub uses your Docker to create the containers, so it must be installed and running. TableHub drives the Docker you already have.

Download TableHub Free