Meet Orbit  ·  AI content operations

Publish content your senior editor would sign off on.

Orbit is a multi-agent content engine that turns your living brand knowledge base into publishable, on-brand, proof-backed articles — drafts your senior editor would sign off on, with real case studies cited by name and voice rules the model actually follows.

Built on
Claude MCP Turso Next.js
100 %
On-brand from structured voice rules
Real
Case studies cited by name, not invented
30 min
Topic → publishable draft
6
Agents working in parallel on every piece

The problem

Every team has AI writers. Almost none ship.

The bottleneck moved. Anyone can generate text. Brand accuracy, real proof, and editorial review are where content still dies.

Without Orbit

The current state

  • Generic LLM output no senior editor would sign off on
  • Proof points invented, vague, or missing entirely
  • Voice drifts — because voice lives in a PDF, not the model
  • AI tells the reader can spot in the first two sentences
  • Rewrite the whole draft to fix one paragraph
  • Every client needs its own stack of logins and tools
With Orbit

Content ops, reimagined

  • Drafts that survive senior editorial review
  • Real case studies cited by name, with hard numbers
  • Voice rules live in Cortex — the model obeys them
  • Humanisation pass strips AI tells and fixes rhythm
  • Patch a passage — Orbit re-runs just that passage
  • Run every brand from one workspace, branded per-brand

How it works

Six stages, one pipeline.

Every article flows through the same six stages. Each one is tracked, audited, and re-runnable in isolation.

01

Understand

Pull voice, personas, case studies, and frameworks from Cortex — your brand brain.

02

Decide

Score topics against Search Console, Ahrefs, and site inventory. Write the highest-leverage piece next.

03

Research

Three specialist agents run in parallel: SERP intent, trend signals, proof mining.

04

Generate

Claude Opus drafts a full article with real case studies and quantified proof woven in.

05

Humanise

Second pass strips AI tells, fixes rhythm, and enforces your brand voice rules.

06

Ship

Inline review, highlight-to-edit, client preview link, then direct commit to your blog.

The platform

Five systems. One content engine.

Each layer does one thing well. Together they replace the tool sprawl a content team has collected over five years.

A living brand brain. Also a standalone product.

Personas, voice rules, frameworks, case studies, portfolio, and reviews — served to every agent via MCP. Cortex is how Orbit stays on-brand, and it's a product in its own right that powers any AI agent in your stack, not just content.

  • Structured voice rules the model actually follows
  • Quantified proof library that gets cited by name
  • Per-brand knowledge graph — no leakage across clients
  • Works with Claude Code, Claude Desktop, and custom agents

An opportunity engine that tells you what to write.

Scores every page and every keyword cluster against performance data, intent, and strategic fit. Surfaces new posts, refreshes, merges, and prunes — so the editorial calendar writes itself.

  • New-post opportunities ranked by lift potential
  • Decay detection on pages losing impressions
  • Merge and prune suggestions to kill cannibalisation

Highlight a passage. Fix it. Ship it.

The reviewer selects any sentence and either rewrites it or files a targeted report. Orbit re-runs that passage only — with full brand context — so a bad paragraph never means redoing the whole article.

  • Highlight-to-edit and highlight-to-report
  • Patch-level re-runs, not full regenerations
  • Full audit trail of every change made

One workspace, your entire client roster.

Agencies run every client from a single console with isolated brand brains, per-brand theming, and branded non-copyable preview links. No more juggling logins across ten different tools.

  • Isolated Cortex per brand — zero data leakage
  • Per-brand theming applied to client previews
  • Roles, seats, and audit logs across the workspace

From draft to production with one click.

Direct commit to Jekyll or WordPress. Shareable, branded preview links for clients. PDF export on demand. Scheduling, rules engine, and cadence controls live alongside the content itself.

  • Native Jekyll and WordPress integrations
  • Client previews — branded, non-copyable
  • Scheduling and cadence controls built in

Who it's for

Three shapes of content team. One engine.

For agencies

Every client, on-brand. Every time.

Spin up a new client in an afternoon with their own Cortex. Every article ships with their voice, their case studies, their frameworks — not a generic template with the logo swapped.

  • Isolated brand brain per client
  • New client onboarded in hours, not weeks
  • Every piece branded and ready for client sign-off
For in-house teams

Editorial-grade content, at the pace of publishing.

