Open-source guide
Run Drizza locally
Start the local Drizza app and understand how it uses your machine.
Requirements
Use Node.js that matches ^22.13.0 || >=23.4.0. The project uses Node's built-in SQLite support, so use a release in the supported range.
Start Drizza
Run the package from a terminal:
npx drizza
Drizza binds to 127.0.0.1 and listens on port 4340 by default. Open http://127.0.0.1:4340/ in your browser.
Local data
The SQLite database lives at ~/.drizza/drizza.db. Drizza creates it on the first run and keeps it on your machine.
Back up your data. To preserve local Drizza data, include the database file in your own backup plan. Keep a copy only in a location you trust.
Security and tokens
- The local server binds to
127.0.0.1, so it is not exposed to other devices on your network. - The planned behavior for provider integrations is for the local process to use credentials and send requests directly to each provider. Token values are planned to stay out of Drizza-hosted services, the SQLite database, logs, API responses, and UI.
- Provider integrations and their token-management instructions are still being prepared. Exact MCP token revocation steps will be published with the MCP guide once its local token location is finalized.
Integrations
GitHub, MCP, and Slack setup guides are coming soon. This guide does not include setup commands for those integrations.