Mission / principles / roadmap

A workbench that outlasts the model.

Models change every few months. Your project, your decisions and your review trail should not. Dranz keeps the engine, the model, what the agent may touch and what it cost in view, whichever model does the work.

Free · Venice private tier · macOS now, Linux in the next release

01 · Mission

Keep the loop whole.

An agent reads a project, makes a plan, runs tools, asks permission, changes files and leaves a diff for someone to review. Dranz holds that loop together and shows each part when it matters.

The loop, as the app shows it

  1. 01Read the projectEngine and model named
  2. 02Make a planPlan mode
  3. 03Run toolsTool activity
  4. 04Ask permissionApproval card
  5. 05Change filesUndo on every turn
  6. 06Leave a diffReview, line comments

02 · Principles

Five rules we build by.

Each one shows up in the app as something you can see or press.

Rule 1

The route is part of the result

Every session names its engine, its model and where inference runs. Today that answer is Venice's private tier, and the app says so plainly.

Rule 2

The agent can stop

Commands and edits that matter pause with the exact action in view. Sometimes the right button is "not yet".

Rule 3

Review is another turn

The diff lives in the conversation. Comment on a line, send it back, or undo the turn.

Rule 4

Receipts beat vibes

Cost, tool activity, files changed and tests run stay on the record after "done".

Rule 5

Privacy claims name their owner

Each route has an owner with its own promises. We say which route is in use and where its edge is.

03 · Roadmap

The order of the work.

Not a calendar of promises. The changelog records what shipped.

  1. Shipping

    The free workbench

    Five engines on Venice, approvals, review with line comments, undo on every turn, subagents, squads and a cost readout on every session. Free for macOS, with Linux in the next release.

  2. Building

    The rename to Dranz

    Cloaky becomes Dranz across the app, the site and the docs. Your settings and sessions are meant to come with you.

  3. Researching

    The real privacy boundary

    We are tracing every path a session takes: turns, assists, subagents, tools and engine vendors. The goal is better controls, clearer docs and no claim we cannot prove.

04 · How we build

Ship it, use it, say what it does.

We put a surface out, use it on real work, measure it and write down its limits. Labels stay plain: shipped, testing, researching, planned.