Try Pro free for 14 days (card required)HeyBrain is now generally available.Start Free

INDUSTRIES · WEB3 AND CRYPTO

Web3 AI for your project's knowledge, team and agents

Connect Web3 AI tools to project docs, governance posts and community knowledge. Keep private contributor material within its intended audience.

  • Governance decisions.
  • Ask from Claude, Cursor or Codex.
  • Keep private knowledge private.

Built for Core teams, DAOs, Community managers, Agents

What did governance decide on the treasury proposal?

The governance record approved the proposal with a revised reporting schedule. The decision links the original discussion and vote. 1

Governance decisionsExample

Keep the knowledge when contributors move on.

Your core teams and DAOs share answers with sources.

  • Core teamsExample

    Governance decisions

    • What did governance decide on the treasury proposal?

      On request

    • Which discussion and vote support the revised reporting schedule?

      Before deciding

    Source answer: The governance record approved the proposal with a revised reporting schedule. The decision links the original discussion and vote.

    Recorded approval and reporting schedule
    The governance record approved the proposal with a revised reporting schedule.
    Original discussion and vote
    The decision links the original discussion and vote.

    Sources: Governance decisions (Google Drive); Fern Collective · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • DAOsExample

    Tokenomics

    • What's our Vesting schedule?

      Weekly

    • Which approved change affects the vesting schedule?

      Before deciding

    Source answer: The tokenomics document contains the vesting schedule and dates. The governance note records the latest approved change.

    Sources: Tokenomics (Notion); Fern Collective · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive
  • Community managersExample

    Core-team docs withheld

    • Can contributors access our private core-team plans?

      On request

    • Which public documentation can contributors read without core-team planning?

      Before deciding

    Source answer: Public documentation is available to contributors. Private core-team planning remains restricted.

    Sources: Core-team docs withheld (Google Drive); Fern Collective · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • AgentsExample

    A community agent on public docs only

    • Can our community agent answer from public docs only?

      Weekly

    • Which sources are outside the community agent’s permitted collection?

      Before deciding

    Source answer: The community agent's policy limits it to the public documentation collection. It cannot retrieve the core-team folder.

    Sources: A community agent on public docs only (Notion); Fern Collective · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive
  • Core teamsExample

    Contributor onboarding

    • Where can new contributors find our roadmap and working agreements?

      On request

    • Who owns the roadmap, governance process and working agreements?

      Before deciding

    Source answer: The contributor guide links the roadmap, governance process and working agreements. Each section names its owner.

    • Open the current source before the next step

    Sources: Contributor onboarding (Google Drive); Fern Collective · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • DAOsExample

    The activity record

    • Which sources did this agent access?

      Weekly

    • Whose access does each agent key use?

      Before deciding

    Source answer: The activity record shows who asked and when. Review it against the access of the member who issued each key.

    Who asked and when
    The activity record shows who asked and when.
    Review against each key’s member access
    Review it against the access of the member who issued each key.

    Sources: The activity record (Notion); Fern Collective · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive

Less searching. More shared context.

Without HeyBrain

With HeyBrain

Read the governance record, original discussion and vote separately to reconstruct the treasury proposal decision.

Find the approved proposal and revised reporting schedule, with links to the original discussion and vote.

Search the tokenomics document and governance note to check vesting dates against the latest approved change.

Find the vesting schedule and dates in the tokenomics document, alongside the latest approved change in the governance note.

Check contributor access to public documentation separately from private core-team planning.

Use the public documentation available to contributors while private core-team planning remains restricted.

Check the community agent’s policy before asking it for documents outside the public collection.

Find the policy limiting the agent to public documentation, with the core-team folder unavailable to the community agent.

ONE CONNECTED BRAIN

One question, across your tools

Bring Google Drive, Notion and your uploads into one cited answer.

Question
What did governance decide on the treasury proposal?
Answer
The governance record approved the proposal with a revised reporting schedule. The decision links the original discussion and vote. (Source 1)
  • Source 1: Governance decisions (Google Drive)
  • Additional source: Tokenomics (Notion)
  • Additional source: Core-team docs withheld (Google Drive)

Illustrative example, fictional data

FOLLOW THE SOURCE

Review the evidence behind an answer

Open the citation. Read the original wording and surrounding detail.

Answer
The tokenomics document contains the vesting schedule and dates. The governance note records the latest approved change. (Source 1)
Cited excerpt from Tokenomics (Notion)
The tokenomics document contains the vesting schedule and dates. The governance note records the latest approved change.
  • Source 1: Tokenomics (Notion)
  • Source 2: Governance decisions (Google Drive)

Illustrative example, fictional data

PERMISSIONS IN EVERY ANSWER

Share the context. Keep the boundaries.

Same question, different permissions. Review the request in the activity record.

Question
What can we share about the protocol roadmap?
Answer for Rafael Okafor (Treasury lead)
Published roadmap and governance process available. Treasury review: quarterly allocation.
Answer for Jonas Chen (Community moderator)
Published roadmap and governance process available. The restricted source is not in your access.
Not in Jonas Chen’s access
TREASURY PLANNING · TREASURY TEAM
Access record
14:02 · Jonas Chen · Asked the brain · RECORDED

Illustrative example, fictional data

Company knowledge, under your control

Source sharing, where we can prove it

Google Drive, GitHub and Slack (beta) sharing carries into HeyBrain. Notion uses the connecting account’s access.

Every AI tool gets its own key

It acts with your access. Revoke it any time.

An activity record

Review questions asked, uploads, syncs and blocked or masked data.

Review provider data terms

Check provider data use and retention.

Bring your own model key

Connect your model to governed knowledge.

SEND PASSAGES, NOT WHOLE FILES

Send less context per task

HeyBrain sends relevant passages instead of whole documents.

Repeated contextWhole documents
With HeyBrainRelevant passages

FAQ

Questions Web3 and crypto ask

  • What did governance decide on the treasury proposal?

    The governance record approved the proposal with a revised reporting schedule. The decision links the original discussion and vote. Ask follow-ups in the same conversation and open each citation to check the surrounding detail, then share the source with colleagues who can access the same collection.

  • What's our Vesting schedule?

    The tokenomics document contains the vesting schedule and dates. The governance note records the latest approved change. Connect the relevant Drive folder or Notion pages, or upload documents, then follow citations to their original passages from the AI tools your colleagues already use.

  • Which sources and AI tools can we use?

    Connect Google Drive, Notion and document uploads; Claude, Cursor and Codex ask your company knowledge through HeyBrain MCP. Keep decisions and references available where your team works. HeyBrain supplies knowledge; agents use their own tools for actions requested by the user.

  • How does HeyBrain keep private knowledge private?

    People and agents receive answers from sources they can open. Workspace rules restrict the audience; each AI tool has its own revocable key that acts with its member’s access. Administrators review who asked and when in the activity record, alongside workspace membership and access rules.

  • How do we get the team started?

    Connect your team’s current brief, decision notes and working guide, invite the people who need them and ask a familiar question. Open its source citations before expanding the collection. Align workspace membership and each governed agent’s policy with each team’s responsibilities.

  • How does HeyBrain reduce AI token cost?

    HeyBrain sends relevant passages instead of whole documents to your AI tool. Compare costs with the context calculator on the Reduce AI token costs page. Your team shares the same connected knowledge across tools, so every new conversation can start with the relevant passages and their sources.

/ Get started today

Put your company knowledge
to work with HeyBrain