DevRel proposal · v1 · outside-in

A 12-month DevRel program built around Tenki's agent-era compute thesis.

An outside-in plan for Tenki — the developer platform for AI code review, drop-in GitHub Actions runners, and disposable microVMs for AI agents (a product of Luxor Technology). Built by a developer-relations leader who shaped the developer program at Cisco Meraki, led DevRel at MetaMask, and brings an 86k-developer community — tuned to Tenki's wedge and the agent era.

Engagement: Full-time / 90-day pilot / fractional North star: Weekly active workspaces running ≥2 products Role: Head of Developer Relations (SF)
The setup

Tenki has a real product and a captive cost moat. What it doesn't have is a developer brand.

Three products shipping weekly on one Firecracker substrate, on compute Luxor owns. But almost no public customers, no community, no content engine, an empty blog. That gap is the entire DevRel opportunity — and the timer is running.

68.9%
AI review recall
~2× the next best · first-party benchmark
up to 60%↓
Runner cost vs GitHub
+30% faster · one runs-on change
81
Releases since Apr 2025
~1 ship/week from a tiny team
~0
Named public customers
the gap DevRel closes

Why DevRel is the lever. Tenki doesn't need more engineering hours — it needs a developer brand, public trust (especially on the precision/honesty front), named references, and a defining agent-era narrative before better-funded incumbents (Blacksmith, Depot) and the AI-review pack (CodeRabbit, Cursor) define the category for it. We attack those gaps directly — and bring an 86k-developer audience to seed the funnel on day one.

The thesis — in Tenki's words

Compute is the new digital oil.

"We started Tenki on the belief that compute is the new digital oil. As global demand for compute accelerates, scalable and tradable compute is set to become one of the most valuable markets of our lifetime."

— Tenki, About

Tenki was born inside Luxor — a profitable, SOC-2 Bitcoin-mining infrastructure company — as it extended its "compute as a commodity" thesis from mining into generalized, AI-era compute. The dev products (runners, review, sandbox) are the consumer wedge; Luxor's owned compute and GPU marketplace are the supply.

This is the through-line for every post, talk, benchmark, and pitch: the agent era runs on compute you can trust — Tenki is where it runs.

The real wedge

Three products that are secretly one product.

Runners, Code Reviewer, and Sandbox all run on the same Firecracker microVM substrate. In the agent era they converge into one thing: where an autonomous agent writes, runs, and gets its code reviewed in isolation. No competitor owns the whole loop.

Moat

One Firecracker substrate

CI + review + agent sandboxes on the same per-job-isolated microVMs. The convergence story is the differentiation pure-plays can't match.

Moat

Owned compute = cost moat

Tenki rides Luxor's captive bare-metal (mining + the new GPU/AI build-out) instead of paying retail cloud margins like every VC-funded competitor.

Narrative

Trust, not just recall

Code Reviewer leads recall (68.9%) but trails on precision (29.9%). The honest gap is the most interesting unsolved problem in the category — and our content engine.

Distribution

86k developers on day one

dabl.club's audience (36–40% open rate) becomes an attributed acquisition channel feeding Tenki-owned community, benchmarks, and events.

Sharpened from using the product

Own the category no one else is claiming: long-running, self-improving agents.

Field notes from hands-on use and a read of the live sandbox market — threads I'd pressure-test with the team in week one.

Positioning

The long-running-agent wedge

E2B, Modal, and Daytona optimize short-lived sandboxes — spin up, run, tear down. The 2026 frontier is long-running, self-improving agents. Tenki's persistent volumes + snapshot/restore + microVMs fit that — a category no competitor is claiming.

Day-1 deliverable

Win the first five minutes

I installed the Sandbox ADE — the native-app approach is a real edge over hours of self-hosting Daytona — but hit a setup snag on first deploy. The highest-leverage first move: a First-Five-Minutes audit to get time-to-first-successful-sandbox under five minutes.

Edge

