Team and advisors

Who builds 0dai

0dai is a small team building one canonical context layer for AI agent CLIs. This page states the team composition, the advisory bench, and what we are hiring next — without inflating the org chart.

Work with usSee the contribution graph

Current release

v4.3.6

Supported agent CLIs

7

Registered MCP tools

113

Core team today

1

Team

The people behind the repo

0dai runs lean today. We name the team rather than hide behind a single anonymous public face, and we update this page as the team grows.

Founder & Engineer

Founder / EngPlaceholder

Builds the CLI, MCP layer, and agent protocol. Prior background in developer infrastructure and tooling. Operates the public repo and release cadence.

Advisors

Advisory bench

Advisors give us infrastructure and go-to-market reach beyond the core team. Seats below are open; we publish them as they are filled.

Advisory seat — Infra/DevTools

AdvisorPlaceholder

Open advisory seat for a developer-tools or infrastructure operator who has shipped a CLI or platform at scale.

Advisory seat — GTM

AdvisorPlaceholder

Open advisory seat for go-to-market guidance on developer-first, bottoms-up adoption.

Hiring

What we are hiring next

The next two quarters are about reducing single-author risk on the runtime and building a repeatable adoption motion.

First ML / agent engineer

Next 6 months

Owns model routing, eval harness, and the agent protocol guardrails. Reduces single-author bus factor on the core runtime.

First GTM / developer-relations hire

Next 6 months

Owns docs, onboarding, and the activation funnel. Turns the open repo into a repeatable adoption motion.

Contract design / front-end support

As-needed

Part-time help on the marketing surface and dashboard polish while the core team stays small.

Interested in a role or an advisory seat? Email hello@0dai.dev.

How we work

Principles that shape the team

A small team scales by being legible. These are the constraints we hold ourselves to.

State team size plainly

No inflated org chart. The page reflects who actually works on 0dai today, including when that is a small team.

Work in the open

Source, issues, and release history are public. The contribution graph is the most honest team page we have.

Local-first by default

Source code and secrets stay on the operator machine. Trust is a product constraint, not a marketing line.