Free Desktop App

FutrixData — The AI Database Gateway
for Agents and Teams

Built for Claude Code, Cursor, Codex — and the developers who own the database. Credentials stay local. Sensitive data is masked automatically. Destructive queries are intercepted.

Download for macOS All platforms
Partially open source · View on GitHub
MySQL MySQL
PostgreSQL PostgreSQL
MongoDB MongoDB
Redis Redis
Elasticsearch Elasticsearch
ChromaDB ChromaDB
DynamoDB DynamoDB
Cloudflare D1 Cloudflare D1
FutrixData Gateway Unified control plane for AI agents and data sources Risk control Data masking Credential vault Audit log Governance pipeline runs on every query Authenticate caller Identify the AI agent and the protocol it connects with authenticated Evaluate risk Every operation is intercepted by the risk engine so AI agents can never accidentally damage your data safe Apply policy Mask PII fields and restrict the database credential to its scope PII masked Seal audit record Write a hash-chained, append-only log entry for every query (verifiable via CLI) logged Claude Code Codex Cursor Gemini Custom AI Developer · Analyst MCP Skill Console SQL PostgreSQL MySQL DOCUMENT & SEARCH MongoDB Elasticsearch VECTOR & CACHE ChromaDB Redis CLOUD DATABASE Cloudflare D1 DynamoDB

Why AI Agents Shouldn't Touch Your Database Directly

Handing an LLM a raw connection string is fast to set up — and easy to regret. Five risks show up the moment you ship.

01

Destructive Queries at 3 AM

LLMs hallucinate. A routine "clean up stale rows" task becomes DELETE FROM users with nobody awake to catch it.

02

Credentials Leak Into Prompts

Connection strings end up in the LLM's context window. One careless log export later, your postgres://user:pass@... is sitting in someone else's training data.

03

PII Shipped to Third-Party Models

Customer names, bank card numbers, biometric data — if the agent queries it, it gets serialised into a prompt and sent to OpenAI, Anthropic, or wherever your model runs.

04

No Audit Trail

"An agent did it" isn't a compliance answer. SOC 2 and GDPR both require you to reconstruct which identity ran which statement, and when.

05

Every Agent Has DBA Privileges

Agents inherit the developer's full credentials — usually read/write on every table. Least-privilege doesn't apply when a chatbot can TRUNCATE anything.

The Safety Layer Between Your Agents and Your Data

FutrixData runs locally on your machine and brokers every agent query. Credentials stay put, dangerous operations get blocked, and every query lands in a local hash-chained audit log you can verify from the CLI.

AI Agent Data Gateway

AI agents connect over MCP or Skill and only see query results — credentials never leak, raw access never leaves your machine.

Addresses #2, #3, #5

Risk Control Engine

Every statement is analysed before it runs. Destructive ops are blocked, expensive queries flagged, and every agent query lands in a local hash-chained audit log you can verify from the CLI.

Addresses #1, #4

Unified Management

A polished desktop app with a visual console and built-in AI chatbot, speaking to 8+ data sources from a single window.

Plus: one workspace for every data source
FutrixData automatically masks PII fields before AI agents see them

Agents Only See Masked Data.
Your Privacy Stays Safe.

FutrixData sits between your AI agents — Claude Code, Codex, OpenCode, Cursor — and your production databases. Agents do only what they are allowed to, and never touch sensitive data or connection credentials.

Connect via MCP or Skill

Database passwords, connection strings, and auth tokens never leave your machine. AI agents connect through standard protocols and only receive sanitised results.

Automatic Data Masking

Fields tagged as sensitive are hashed on the fly, so your most valuable data never makes it into an LLM prompt.

Works over MCP or Skill
Zero credentials exposed to LLMs
PII masked before it reaches the agent
Every operation passes through risk control
Works with Claude Code, Codex, OpenCode, Cursor
FutrixData risk engine blocking a destructive DROP TABLE query from an AI agent

Block Destructive Ops

DROP TABLE, TRUNCATE, and mass DELETE are intercepted automatically and require human approval to proceed.

