Licence
Oxys DB Studio is distributed under the terms of either the MIT licence or the Apache License 2.0, at your option. You may use, study, change and redistribute it, including in commercial settings, under the conditions of the licence you choose. See the licence page for details.
Everything the project ships is held to the same standard: its dependencies, bundled tools, fonts and icons are under permissive licences, checked by the build on every change. The few exceptions, such as fonts under the SIL Open Font License, are recorded decisions and credited in the attributions.
What is in the repository
| Part | What it is |
|---|---|
oxysdb | The desktop application, with a GPU-drawn interface |
oxysdb-cli | The command-line client: every command of the app, plus the local MCP server (read-only tools) run headless |
oxysdb-server | The self-hosted team server |
oxysdb-runner | The self-hosted task runner |
crates/ | The engine, the MongoDB backend, import and export, SQL translation, migration and more, as Rust libraries |
deploy/ | Container images, Docker Compose profiles and the Helm chart |
The engine is separate from the interface: every action is a command with a stable identifier and JSON parameters, so the desktop app, the command-line client and the local control channel all use the same code. AI agents use the read-only tools of the local MCP server.
Contributing
Contributions are welcome: bug reports, documentation, translations and code.
- Start with the repository’s
AGENTS.mdanddocs/contributing.md. They describe the layout, the rules every change follows (no panics, tests against real databases, one command per action), and how to add a command. - Every change comes with tests. Database behaviour is tested against real servers started in containers, not mocks.
- Open an issue before a large change, so we can agree on the approach.
Browse the source code · Open an issue
Security
Please report vulnerabilities privately, through a confidential issue, as described in the security policy. Do not open public issues for security problems.
Privacy
The application has no telemetry, no analytics, no crash reporting and no account. The repository lists every outbound connection it can make, and its checks fail if a part of the code that can make web requests is missing from that list. See privacy.