BrandMan

BrandMan is an agent-first brand brain. It keeps a brand’s mission, voice, compliance rules, audience personas, sources, campaigns, and results in one place, and lets AI agents (through MCP) and people (through a dashboard) work from that same record.

This repository is the AGPL-3.0 open core. It is free software and is not paywalled. You can run, modify, and self-host it with no BrandMan Cloud account. If you run a modified version as a network service, the AGPL requires you to offer that source to the people who use the service. The BrandMan name and logo are not covered by the license.

BrandMan Cloud is a separate paid product. It is this core plus closed components (a hosted service, billing, multi-tenancy, and similar). Cloud has more features. The open core is the smaller, functional system: one SQLite database, a password-gated dashboard, and an MCP server you run yourself. Cloud is not in this repository, and you do not need it to use the core.

Status: early (0.1.x). The core runs and is tested. Expect rough edges and breaking changes.

Quick links: Quickstart · Architecture · Docs · Contributing · Security · BrandMan Cloud · PyPI

What the open core does

• Brand context. Mission, voice, guidelines, personas, and compliance rules, readable by agents and people.
• Content workflow. Sources, campaigns, channel drafts, and newsletter issues.
• Exact-revision approval. An approval covers one exact revision. Editing an approved item clears the approval, bumps the revision, and sends it back to draft. Nothing is posted until its current revision is approved. Human review of each post is optional: you choose who approves (a person in the dashboard, or your own automation through the REST API), and the brand’s approval policy is a setting. The MCP server can draft and submit for approval; it has no tool that approves or publishes.
• Feedback. Record what a channel did, propose a learning, and accept it into the brand context only with an explicit decision.
• Missions. Time-boxed goals with a baseline, a target, and a trajectory.
• MCP. The same flows for Claude, Cursor, and Codex, over stdio (brandman-mcp) or a hosted OAuth endpoint (/mcp).
• Dashboard and REST API. Operator UI at /app, and the API behind it.
• Channels at the edge. X and Beehiiv are replaceable adapters. The brand record does not live inside a channel.

Architecture

Claude / Cursor / Codex ──MCP──┐
browser ──► dashboard (/app) ──┤
scripts ──► REST API (/api) ───┴─► FastAPI app (brandman.main)
                                    ├─ brand context, campaigns, newsletters