DBAPI is a low-code data service platform for data warehouse developers that turns SQL into production-grade HTTP API endpoints, so teams can publish, monitor and govern data APIs without writing repetitive CRUD code.

What it is

DBAPI is a self-hosted application with a Vue front end and a Java runtime, licensed AGPL-3.0, registering around 800 stars, 239 forks and 16 open issues, with a last push on 13 June 2026. It positions itself as an enterprise data service management centre: one place to create, publish, monitor and govern every data API a team exposes.

The concrete problem it solves is the hand-written controller, service and serialisation layer sitting between a database and every consumer of its data. Rather than building one endpoint per query, a developer writes SQL on a page, binds parameters, and DBAPI generates the HTTP endpoint. Sources include MySQL, SQL Server, PostgreSQL, Oracle, Hive, DM, Kingbase, Doris, OceanBase, GaussDB, all JDBC-compatible databases, Elasticsearch through an ES DSL executor, and third-party REST services through an HTTP executor. Declared scenarios are BI reports, data dashboards, rapid frontend prototyping and AI application data integration.

Key capabilities

• Dynamic SQL with MyBatis-style #{} and ${} parameter binding, covering Select, Insert, Update, Delete and stored procedures, with a built-in run and debug SQL editor.
• DAG visual canvas for API orchestration, wired from Start through API Execution and Condition (If/Else) nodes to End, where earlier API results feed later steps and Groovy scripts reshape data.
• Security layer: clientId plus secret token auth, API-level access control, IP whitelist and blacklist filtering, API-level QPS throttling, RSA response encryption, request signing and audit logging.
• Plugin system in five categories: cache plugins such as Redis and Ehcache, data transformation, alerting through Email, SMS, DingTalk, Feishu and WeCom, parameter processing, and global transformation compatible with AMIS.
• MCP support mapping data APIs to MCP tools for Claude Desktop, Cursor, LangChain and Spring AI, plus AI-assisted SQL generation from natural language.
• Monitoring with API call history and access statistics, log storage in ClickHouse, MySQL, PostgreSQL or Doris, and Kafka buffer collection for large-scale traffic.
• Zero-downtime hot deployment of API changes, API group management, data source health checks, built-in __clientId and __apiId variables, and an OpenAPI integration interface.

Who uses it and how

• Data warehouse developers who own the SQL and want to expose it directly rather than wait on a backend team.
• BI and dashboard teams needing stable, throttled, audited endpoints for report data.
• Frontend and AI teams prototyping against real data; MCP integration reaches Claude Desktop, Cursor, LangChain and Spring AI.
• Small-footprint deployments: a standalone instance runs on a 2-core 4GB server, while the same build supports cluster mode on Windows or Linux.
• High-volume setups that push access logs through Kafka into ClickHouse or Doris instead of the primary database.

Getting started

Download the free Community Edition tarball, for example dbapi-4.0.32-bin.tar.gz, extract it, edit conf/application.properties if the default embedded SQLite database is unsuitable, then run bash bin/dbapi-daemon.sh start standalone. The console listens on port 8520 with default credentials admin / admin; JDK 8, 11 or 17 is required, and OpenSSL 3 is needed on non-Windows hosts.

How it compares

No list of paid products that this project replaces was provided, and the registry names no directly comparable tool, so DBAPI stands alone in this registry. The nearest names in its own documentation — AMIS, Claude Desktop, Cursor, LangChain, Spring AI — are integration targets rather than competing products.

When to use it — and when not to

A self-hoster must operate a Java service and its backing storage: embedded SQLite by default, or MySQL, PostgreSQL, Oracle, Doris or ClickHouse for logs, Redis or Ehcache if cache plugins are used, Kafka for buffered logging at scale, and mail, SMS, DingTalk, Feishu or WeCom credentials if alert plugins are enabled. Teams that cannot run a JVM service should look elsewhere, and anyone needing API import/export or version rollback should note those are marked Enterprise. The project is AGPL-3.0, which carries source-disclosure obligations for network services, and its README is Chinese-first with a separate English document, so non-Chinese readers may depend on the documentation site.

# Download Community Edition (free)
wget https://img.51dbapi.com/dbapi/dbapi-4.0.32-bin.tar.gz
tar -xzf dbapi-4.0.32-bin.tar.gz
cd dbapi-4.0.32

# Modify database config (default uses embedded SQLite)
# vim conf/application.properties

# Start service
bash bin/dbapi-daemon.sh start standalone