Pre-flight EXPLAIN

Queries are EXPLAIN-checked first. Full table scans, missing indexes, and costly joins are caught before they can hurt your production data.

Schema Changes

DDL that drops indexes, alters primary keys, or changes critical structures requires explicit, configurable human confirmation.

Customisable Rules

Scope rules by data source, entity pattern, or operation. Row count and query cost thresholds are fully configurable.

Every Operation Analysed
Before It Runs

The core safety net. Whether a statement comes from an AI agent or a human, the same risk engine inspects it first — and dangerous operations are actively blocked.

FutrixData desktop console managing MySQL, Postgres, MongoDB and Redis from one window

One App for
Every Data Source

A polished desktop console that lets you manage databases, run queries, and collaborate with an AI assistant — all from a single window. No more juggling tools.

Visual Console & Schema Browser

Monaco-powered SQL editor, virtual result tables, EXPLAIN visualisation, execution history, and light/dark themes.

Built-in AI Agent

Describe what you need in plain language. The agent drafts an optimised query, runs it through the risk engine, and charts the result.

BYOK — Anthropic, OpenAI, Google, DeepSeek, Ollama, local models
MySQL, PostgreSQL, MongoDB, Redis, ES, and more
Natural language to SQL with chart rendering
Monaco editor with syntax highlighting
Relational, document, vector, KV — one unified view

Need a Self-Hosted Gateway?
Bring FutrixData Inside Your Network.

FutrixData Enterprise Edition is the server build of the same gateway — deployed inside your own network and governing every AI agent that touches production data. Same risk engine, same PII masking, plus central admin, agent admission, and instant revocation.

Self-hosted, your perimeter

Ships as a Docker image with Compose and Kubernetes recipes. Database credentials and AI inference can stay entirely inside your network.

Per-agent identity & access keys

Every Claude Code, Cursor, Codex, or in-house agent gets its own access key. Grant, scope, and revoke individually without affecting the rest.

End-to-end audit log

Every tool call records the agent, source, target, statement, outcome, and any matched rule — ready for compliance review and incident response.

Instant revocation

Cut off any agent's future access in real time. Long-running operations are re-checked mid-flight; revoked agents keep full historical audit.

Built for platform, security, and data teams in regulated industries.

Three Steps to Safe Data Access

From download to your first AI-assisted query in under five minutes.

1

Connect Your Databases

Add MySQL, PostgreSQL, MongoDB, Redis, Elasticsearch, ChromaDB, DynamoDB, or D1. Credentials are encrypted and stored locally.

2

Enable MCP / Skill

One command registers FutrixData as a tool for Claude Code, Codex, OpenCode, Cursor, or any MCP/Skill-compatible agent.

3

Operate with Confidence

Every operation goes through the risk engine. Dangerous ones are blocked, sensitive fields are masked.

Download FutrixData

v1.0.27

Free desktop app. Connect your databases, turn on the gateway for your AI agents, and manage everything from a single window.

Using Codex? Add the FutrixData plugin to Codex and authorize it in a few steps.
Codex plugin setup guide

What is new in this release

v1.0.27 adds the Codex plugin flow, Vault-backed secret references, a 30-day local trial, and clearer SQL and datasource diagnostics.

  • Codex users can install the FutrixData plugin, authorize it from the desktop app, and use the bundled sidecar and skill assets without hand-wiring MCP config.
  • Teams can point datasource credentials at existing HashiCorp Vault KV v2 secrets; FutrixData stores only reference metadata and strips stale inline plaintext.
  • New local users get a 30-day trial, including logged-out use, with plan limits applied consistently across datasources, risk rules, sensitivity rules, and daemon access.
  • The SQL console now catches common syntax mistakes before execution, shows friendlier database syntax errors, and preserves datasource timing diagnostics in the Wails runtime.

No manual migration is required. Vault-backed credentials require an existing Vault KV v2 secret and provider configuration; Codex plugin users should authorize the plugin from the desktop app.