General Purpose Database Agent & Proxy for deploying databases in Docker Containers at a scale.
  • Rust 98.7%
  • TypeScript 1.1%
  • Shell 0.2%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Calagopus Mirror Bot 179c5bf341
Some checks failed
Build and Push Registry Image / Build db-agent image(s) (push) Failing after 1m1s
ci: add db-agent registry build workflow
2026-09-17 07:16:19 +00:00
.forgejo/workflows ci: add db-agent registry build workflow 2026-09-17 07:16:19 +00:00
.github fix ci #2 2026-09-17 08:58:49 +02:00
database simplify instance state migration 2026-08-23 11:15:11 +02:00
src fix ipv6 bracket bug 2026-09-16 22:22:29 +02:00
.gitignore upload files 2026-07-07 14:41:20 +02:00
build.rs upload files 2026-07-07 14:41:20 +02:00
Cargo.lock update deps, less request logging under load 2026-09-15 11:12:35 +02:00
Cargo.toml [ci skip] license 2026-09-16 19:06:15 +02:00
compose.yml some code cleanup, fix compose issue 2026-07-19 00:17:54 +02:00
Cross.toml fix ci #2 2026-09-17 08:58:49 +02:00
Dockerfile upload files 2026-07-07 14:41:20 +02:00
LICENSE [ci skip] license 2026-09-16 19:06:15 +02:00
README.md [ci skip] update documentation 2026-09-10 14:28:11 +02:00
SECURITY.md [ci skip] update documentation 2026-09-10 14:28:11 +02:00
tag-release.sh upload files 2026-07-07 14:41:20 +02:00

Calagopus Logo

DB Agent

Rust License GitHub issues GitHub stars Discord

db-agent is a high-performance, low-latency database proxy and agent written in Rust. It is designed to handle database-routing and provisioning for PostgreSQL, MySQL, Redis and MongoDB, with a focus on security, scalability, and ease of use. It provides a dedicated REST API for management.

To be compatible with ridiculous versions of various specifications, we only ever parse & "handle" the authentication phase of the database protocols, ensuring that clients can connect seamlessly while maintaining security and protocol compliance. After authentication, db-agent hands off the full duplex communication to the respective database server, allowing normal operation to continue without interference.