Sandbox-first, easy, affordable

Most "sandboxes" are afterthoughts of a cloud business; Daytona is great at visibility but expensive and hard to self-host. Tenki wins on a sandbox-first brand, easy native UX, and owned-compute price.

And the GTM to match: capture adjacent communities (E2B/Modal/Daytona, plus the Cursor / Codex / Claude Code crowds) via multipliers; run hackathons as lead-gen, not prototype-gen — customer targets in the judge seats, partners co-sponsoring, and a branded event hub that spins off content.

The 7 initiatives

Seven coordinated programs, each attached to a SWOT lever.

A proven 7-initiative framework, tuned to Tenki's wedge. Every program ties to a Strength to amplify, Weakness to close, Opportunity to capture, or Threat to neutralize.

1

The Tenki Benchmark Series (the trust engine)

Attacks W2 (precision/trust gap), S5 (recall lead), T7 (AI-review credibility)

The flagship is TenkiBench — the agent × open-model matrix (every coding agent × every open model, sliced both ways), run end-to-end on the stack: Runners orchestrate, Sandbox runs each pairing in parallel, Luxor compute serves the models, plus bring-your-own-evals. Alongside it: reproducible AI-review, runner, and sandbox benchmarks — published even where Tenki loses (honesty is the credibility). Leaderboard at tenki.cloud/benchmarks.

2

Agent-Era Reference Architectures (Sandbox + BYO-agent)

Attacks S6 (Sandbox), O2 (agent explosion), O4 (CI convergence), T4 (E2B/Modal)

Official, maintained references: Claude Code + Sandbox (co-marketed with Anthropic), Codex + Sandbox (OpenAI), Cursor / Devin / Cline. Each ships a repo + 5-min video + guide + cost calculator. "Give your agent root without giving it yours."

3

The 2-Minute Migration Engine

Attacks S1 (drop-in), O1 (GitHub pricing backlash), W6, T2/T6 (commoditization)

Migration content + Migration Wizard storytelling, honest comparison guides (vs GitHub Actions, Depot, Blacksmith, Namespace), a public cost calculator, and a first-five-minutes onboarding overhaul that crushes time-to-first-green-run.

4

Community + Content Engine

Attacks W3 (no community/brand), W8 (unknown)

Discord (per-product + per-agent channels), weekly office hours, weekly build-in-public stream, biweekly newsletter, "How I ship with Tenki," coordinated HN/Reddit/X launches, podcast guesting — seeded from dabl.club's 86k developers.

5

Design Partner Cohort (manufacture the references)

Attacks W1 (no public customers), W8

12-week cohorts · 8–10 companies · 4 batches/year. White-glove onboarding in exchange for case studies with quantified ROI, quotes, co-presented talks, and logos. Quarterly public Demo Day livestream.

6

Tenki for Open Source + Champions + Hackathons

Attacks W1, W3, W5 (not OSS → no flywheel), O7

Free Runners + Code Reviewer for public repos; a Champions program for sustained contributors; an "Agent Camp × Tenki" hackathon series (leveraging the dabl.club event engine) where devs build on Sandbox; plus OSS PRs where Tenki was the assistant, diff + prompt history attached.

7

Strategic Channel & Ecosystem Integrations

Attacks O6 (co-marketing), T2/T3/T4 (incumbent threats → distribution)

GitHub Marketplace listing; Anthropic (Claude Code) + OpenAI (Codex) + Cursor co-marketing via the Sandbox references; AI-agent registry placements; the Luxor compute/enterprise tie-in; alliances across the AI-coding ecosystem.

12-month phasing

Three phases, three marketing moments.

PHASE 1 · MONTHS 1–3

Foundations

Instrument the funnel + DevRel scorecard · first-five-minutes overhaul · Discord + weekly office hours + weekly build-in-public stream · Benchmark Drop #1 (the AI-reviewer teardown) · migration comparison guides + cost calculator · Cohort #1 opens · dabl.club cross-pollination begins.

