Tenki's blog is empty. That's the opportunity: a publishing flywheel where benchmarks, reference architectures, migration teardowns, and build-in-public all reference each other. One team deep post every two weeks, one community post weekly, a biweekly newsletter, and weekly YouTube — all anchored to the trust-and-honesty wedge.
Each week ships one major artifact. Sequencing ensures each launch rides the air cover of the prior week's audience — opening with a migration win and the Benchmark Drop #1 teardown.
| Wk | Drop | Channel | Persona |
|---|---|---|---|
| 1 | "I migrated a real monorepo to Tenki in 2 minutes — here's the diff and the bill" | Blog + X | CI owners |
| 2 | Benchmark Drop #1: AI reviewers on real OSS bugs (the teardown) | Blog + HN + X | Eng leads |
| 3 | "Give your agent root without giving it yours" — Sandbox + Claude Code | YouTube + Blog | Agent builders |
| 4 | Tenki vs GitHub Actions vs Depot vs Blacksmith (honest comparison + calculator) | Blog (SEO) | Evaluators |
| 5 | Cohort #1 applications open | Landing + email (dabl.club) | AI-native teams |
| 6 | "The precision problem in AI code review" (POV essay) | Blog + X | Eng leads |
| 7 | Codex + Tenki Sandbox reference architecture | GitHub + Blog | Agent builders |
| 8 | Community story #1 ("How I ship with Tenki") | Blog + LinkedIn | All |
| 9 | Weekly stream milestone: live-fix an OSS bug w/ Tenki | YouTube/X live | All |
| 10 | Customer story #1 (cohort reveal) | Blog + LinkedIn | Enterprise |
| 11 | "Runners, review, sandbox: why they're one product" (the convergence thesis) | Blog + HN | Eng leads |
| 12 | Agent Camp × Tenki hackathon announce | Landing + email + X | Agent builders |
Every artifact serves one of four pillars — and all four ladder up to a single through-line: the agent era runs on compute you can trust, and Tenki is where it runs.
Reproducible, open-harness benchmarks across AI review, runners, and sandbox — published even where Tenki loses (precision today, the long-running-agent frontier next). The honesty is the credibility, and it's how you win developers: be useful, build in public, let the receipts do the selling. Tenki defines the metric.
Cadence: quarterly + per-model-release. See Benchmarks.
Own the category no one's claiming: the sandbox for long-running, self-improving agents (incumbents optimize short-lived sandboxes). Canonical reference architectures — Claude Code, Codex, Cursor, Devin, Cline on Tenki Sandbox — plus "give your agent root without giving it yours." Repo + 5-min video + guide + cost calculator each.
Cadence: ~1/month in year 1.
Migration Wizard storytelling, honest comparison guides vs GitHub Actions / Depot / Blacksmith / Namespace, and the public cost calculator. Lean into the GitHub-pricing moment.
Cadence: evergreen SEO + reactive to pricing news.
The weekly stream running Tenki against a live OSS bug, plus community "How I ship with Tenki" posts and OSS PRs with diff + prompt history attached — the exact motion the JD describes.
Cadence: weekly stream + 1 community post/week.
A sustainable, predictable rhythm — heavy enough to build a brand from zero, light enough for a lean DevRel team to actually ship every week.
| Stream | Cadence | Owner |
|---|---|---|
| Tenki-team deep post | 1 every 2 weeks | DevRel + eng |
| "How I ship with Tenki" community post | 1 per week | Contributor-led, lightly edited |
| Newsletter (biweekly) | Every other Tuesday | DevRel |
| YouTube (migration + Sandbox walkthroughs) | Weekly · Thursdays | DevRel |
| Build-in-public stream (live OSS bug) | Weekly · Fridays | DevRel |
| Coordinated HN / Reddit / X launches | Per major drop | DevRel |
Seeded distribution. Every drop gets cross-pollinated to dabl.club's 86k developers (attributed via UTMs) — the instant top-of-funnel most startups spend a year building. Newsletter target: 8,000 subscribers by month 12.
Video is where migrations and agent setups become believable. Podcast guesting is how a founder-DevRel borrows existing audiences while Tenki's own brand compounds.
When a team is deciding whether to switch CI or adopt an agent sandbox, they Google a comparison. We make sure Tenki's honest comparison is the result they find — and we own the agent-era category terms before the pure-plays do.
tenki vs github actionstenki vs depottenki vs blacksmithgithub actions alternativecheaper github actions runnersai code reviewai code review benchmarkagent sandboxmicrovm sandbox for ai agentse2b alternativetenki vs *How this rolls up. The content engine attacks W3 (no content engine / empty blog) and feeds every other initiative: benchmarks build the trust that converts trials, reference architectures are the agent-era portfolio, and comparison SEO captures O1 (the GitHub-pricing backlash). Tracked weekly on the metrics dashboard.