Skip to main content
Origin
14 May 2026Edition 2026.05

Marketing artifacts ship from the repo, reviewed like code.

Origin is the open-source framework that puts marketing inside your engineering workflow. Every release opens a PR with the release note, changelog, blog draft, and social posts: drafted from your code, reviewed by your team.

Read the manifesto →

Validated on PostHog's 30K+ ★ repo · 1018 tests on every release.

See how it works ↓

Marketing lives outside the repo

Engineering ships in GitHub. Marketing lives in Notion, HubSpot, Asana, Substack, Webflow. The hand-off is a Slack thread and a hope.

Release notes are wrong by Friday

A feature ships Tuesday. By Friday the release note has the API parameter wrong because nobody told marketing the signature changed.

The technical marketer doesn't scale

The one marketer who reads PRs becomes a hero. They don't scale. They burn out. They quit. You hire a less technical replacement and the gap widens.

The person writing the blog post shouldn't have to hunt down the PR that introduced the feature.
The Shift
01

The technical marketing stack is fundamentally broken.

Most devtool companies treat marketing as a post-facto scramble: something that happens after the work is merged. This creates a disconnect between development cycles and announcement timelines.

Origin shifts context to the point of creation.

By moving the drafting phase into your existing CI/CD pipeline, Origin ensures that every line of code is accompanied by its human narrative. You no longer need to chase engineers for context on Friday afternoons.

PR opens. Origin runs on the release tag. Fans out to release note, changelog, blog draft, social posts.

Origin runs on every release. It reads the PRs in the release, the diff, the docs, and your past marketing artifacts. It opens one PR with a draft of every artifact you'd usually scramble to write on Friday. Your team reviews it. Merge ships marketing the same way merging code ships features.

Marketing artifacts ship from the repo, reviewed like code.
Open Source
02
✓ installed devrel-origin 0.2.14 $ devrel init + .devrel/config.toml + .devrel/voice.md + .devrel/style.md + .devrel/slop-blocklist.md + .devrel/kb/ + .devrel/deliverables/ Done. Next steps: 1. Run devrel auth to configure your LLM API key. 2. Edit voice.md / style.md / slop-blocklist.md. 3. Run devrel doctor to verify. $ devrel auth Pick an LLM provider: 1) anthropic (console.anthropic.com) 2) openrouter (openrouter.ai, free credits) ✓ key validated, written to .devrel/.env (mode 0600) Install: pypi.org/project/devrel-origin

What you get, free, MIT-licensed:

  • A .devrel/ directory convention. config.toml + voice.md + style.md + slop-blocklist.md. Versioned in your repo.
  • 24 verbs: init, auth, doctor, migrate, config, run, schedule, cost, triage, listen, synthesize, experiment, intel, content, docs, video, kb, marketing, sales, growth, cro, analytics, argus, deliverables.
  • 15 specialists across 4 pillars: Health, DevRel, Content, and Sales. One weekly pipeline. KB-grounded, code-validated.
  • 7-stage editorial pipeline: developmental edit → line edit → copy edit → anti-slop → reader-persona test → readability check → brand audit.
  • Bring your own ANTHROPIC_API_KEY or OPENROUTER_API_KEY. OpenRouter onboarding ships with free monthly credits, so the practical floor is $0/month for low-volume use. Route different agents through different models via [llm].agent_models in .devrel/config.toml.
  • Cron via devrel schedule install. Or run on demand: devrel run for the full cycle, devrel content draft "tutorial on X" for one piece.
  • Operates on your project repo the way git, npm, and cargo do.
Quickstart →Read the docs →
Cloud
03

From your repo, at team scale.

The OSS gives you the workflow. Cloud gives you the brain.

Repo-grounded generation

Drafts read your AST, your API surface, your past release notes, your existing voice. Not generic LLM slop.

How it works →

Drift detection

"Your tutorial uses client.send(): deprecated 3 versions ago. PR #2891 changed it to client.dispatch(). Apply the fix?"

See an example →

Multi-channel publishing

One marketing PR fans out to Substack, LinkedIn, X, Discord, your blog. Each channel adapted to its native form, not cross-posted.

Channel list →

Analytics by commit

Which release drove the most signups? Which tutorial converts? Attribution rolls up to the commit and the PR, not a UTM string.

