On this page
Requirements
| Platform | What you need |
|---|---|
| macOS | macOS 13 (Ventura) or later, on Apple silicon or Intel. A DMG and a ZIP. |
| Linux | Coming in the next release (0.1.2), which is in testing: an AppImage, a .deb and an .rpm. The AppImage needs FUSE 2: the libfuse2 package (libfuse2t64 on Ubuntu 24.04 and later). Without it, start the AppImage with --appimage-extract-and-run. |
| Windows | No build. |
The Apple silicon build gets the most testing. Reports from Intel Macs, and from Linux on Wayland or X11 once that release ships, are especially useful.
Download
Dranz builds will be linked here as they ship. Until then, join early access and we will email you the day a build is ready.
Release builds for macOS are signed with a Developer ID certificate, notarized by Apple and stapled, so a downloaded copy opens with the standard first-launch prompt and nothing else. Every release attaches a SHA256SUMS file. To verify a download before you open it:
spctl -a -vv /Applications/Dranz.app # source=Notarized Developer ID
shasum -a 256 -c SHA256SUMS # SHA256SUMS is attached to every release
Your Venice key
Every session in Dranz runs on Venice, with your own key. Create one from an account with credit at venice.ai/settings/api. On first launch, onboarding checks the key and the balance before anything else can start.
You do not need an account with any engine's vendor. Dranz gives each engine a per-run configuration that points it at Venice, so every engine uses your Venice key and Venice models.
Engines
Dranz runs five engines: Claude Code, OpenCode, Codex, Kimi Code and Grok Build. Engines are yours. Install each with its vendor's own command; Dranz finds them on your machine, and each keeps itself up to date.
Onboarding and Settings › Engines show which engines are installed and the command for each of the rest.
First session
- Open a project folder.
- Pick an engine and a model. The picker shows the provider and the privacy tier for every row.
- Choose a permission mode. Plan reads and proposes. Approve for me asks before every edit and command. Accept edits asks only before commands. Full access never asks.
- Describe the work. Edits and commands that need you arrive as approval cards with the exact action in view.
Lookout, the optional second opinion, is off until you turn it on. See Lookout.
Updates
Dranz can update itself. Press Check for updates in Settings › General, or leave Check for updates automatically on. The Update channel setting there offers Beta, for builds before they are released as stable. You can also download a new version and replace the app.
The signing identity stays the same across versions, so macOS keeps the folder permissions you granted.
Where your data lives
Settings, sessions and local records live in one folder in your home directory, outside the app, so they stay in place when you update. Today that folder is ~/.cloaky.
Settings › Start fresh removes local history and keeps your credentials, logins and engine settings. Deleting the whole folder resets Dranz to a first launch, including the Venice key.
What leaves your machine, and when, is on Privacy & data.