Skip to main content

Onboarding and configuration

When you first sign in, Reactor walks you through a short setup flow, then drops you into the app. Everything you enter can be changed later.

Workspace setup​

Step 1: Company​

Name your company. That's the only typing: the workspace and engine take their names from it, and Reactor finds your website from your work email domain.

Step 2: The engine reveal​

Reactor seeds your engine from your site while you watch: a drafted voice, audiences, competitors, and positioning, ready before you write a word. Fix what it got wrong; everything is editable in the Engine section afterwards. Signed up with a personal email? The engine starts generic and the AI drafting controls can fill it from any URL later.

You pick a plan before setup (Solo is free forever with no card; Team and Scale start a 14-day trial; see Billing), and onboarding drops you on projects, where work starts.

After onboarding​

Four things make the first week dramatically better; do them in roughly this order:

  1. Plan your first project: pick one of the proposed directions (they're read from your freshly seeded engine) and a two-week project assembles on a canvas. See Projects.
  2. Refine your engine in the Engine section of the sidebar: voice, brand, positioning, writing rules, audiences, and the competitive landscape. Edit the seeded sections or click the AI draft control to redraft any of them. There is no cap on how many audiences or landscape entries you add. See the engine.
  3. Connect your channels at Integrations: social accounts, blog targets, email providers, and analytics sources all connect from the same hub. Connecting requires the manager role.
  4. Generate an API key under Settings → API if you want to drive Reactor from an MCP client. See Build with AI.

Channels​

Pick and configure the channels you generate for in the Engine section (per-platform tone lives there too). The generable channels:

  • X (Twitter)
  • LinkedIn
  • Blog (published via Webflow or GitHub)
  • Newsletter (drafted into your email provider)
  • Discord
  • YouTube
  • Instagram
  • Reddit
  • TikTok
  • Press release (generable, exported rather than published)

Facebook, Pinterest, Threads, and Bluesky are reachable through an aggregator connection (Hootsuite or Vista Social). See Integrations.

Reference documents​

Upload documents you want the AI to draw on when generating: product specs, past posts, brand guidelines, messaging frameworks. These live in Engine → Context and can also be uploaded over MCP.

Self-hosting​

Reactor is operated as a hosted service; environment and deployment configuration is internal to the operator and not something workspace users set up. Everything in these docs happens in the app or over MCP.