Git-native marketing infrastructure

Turn the release into a reviewable proof room.

Origin reads repository evidence, drafts source-linked marketing artifacts, and leaves the final decision with your team in Git.

Open quickstart Inspect generated examples

Install the CLIpipx install devrel-origin

Origin runs from your repository. Generation requests go to the provider you configure. Outputs remain local files until you commit them. Read the current security posture.

Origin proof room

Example trace

Source01

root/README.md

+ Session replay captures product interactions+ Privacy controls remain configurable

Grounded claim02

Session replay can be configured with privacy masking.

Linked to a supplied knowledge-base source. Unsupported file and API references are removed during grounding validation.

Human review03

Reviewer noteConfirm the implementation path against the target application before merging.

Reviewable outputReady

posthog-session-replay-nextjs.md

Draft and trace JSON stay together in the repository.

Workflow / One evidence chain

Code changes. Sources. Draft. Human decision.

Every stage remains legible, so marketing can move quickly without disguising uncertainty as proof.

Input

Read the repository

Origin assembles the task, selected knowledge-base sources, code paths, and product context.

Generation

Draft with receipts

The deliverable and its trace record are written together under .devrel/deliverables/.

Validation

Validate the claims

Grounding and code checks flag or rewrite references that are not supported by supplied evidence.

Human gate

Review in Git

Your team edits the marketing diff, requests changes, and decides whether it is ready to merge.

Repository evidenceTraceable draftReviewable change

Evidence dossier / Public example set

Inspect the draft and its receipts in one room.

These four artifacts are stored in this site's repository with their trace files. They are examples to review, not performance claims.

TutorialGenerated example

Setting up session replay for a Next.js app with PostHog

A practical implementation guide produced from the public PostHog repository and handbook.

Draft and trace are committed together under content/examples/.

Read the full generated draft

Trust posture / Verifiable today

Claims that survive their own review.

No popularity counters and no implied certifications. The site states what the open-source product does now and separates that from the managed product roadmap.

Public source

Inspect the repository and contribution history on GitHub.

MIT licensed

The open-source workflow remains inspectable and self-managed.

Provider choice

Configure Anthropic or OpenRouter during initialization.

Review required

Generated files stay in the repository until your team approves them.

Managed Origin CloudSOC 2 Type II is on the roadmap, not a current certification.

Review security details

Access / Start in the repository

Use the open-source CLI. Join Cloud when the shared layer fits.

Origin CLI

Open source

Install the current workflow, configure your provider, and keep the deliverables in your repository.

Repository and knowledge-base grounding
Draft and trace files stored together
Git-based editorial review

Install the CLIpipx install devrel-origin

Follow the five-step quickstart

Origin Cloud / Private beta

Managed path

Shared orchestration for teams

Join the product waitlist for managed workflows, organizational context, and team visibility as those capabilities become available.

This is a product waitlist. It does not imply current compliance certification or general availability.