Reactor

The multiplayer AI marketing engine. A marketing engine holds what your company knows about its voice, audiences, positioning, and rules, and everything you publish generates from it. Multiplayer means your whole team and all their AI tools work from the same one, live, in the same piece at the same moment. Single-player AI makes one person faster. This makes the team better: one teammate's correction improves everyone's next draft, permanently.

Most AI content tools are single-player: an AI writing tool per seat, each one starting from nothing. Reactor is collaborative AI for marketing — an AI marketing platform where using AI in marketing is a team activity, not a private tab. Every blog post, social post, image, and project is generated from the same engine, so AI generated marketing actually sounds like your company.

Start here

• Quickstart: go from sign-up to your first published post in a few minutes.
• Configure your engine: the voice, audiences, landscape, and rules every generation draws from.
• Build with AI: hand setup to an AI agent and drive Reactor headlessly over MCP.

The six things to know

1. The project canvas: one prompt becomes a two-week project of briefed, dated pieces on a live board. The whole team arranges it, derives the thread from the blog post, comments where it matters, and schedules with a drag. Projects are where work starts.
2. The collaborative editor and sharing: everyone writes in the same piece at the same moment. Voice Tab completions in your voice (lint-checked before they appear), ⌘K rewrites on any selection, assistant edits that arrive as reviewable diffs, comments that anchor and heal, and shares that put founders and freelancers in the piece without joining your workspace.
3. The Anti-Slop Guard: deterministic lint flags the tells of AI writing in the editor with one-click repair, a similarity check catches near-duplicates of your own library, and corrections become standing rules ("remember: never call it a platform") that bind everyone's next draft. Advisory when you publish by hand; blocking when nothing is watching. Your engine always outranks it.
4. Integrations and scheduling: connect your blog, email, web, and social channels once, and Reactor publishes there directly. One calendar, scheduled posts that ship themselves, and everything you publish lives on your own properties.
5. The analytics feedback loop: metrics flow back per channel, per piece, and per project, become the Guard's nightly signals, and steer what generates next. The loop closes without a spreadsheet.
6. The assistant: one chat on every page that sees what you see. Everything it proposes (revisions, engine changes, calendar slots, standing rules) arrives as a card you review before it applies.

Also in the box: the media studio (87 named styles, your derived brand style, Figma templates, video), MCP with every capability as a tool for Claude, Cursor, or any client, and webhooks for the rest of your stack.

Three ways to learn

Pillar	What's inside
Getting Started	Sign up, onboard, configure the engine.
Learn	Feature guides: projects, the editor, the Guard, publishing, analytics.
Build with AI	MCP, webhooks, authentication, and handing setup to an agent.

:::tip For LLMs Every page has a Copy page button (top right) to grab it as Markdown. The whole site is also available as llms.txt and llms-full.txt. :::