Security
Summary. Local-first, credentials encrypted on your machine, zero telemetry, signed updates and a bounded MCP server. Operations run with your IAM permissions and at your responsibility.
Credentials and local data
- Secret keys, session tokens and proxy credentials live in a local store encrypted with AES-256-GCM, with permissions restricted to the user. They never leave your machine.
- The license key is stored encrypted and bound to the machine.
- Error messages hide credentials in URLs and proxies.
Safeguards when operating
- Read-Only mode is enforced in the backend (Rust), not only in the interface; connections tagged
prodopen read-only. - On AWS with the Free plan, PartiQL accepts
SELECTonly. - Confirmations and a change review (Staged Changes) before writing, plus local undo.
MCP server
Read-only by default; it does not expose PartiQL; every call has caps (one request, ≤ 100 items, 1 MB). Write tools must be enabled explicitly and do not work in Read-Only. Still, the MCP acts with your credentials and IAM permissions and at your responsibility: use a least-privilege role.
Updates and distribution
CaesarDB is closed-source and distributed as signed binaries. Updates are downloaded from GitHub Releases and signature-verified before installation. Dependencies are audited regularly.
Your part
Keep backups enabled (PITR), use least-privilege credentials, enable your operating system’s disk encryption and watch your AWS costs.
Report a vulnerability
Write to cgarrui0301@gmail.com with a description, steps to reproduce, version and operating system. We ask for responsible disclosure: do not publish the flaw before it is fixed. We appreciate the report and will reply as soon as possible.