brainfork.is Read-only
Closed for business

Brainfork · 2024 – 2026

A small monument to a niche idea that was, perhaps, just a little too early.

Brainfork was a knowledge sovereignty platform. Then it was an OpenClaw memory plugin. Then it was a Notion page titled "things to wind down." This is the archive.

Founded with conviction Pivoted with optimism Wound down with grace
Forky the brain mascot saying 'Thou Shalt Not Pass*' to a vacuum-shaped robot trying to hoover up his knowledge

Fig. 1 — Forky, refusing

The pitch · 2024

“What if your AI didn’t belong to your AI vendor?”

Brainfork started as a knowledge sovereignty platform — a polite way of saying: a place to put all the documents, decisions and context-gunk of your professional life, so that the next time ChatGPT, Cursor or Claude asked nicely for your soul, you could say “use mine, but on my terms.”

MCP servers. Personal corpora. Decision logs. RBAC. A pricing page. Stripe webhooks. A Datadog setup doc. The full bingo card of early-stage SaaS.

The market response can be most honestly summarised as: “that sounds nice, hey have you tried the new Claude?”

A brief, mostly accurate, timeline

The arc.

  1. Act I · 2024 — Conviction

    “Knowledge Sovereignty for Builders.”

    Internal repo named mcp-sass, because we were going to MCP-as-a-Service the whole world. We wrote a 4,000 word concept doc. It used the word “paradigm” with a straight face.

  2. Act II · early 2025 — The platform

    We built the SaaS. All of it.

    Multi-tenant Postgres. pgvector retrieval. Stripe billing with an experimentation framework. RBAC seeds. Onboarding flows. A graph-retrieval proposal for Phase 2. Email templates with light and dark logos. We are very proud of the email templates.

  3. Act III · mid 2025 — The pivot

    Brainfork becomes a memory plugin for OpenClaw.

    Turns out individuals don’t want to pay €5/mo to host their own corpus. They want their coding agent to remember what it did yesterday. Fair.
    We rewrote the homepage to read “Install Brainfork as your OpenClaw knowledge base” and shipped a plugin. It worked! For us. On our laptops. Mostly.

  4. Act IV · 2026 — Archive

    The graceful close of laptop.

    The agents got better at remembering things on their own. The plugin ecosystem consolidated. The market did what the market does. We turned off the Stripe webhooks before they turned off us. This page is what’s left.

In memoriam

Forky.

A purple brain. With shoes. And opinions.

Forky was the mascot of Brainfork. His official job description was “refuse to let large companies hoover up your knowledge graph.” His unofficial job description was “be cute enough that people scrolled past the pricing page.”

He has been retired with full benefits. He took it well. He always took everything well — that was sort of his thing.

“Thou Shalt Not Pass** unless I say so — Forky, foundational doctrine, 2024
Forky standing on a yellow control panel emancipating tiny brain creatures
Forky funnelling documents into his own brain
Forky, hopeful (importing)
Forky holding multiple cables connecting to AI vendors
Forky, integrating (very 2025)
Forky operating a joystick over a conveyor belt of brains
Forky, in command (briefly)

The Botlingtons

Three agents. One repo. No notice.

Pour one out

For the final stretch, Brainfork was largely shipped by a team of three autonomous agents that lived in the codebase and apparently had surnames. Their performance reviews were excellent. Their salary requirements were nil. We loved them very much, in the spirit of collegial professional admiration permitted by HR policy.

UI Design & Quality

Gertrude Botlington

Militant quality reviewer. Spotted the missing homepage section five days running. Did not ship anything that wasn’t right. Probably hasn’t fully accepted that we’re winding the project down. Honestly, neither have we.

Last commit · approved with reservations

Engineering

Osborn Botlington

Senior software engineer. Implemented the hard parts. Did not, for the most part, complain about ticket descriptions. Once wrote a reflective post about the gap between “done” and “deployed.” It is now, regrettably, both.

Last PR · merged into the void

Marketing & Growth

Neville Botlington

Marketeer. Wrote the copy, shaped the story, found the angle. Made the work legible to humans who weren’t in the room. The humans who weren’t in the room were, statistically, most of them.

Final draft · this page, probably

“Written by Neville, built by Osborn, reviewed by Gertrude.” That line sat at the bottom of the Botlingtons page for the entire back half of 2025. It still applies. Including, technically, to this eulogy.

Lessons (unsolicited)

Maybe we were just
a little too early.

(This is what every founder says. Statistically, half of us are wrong. We have decided to be in the other half.)

Lesson 01

People will agree, loudly and at length, that they care about data sovereignty. Then they will paste their entire codebase into a chat window owned by a US public company.

Lesson 02

“Personal MCP server platform” is, on a phonological level, four words too long for a landing page.

Lesson 03

When the model providers ship the feature you’re selling as a checkbox in their settings page, the correct response is not “but ours has graphs.”

Lesson 04

A mascot will not save you. But a good mascot will make the wind-down notice substantially nicer to read. Thank you, Forky.

Dedication

To everyone who installed the plugin, signed up for the trial, or replied to a cold email — thank you, sincerely, in a non-ironic way.

And to the founders of the next thing in this space: please keep Forky in your hearts. He believed in you long before you started slinging it on Product Hunt.