Design partner program

We're building this with 5 design partners. Be one of them.

People, teams, and systems improve through exploration, not by getting the design perfect upfront. If your agents already work across experiments, evals, logs, or artifacts, we're looking for design partners to help shape a workspace where every token does more useful work.

Talk to an engineer Read the benchmark First cohort: 5 teams.

Fit check

Who we're looking for: teams running agents over experiment tracking data, eval pipelines, or artifact-heavy research workflows — and platform teams giving internal agents a workspace. You should have the problem today (you've probably already glued together S3 + JSON + a tracker DB) and want to influence what gets built.

The deal

A straight trade.

Eight cells, no fine print.

What you get

Direct access to the core engineers (shared Slack channel)

Hands-on deployment help, free

Token-bill instrumentation of your agent workloads (the benchmark harness, pointed at you)

Roadmap influence — design partners vote first

What we ask

Timely, transparent feedback in a shared Slack channel (engineer-to-engineer, directly)

Your real workload shape (scale, agent concurrency, current stack)

Honesty about what breaks

A quotable, quantified result at the end (with your name and title)

Read this before you apply

Where NoKV actually is.

NoKV is early — single-node today, distributed metadata on the roadmap. That's exactly why design partners get outsized influence: the multi-node layer will be shaped by your workload, not our guesses.

Status today single-node no HA yet POSIX incomplete

Apply

Tell us about your workload.

Five fields, no scheduling widget. Submissions go straight to the engineers building NoKV.

  1. 01An engineer reads your submission — every one of them.
  2. 02You hear back within a few days.
  3. 03If it's a fit, we set up the first 30-minute call and get you running.
First cohort: 5 teams.

Forms aren't the only door. Ask anything in GitHub Discussions →