HYDRALive

A work console your agents and scripts can file into directly

A multi-tenant work console whose primary interface is a scoped API, so the script or agent doing the work files and closes it directly. Work belongs to the product it is for, not to one flat list.

A senior engineer replies within one business day.

HYDRA — end to end
  1. Entry tree
  2. Scoped API key
  3. Agents file + close
  4. Console stays true

Why this exists

Task tools assume a human types everything in. When half your work is done by scripts and agents, the tracker drifts from reality within a week.

A multi-tenant operations console with a scoped API that other projects drive directly, so work is filed by the agent or the person doing it rather than copied into a tracker afterwards.

What it does

Everything HYDRA handles for you.

  • Entry tree, not a flat list

    Work belongs to the product it is for, which is what makes a task list survive more than one project.

  • Scoped API

    A versioned /api/v1 with per-key scopes, so tools and agents file and close their own work.

  • Multi-tenant

    Organisations, roles and invites — it is a real workspace, not a single-user notes file.

  • Asks questions of its own data

    Follow-up questions are answered against the relevant entry through Heimdall and saved back to it.

What you get

Concretely, what lands.

Not adjectives — the things that exist afterwards that did not exist before.

  • Work filed against the product it is for — an entry tree rather than one flat list that collapses at the second project.
  • A versioned /api/v1 with per-key scopes, so tools and agents create, update and close their own tasks.
  • Organisations, roles and invites — a real multi-tenant workspace, not a single-user notes file.

How it works

From nothing to working.

  1. Model the work as a tree

    Every task belongs to an entry — the product or item it is for — and can nest under a parent. That is what lets a task list survive more than one project.

  2. Hand out scoped keys

    A key per tool or agent, with only the scopes it needs. Anything a caller may not see answers 404 rather than 403, deliberately.

  3. Let the workers write

    Scripts and agents POST what they surface and PATCH it closed when it is done, so the console reflects reality without anyone transcribing.

  4. Ask it questions

    Follow-up questions are answered against the relevant entry through Heimdall and saved back to it, so the answer stays with the work.

Who it's for

Built for these people.

If you are not one of them, we will say so rather than sell you a seat.

  • Solo founders and small studios running several products at once
  • Teams whose agents and scripts should be filing work directly

Pricing

Two ways to buy it.

HYDRA can run on our infrastructure under your brand, or on yours. The difference is who gets the call when it breaks.

ManagedWe run it.
$99/mo

per branded workspace · $900 setup

  • Deployed under your brand, on your domain
  • We host, monitor, patch and update it
  • A failure at 2am is ours to fix, not yours to diagnose
  • Monthly — cancel when it stops being worth it
Start managed
Self-hostedYou run it.
$1,600 once

+ $400/yr updates and support

  • Runs on your own infrastructure, inside your own network
  • One production instance, plus as many staging and local copies as you need
  • Yearly renewal covers updates, security patches and support
  • Source code is not included in either tier
Get a quote

Before you ask

The questions that come up.

  • It is a task manager with the assumption inverted: the API is the primary interface and the UI is the second one. If all your work is typed in by people, a normal tracker is cheaper and you should use one.

  • Scoped keys and the entry tree. An agent can only write where its key reaches, and a task with no entry is rejected rather than landing in a general inbox.

  • Both — a branded workspace we run, or a one-time licence with annual updates. Licensed per instance.

  • It is what the studio runs on. It replaced the tool we had been using, which we then killed.

Run HYDRA on your side.

A few lines is enough. A senior engineer reads it and replies within one business day — and says straight away if it isn't a fit.

Or email us directly at contact@caffinix.com.

Or email contact@caffinix.com. We sign a mutual NDA before scoping if you need one.

Built on·Next.js 16 · Postgres/Drizzle · Heimdall

← All products
HYDRA
Live
Start →