Brainstead

A project per client separates clients by habit. A brain per client separates them in the infrastructure.

Many agencies keep one ChatGPT project per client. It works well for drafting, but every project sits in one shared workspace, and keeping clients apart depends on people picking the right project every time.

Brainstead gives each client its own brain: its own storage bucket and encryption key in AWS Frankfurt (eu-central-1), its own Slack app and its own agent. One brain's credentials have no permission on another's, and the agent can't post anywhere. It runs on Claude by default, or another frontier model your client chooses.

Request a demo Read the security page

Design-partner stage · priced per client brain, not announced

ChatGPT · one workspace
harbour project
corvid project
larkspur project
Kept apart by picking the right project.
Brainstead · three brains
harbourown bucket · own key
corvidown bucket · own key
larkspurown bucket · own key
Kept apart in the infrastructure.

Side by side

ChatGPT projects and Brainstead, side by side

QuestionChatGPT, one project per clientBrainstead
Where client material livesOne shared workspace, kept apart by projects and namingIts own storage bucket and encryption key per client, in AWS Frankfurt
Who can post on the client's channelsWhatever you've connected it toNot the agent: it holds no channel credential and writes drafts only
Access to your toolsWhatever was granted when it was connectedRead-only by default; write is a per-tool switch, and every call is logged
The client's voicePasted into each project's instructions and filesKept in the brain: the client's site, brand files and skills
Unsupported claimsUp to the reviewer to spotMarked [NEEDS-FACT] in the draft, with notes for the reviewer

Row by row

What sits behind each row

Storage and keys

In a ChatGPT workspace, client projects share one account boundary. In Brainstead, naming the client creates a dedicated bucket and encryption key, and credentials for one brain have no permission on another brain's bucket or key. A brain you don't own returns "not found", so its existence isn't even confirmed.

Who can post

A chat tool can act on whatever it's connected to. Brainstead's agent holds no credential for Slack, LinkedIn or a client's site. It writes a draft with a SHA-256 fingerprint, and a person sends it.

Tool access

Brainstead connects ClickUp, Notion and other tools read-only by default, enforced at our proxy rather than by instructions to the model. The owner switches write access on per tool, and every change is logged.

Brand voice

Project instructions drift as people edit them. Brainstead keeps the voice in the brain as plain markdown: up to 25 pages of the client's site, brand files and skills, with sources named in the reviewer notes.

Unsupported claims

A chat model fills gaps fluently. Brainstead's drafts mark a claim it can't source as [NEEDS-FACT], so the reviewer sees the gap instead of a guess.

Fair to say

What ChatGPT projects do well

ChatGPT is quick to start, flexible, and many people on your team already know it. For brainstorming, research and one-off writing, a project per client is a reasonable setup. Brainstead is for the work where a client's material, voice and channels need to stay provably separate.

How to

How to move a client from a ChatGPT project to a brain

  1. 01

    Name the client

    Create a brain with the client's name. Its own storage bucket and encryption key are created in AWS Frankfurt (eu-central-1).

  2. 02

    Paste the client's website

    The brain reads up to 25 pages into knowledge/website/, so it starts from the client's own words.

  3. 03

    Bring over the project's instructions

    Copy the ChatGPT project's custom instructions and the approved copy you uploaded there into brand/ as markdown files.

  4. 04

    Install the brain's Slack app

    Invite it to the client's channel, for example #harbour-marketing.

  5. 05

    Compare the first drafts

    Ask both for the same piece, for example @brain-harbour /draft a LinkedIn post about our Q3 launch, and read the reviewer notes and [NEEDS-FACT] markers side by side.

When to switch

Signs a project per client has stopped being enough

A client's security questionnaire asks how their material is kept apart from other clients'. Two account managers write in two different versions of the same client's voice. Someone pasted the wrong brief into the wrong project. Each of these is a sign the separation depends on habit rather than on the system.

Questions

Frequently asked questions

Can we keep using ChatGPT alongside Brainstead?

Yes. Many teams keep ChatGPT for open-ended work and use a client's brain for drafts that go to that client.

Can we prove Client A's material never fed Client B's work?

Each brain has its own bucket and key, and one brain's credentials can't open another's. The audit log records every tool call, refusal and access change.

What does a security questionnaire need from us?

Send the client our security page. It lists what's enforced today and what's in development, in plain words.

Can we export a brain?

A brain is plain markdown: knowledge, brand voice and skills. Export, so you can take it with you, is in development.

How much does it cost?

Brainstead is priced per client brain, not per seat. Pricing isn't announced yet.

What isn't it?

It isn't a general chat assistant, and it isn't certified yet: SOC 2 and a DPA are in progress.

Related

Also works with

Each client brain also works with Slack, Brand voice, ClickUp and Client isolation. See what runs today and what's in development, the security page for questionnaires, or start from the Brainstead home page.

See a client brain built in front of you.

Request a demo