Sample dashboard →
System Validation
marketing/changeloglast 3
  1. v0.2.132026-05-13

    Wizard UX fixes from real user testing + audit hygiene

    Real-user testing on v0.2.12 surfaced three onboarding bugs and one release-blocker. v0.2.13 fixes all four plus the recommendations from a full pre-rename audit.

    1 PR →
  2. v0.2.122026-05-11

    Onboarding overhaul (interactive init wizard)

    `devrel init` is now an interactive wizard that walks you from a fresh shell to your first content draft in one session: scaffold `.devrel/`, configure an LLM key (provider picker,

    0 PRs →
  3. v0.2.112026-05-11

    Fix OpenRouter 400 on default model ids

    `devrel run` and `devrel auth` no longer 400 on OpenRouter. The hardcoded default model ids in `core/llm_backends.py` used Anthropic's dated suffix (`anthropic/claude-sonnet-4-5-20

    0 PRs →
View full changelog →

The changelog you're reading was generated by Origin from this repo's PRs. Each entry links to the source commit.

Reviewed and merged by us, the same way you would. When a new release ships, the entry appears here automatically: same single-source-of-truth Origin promises for any other devtool.

vs the alternative04

  • Lives in your repo

    Origin
    ✓
    DevRel agency retainer
    –
    In-house marketing stack
    –

  • Triggered by releases

    Origin
    ✓
    DevRel agency retainer
    –
    In-house marketing stack
    –

  • Grounded in your code

    Origin
    ✓
    DevRel agency retainer
    partial
    In-house marketing stack
    –

  • Reviewed in PRs

    Origin
    ✓
    DevRel agency retainer
    –
    In-house marketing stack
    –

  • Versioned & diffable

    Origin
    ✓
    DevRel agency retainer
    –
    In-house marketing stack
    partial

  • Self-serve from $0

    Origin
    ✓
    DevRel agency retainer
    –
    In-house marketing stack
    –

  • Drift detection

    Origin
    ✓
    DevRel agency retainer
    –
    In-house marketing stack
    –

  • Time to first artifact

    Origin
    < 1 hour
    DevRel agency retainer
    4–8 weeks
    In-house marketing stack
    weeks per artifact

  • Monthly cost (10-person team)

    Origin
    $0–$499
    DevRel agency retainer
    $8K–$25K
    In-house marketing stack
    $400–$2K in tools, plus headcount
Pricing
05

Free for OSS. Cloud is coming soon.

Open Source
$0

The framework, CLI, GitHub Action, templates, Discord community. Self-host. Use forever. No account required.

Get started →
RecommendedCloud
Coming soon

Hosted generation, multi-channel publishing, drift detection, analytics, team review. Pricing locked when the waitlist closes.

Join the waitlist for first access.

Join waitlist →See OSS pricing →
Enterprise
Talk to us

Series A+ devtool companies. Private workspace, SSO, DPA, custom agents, dedicated engineer, quarterly roadmap calls.

Contact sales →
Security

Your code and docs,
handled like code and docs.

Isolated workspaces

Your repo clones and knowledge base live in a per-customer workspace. No cross-tenant data access. No shared prompts.

You own every output

Tutorials, triage reports, outreach copy — everything the platform ships is yours, licensed to you, not training data.

Delete on cancel

Cancel the subscription and every workspace, repo clone, and embedding is destroyed within 30 days. No recovery, no archives.

SOC 2 on roadmap

Working toward SOC 2 Type II. DPA and Standard Contractual Clauses available today on request.

The fix is to put marketing in the workflow that already works for engineering: pull requests, code review, releases.
Common Questions06

Common questions.

Why this exists

Daria Dovzhikova

Founder of Origin

LinkedInX / Twitter

Daria Dovzhikova, founder.

12+ years leading product marketing and growth for devtool companies: JetBrains, Huawei, and a dozen developer-first startups.

I built Originbecause I kept hiring marketers who couldn't scale, and I kept being the marketer who couldn't scale. The pattern was always the same: the technical ones became heroes and burned out. The non-technical ones shipped marketing that was confidently wrong.

The fix isn't to hire more technical marketers. The fix is to put marketing in the workflow that already works for engineering: pull requests, code review, releases. Origin is what that looks like.

Ship marketing from the repo

One hour to your first auto-generated release note.

Quickstart →Read the manifesto →