Milestone: community seeded (500+ engineers), funnel instrumented, 1 benchmark live, time-to-first-run improving.

PHASE 2 · MONTHS 4–6

Agent-era push

Sandbox reference architectures (Claude Code, Codex, Cursor) · Anthropic/OpenAI co-marketing · Agent Camp × Tenki hackathon #1 · Cohort #1 Demo Day livestream · Benchmark Drop #2 · Tenki-for-Open-Source launch.

Milestone: 1,500 weekly active workspaces, 8 case studies in flight, agent-era narrative landed.

PHASE 3 · MONTHS 7–12

Scale + enterprise

Flagship event presence (AI Engineer World's Fair, GitHub Universe, KubeCon) · enterprise references + the Luxor compute narrative · Champions program · Cohorts #2–3 · Benchmarks #3–4 · first analyst attention.

Milestone: 3,000 weekly active workspaces, 20 named references, 150 paid Team/Enterprise accounts.

What I deliver

The operating system — and three ways to engage.

Tenki keeps engineering focus on the product. I bring the playbook, the tools, an 86k-developer audience, and the cadence.

Always-on operating system

  • DevRel strategy ownership + quarterly OKRs
  • Content engine: writing, video, build-in-public streams
  • Community ops: Discord, office hours, newsletter
  • Benchmark publishing + reproducibility infra
  • Cohort program management end-to-end
  • Tenki-for-OSS + hackathon + Champions programs
  • Conference talk authoring + submission machinery
  • Analyst + press outreach · brand/SEO
  • Monthly metrics dashboard + executive readout

Project-based deliverables

  • Agent-era reference architectures (Claude Code, Codex, Cursor)
  • Migration comparison guides + cost calculator
  • First-five-minutes onboarding overhaul
  • Quarterly benchmark publications (open harness)
  • 8–10 cohort case studies per cohort
  • Agent Camp × Tenki flagship event

Tooling I deploy

  • OpenClaw — AI DevRel agent that triages community questions, drafts outreach, routes leads
  • MetricsBoard — public metrics dashboard
  • Cohort Portal — application + onboarding flow
  • dabl.club — 86k-developer audience as an attributed acquisition channel

Three engagement options

  • A · Full-time, all-in. Wind down Nebius over ~60 days, join as Head of DevRel. SF comp + equity.
  • B · 90-day paid pilot → convert. ~$155K for 90 days with defined OKRs + a conversion gate. The two-way-door path. Recommended.
  • C · Fractional with OKRs. $35–50K/mo retainer + programs. Operating system, lighter commitment.

Substance is identical in all three. Only exclusivity and ramp differ. Nebius conflict disclosed + wound down; location handled up front.

Why opencolin

A builder-DevRel with the playbook and the audience.

I've built developer programs from zero and led DevRel at scale — and I bring an 86k-developer audience with me. Tenki gets the operating system, the network, and a builder who ships, on day one.

Developer programs

Built Cisco Meraki's developer program

Docs, webinars, a partner ecosystem, and the reusable DevRel playbook I still run today.

DevRel leadership

Head of DevRel at MetaMask

Led developer relations through multiple L2 launches across the crypto ecosystem.

Audience

Founder of dabl.club — 86k developers

My own developer community (36–40% open rate), pivoted hard into AI agents in early 2025 — a day-one distribution channel for Tenki.

Builder first

I ship, then I write

This whole strategy and site is the proof — built before the first conversation. I'd rather file the PR than write the press release.

Next steps

Three doors. Same operating system on the other side.

If full-time fits: a ~60-day Nebius wind-down and I join all-in. To de-risk first: a 90-day paid pilot (~$155K) with defined OKRs and a conversion gate — Phase 1 of this plan, with hard metrics. Or fractional at $35–50K/mo. Same playbook in all three: Benchmark Drop #1, weekly office hours, Cohort #1, Discord, OpenClaw, and dabl.club distribution from day one.