One brand brain, one editor, one pipeline. Keep editorial control via inline review — and keep the voice, proof, and positioning you've spent years building.

  • Editor keeps final cut on every piece
  • Brand voice enforced from day one
  • Real proof from your own case study library
For enterprise

Your brand, your knowledge, your infrastructure.

On-premise Cortex deployment, SSO, custom integrations, and a dedicated workspace. All your brand IP and customer proof stays inside your perimeter.

  • On-premise or VPC deployment
  • SSO, SOC-ready audit logs
  • Custom MCP tools for internal systems

How it compares

Not a writer. An operating system for content.

 
Orbit
Generic AI writers
Human agencies
On-brand voice from structured rules
Partial
Real case studies & quantified proof cited by name
Partial
Humanisation pass that strips AI tells
Topic selection tied to live performance data
Partial
Inline, passage-level human review
Multi-brand with isolated knowledge graphs
Direct commit to blog repo (Jekyll / WordPress)
Editor would ship it without rewriting

Under the hood

Built for editorial quality at scale.

The architecture is the product. Every choice is made so brand accuracy, proof integrity, and editorial control hold up as your content operation grows.

Claude Opus, Sonnet & Haiku

Model tiering by role — generation, research, and lookup each use the right class.

Model Context Protocol

Cortex, Ahrefs, and Search Console are all MCP servers. New data plugs in without rewrites.

Turso + Drizzle ORM

Distributed SQLite. Brand data replicates globally, writes from any worker.

Next.js 16 on Vercel

Control plane is fast, cache-native, and cloud-ready out of the box.

Distributed job queue

Multi-worker processing with automatic primary failover. Scales horizontally.

Quality-first pipeline

Brand context loaded once, agents handed strict output contracts, and humanisation applied before any reviewer sees the draft. Voice and proof hold up as brands scale.

Powered by Cortex

Orbit is only as on-brand as the brain behind it.

Every voice rule, framework, case study, and quote Orbit uses comes from Cortex — our standalone brand-memory server. Cortex is what makes "on-brand" a non-negotiable instead of a hope, and it's available as its own product for any AI agent in your stack.

Explore Cortex MCP-native Typed schema Multi-brand

Early signal

What the first teams are saying.

The first AI content tool where I haven't had to rewrite the lead. Proof shows up by name, voice feels like us, and I can patch a paragraph without regenerating the whole thing.

We onboarded our seventh brand in under an afternoon. Every article ships sounding like the client, not like generic AI — our editors have stopped rewriting leads.

The opportunity engine is the killer feature. It stopped us writing things that were never going to rank.

Questions

Things buyers ask us.

How is Orbit different from tools like Jasper or Copy.ai?

Jasper and Copy.ai sell text generation. Orbit is a full content operation that produces editor-grade work: it decides what to write based on your live performance data, researches with multiple agents, cites real proof from your case study library, enforces voice from a structured brand brain, and ships to your blog. Generation is one step out of six.

Will the output actually sound like our brand?

Yes — because voice rules, frameworks, and proof points come from Cortex, a structured brand brain, not from the model's imagination. If a sentence drifts off-brand, your editor highlights it and Orbit re-runs just that passage with full brand context.

What does onboarding a new brand look like?

For agencies, a new client is typically live in a few hours. We import existing case studies, portfolio, voice guidelines, and performance data, then generate a calibration article that you review. Your feedback sharpens the brand brain.

Do you integrate with our CMS?

Jekyll and WordPress are native. For other CMSs we ship via markdown export or a simple MCP adapter — usually a day or two of work.

What about data isolation across clients or brands?

Every brand has its own Cortex with hard boundaries. No brand ever sees another brand's data, and the agent context for one brand's article never includes another brand's knowledge graph.

Can we host Orbit on our own infrastructure?

Yes. On-premise and VPC deployments are available on enterprise plans, including on-prem Cortex, SSO, and custom MCP tools for internal systems.

How do you stop the output from sounding like AI?

Two things. First, Cortex — voice rules, tone, sentence-length preferences, and banned phrases live as structured data the model is forced to follow, not a PDF it glances at. Second, a dedicated humanisation pass rewrites rhythm, strips AI tells (over-hedging, corporate filler, tidy tricolons), and enforces brand-specific cadence before the draft ever reaches your editor.

Ready?

See Orbit running on your brand.

We'll load your brand brain, wire up Search Console and Ahrefs, and generate a live sample article on a topic of your choice. Usually within a week.

Demo delivered in 5–7 days Your data stays yours No procurement process to start