Runs on your own machine
Volath is a local dashboard. Your code, tickets and settings live in a local SQLite database on your computer, or in a MySQL or MariaDB database that you run.
Runs locally
AI coding agent security and privacy
It runs on your own machine. Your code, tickets and settings live in a local SQLite database, or in your own MySQL or MariaDB. You decide which steps need your approval and which AI provider does the work.
Local-first
Volath runs on your own machine. Your code, tickets and settings live in a local SQLite database, or in your own MySQL or MariaDB.
Credentials are encrypted on your machine
Tokens and API keys you enter are stored encrypted in the data folder of Volath, with a key generated on your computer. Back up the database if you care about your history.
SQLite backup before every migration
Before an update changes the SQLite database, Volath copies it to the backups folder inside its data folder and keeps the latest 10. To undo an update, quit Volath and put that copy back as database.db. With MySQL or MariaDB no automatic backup is made, so back the database up with mysqldump before updating Volath.
Control
By default the pipeline runs on by itself. These settings let you hold, limit and observe what the AI does.
Hold steps until a human approves
Policies can require approval before the AI starts developing, before the pull request is opened, or before the merge into staging. Nothing is held until a policy is turned on.
Auto-run only what you allow
Policies can auto-run only tickets with a label such as safe, and only while the AI spend on the ticket stays under a limit.
Signed webhooks
With a secret set, each webhook carries X-Volath-Signature: sha256=<HMAC-SHA256 of the raw body>, so a receiver can verify it.
Turn memory off
Memory learns lessons from merged tickets, rejected pull requests and review comments. Learning can be turned off per project (Settings › AI › Project memory) and per ticket (Options › Learn from this ticket). You can review, edit or delete the lessons.
Plugin trust
Plugins are optional. When you use them, these rules decide what a plugin can and cannot do.
Plugin code runs in its own process
Plugin code runs in its own Node process with the permission model of Node: no child processes, workers, native addons or file access outside the plugin's folder, 256 MB of memory, and none of the environment of Volath, so tokens and keys do not reach it. This needs Node 22 or newer. Without it the code is refused unless the sandbox is turned off, and the app then says so.
You accept what a plugin asks for
Every call goes through Volath, which checks it against the permissions the administrator accepted, read in plain words on the install screen. A plugin stays off until they are accepted, and a new version that asks for more stays off until they are accepted again.
Plugins have hard limits
A plugin does not receive events its own changes caused, is limited to 120 changes a minute, and a call times out after 60 seconds. One that crashes five times in ten minutes is switched off. It can never delete tickets, projects or custom fields, read project or ticket settings, change anyone's email or password or create sign-in accounts, and a person's email never reaches it.
Marketplace installs are checked
Every marketplace download must carry a sha256 that matches the list, and the package must have the id of the entry, or the install is refused. A policy for administrators can refuse zip installs (marketplace only), and auto-update updates marketplace plugins only when the new version asks for nothing more.
You can see where a plugin came from
Everything a plugin creates shows "from plugin X". Each plugin says whether it came from the marketplace or from a zip that Volath has not reviewed. The install screen warns when a plugin looks like it reimplements a feature of a paid plan, or asks for admin access or a wildcard network host, and the Health and Logs views show what a plugin did.
The honest limit of plugins
Node cannot close the network for a process, so plugin code could open a connection without going through Volath. Install plugin code only from people you trust, prefer plugins from the marketplace, and use the marketplace-only policy on a shared instance. Declarative plugins have no code.
Know before you run it
What Volath can do on your machine, so you can decide where to use it.
Agents can write to your project folder
Volath runs AI agents with write access to the project folder. Use it on repositories you trust.
Your Git host token opens pull requests
Volath can push branches and open pull requests with your GitHub token. Review the pull requests it opens.
Reset to default settings
Quit Volath and delete its data folder to start again from the setup wizard. It removes the database and stored screenshots, so tickets, projects, developers, API tokens and every setting are gone, and it cannot be undone. Export a backup first if you want to keep anything.
AI providers
You choose the AI provider
Use a CLI or an API key. The provider and model are configurable globally, per project and per ticket.
- Claude Code
claudeCLI - Codex
codexCLI - GitHub Copilot
copilotCLI - OpenCode
opencodeCLI - Anthropic APIAPI
- OpenAI APIAPI
FAQ
Security and privacy questions
Does Volath run on my own machine?
Yes. Volath is an app you install and run on your own machine. Your code, tickets and settings live in a local SQLite database on your computer by default, or in your own MySQL or MariaDB.
Can I choose the AI provider and model?
Yes. The provider and model are configurable globally, per project and per ticket. An empty project field uses the general value.
How do I stay in control of what the AI does?
You follow every ticket from a Kanban board. Under Project settings › Policies you can hold steps until a human approves: before the AI starts developing, before the pull request is opened, or before the merge into staging. By default the pipeline runs on by itself, and nothing is held until you turn a policy on.
Is it safe to run Volath on my repositories?
Volath runs AI agents with write access to the project folder and can push branches and open pull requests with your GitHub token. Use it on repositories you trust, and review the pull requests it opens.
Does the AI learn from my project?
Yes. Memory keeps lessons per project from merged tickets, rejected pull requests and review comments. Active lessons are added to the prompts of analysis and development. You can review, edit or delete them, and turn learning off per project and per ticket.
Are plugins safe?
Plugin code runs in its own Node process with the permission model of Node, with none of the environment of Volath, and every call is checked against the permissions the administrator accepted. A plugin stays off until they are accepted, and it can never delete tickets or projects. Node cannot close the network for a process, though, so install plugin code only from people you trust. Declarative plugins have no code.
Can Volath use MySQL or MariaDB?
Yes. SQLite is the default and needs no setup. To use MySQL 8 or later or MariaDB instead, create an empty database and set the VOLATH_DB_ variables in backend/.env. Versioned migrations and the automatic backup before a migration are SQLite only, so back up a MySQL database with mysqldump before updating Volath, and note that existing SQLite data is not moved over.
Can Volath notify other tools?
Yes. Webhooks send events such as ticket.status_changed, pr.opened, ci.failed and deploy.finished as a JSON POST, signed with HMAC-SHA256 when you set a secret. Set Send as to Slack or Teams to get a readable message instead.
Run Volath on your own machine
It runs on your own machine. Your code, tickets and settings live in a local SQLite database, or in your own MySQL or MariaDB.