The workspace's always-on context, like a CLAUDE.md for the whole company. Billy, Claude, ChatGPT and any other tool you connect read it first, so every assistant starts from your rules.
The Backbone WikiCompany knowledge, in twelve volumesComing soon
Knowledge is power.
Access it from anywhere.
Backbone Wiki dramatically increases your productivity by hosting the most precious knowledge about your company and workflows. No matter which AI tools you're using.
Point at a volume to take it off the shelf. Click to open it.Swipe along the shelf. Tap a volume to pull it out, tap again to open it.
Read the entryBackbone Wiki
From Backbone, the back office for freelancers and studios
The Backbone Wiki is where you write down how your company works: rates, payment terms, onboarding, processes, how AI tools should work, tone of voice, and much more. All the knowledge can be accessed by the AI tools you're already working with, even if you decide to switch tools.
Billy, the assistant built into Backbone, and the AI tools you connect, such as Claude and ChatGPT,[2] read the wiki before they work, and can write to it. What an AI writes waits for your review.
And because the wiki lives in Backbone, next to your clients, hours, invoices and books, the knowledge sits beside the data it is about. A client's rate and the invoice that uses it are one click apart. So whichever AI you ask, today or after a switch, the answer comes from the same page, kept up to date in one place. The wiki is coming soon.
§ 1Any AI, the same knowledge
It doesn't matter which AI model or chat you work in. The knowledge lives in Backbone, not in one assistant's memory or settings, so it is there wherever you ask: in Billy, in Claude, in ChatGPT, or in the next tool you try.
Works in every client
The wiki is reached through MCP tools, the part every AI client supports, ChatGPT included. Pages, context and skills all come through them.
Switch tools, keep everything
Move from one chat to another, or try a new model. Connect it to Backbone and it reads the same pages, context and skills from the first message. Nothing has to be written again.
No lock-in to one AI
Take it out whenever you like: the whole wiki as a .zip, a context as CLAUDE.md or AGENTS.md, a skill in the Agent Skills format.[4]
Backbone WikiPages · context · skills
BillyBuilt in. The context is already in the conversation
ClaudeBackbone connector (MCP)
ChatGPTBackbone connector (MCP)
Claude Code and other MCP clientsBackbone connector (MCP)
Anywhere elseExport as .zip, CLAUDE.md or AGENTS.md
§ 2Three kinds of entry
Everything in the wiki is a Markdown file.[1] What it is for decides where it lives and who reads it when.
Pagenoun
/wiki/how-we-work/invoicing-rules.mdKnowledge, written by people and by AI. Pages sit in folders, link to each other with [[Page title]], and keep every version.
"Invoicing rules", "Kinetik Studio", "Month-end close".
Contextnoun
CLAUDE.md · AGENTS.mdInstructions the assistant reads before it works on a topic, a folder or a client. A context loads always, when the topic matches, when the client is named, or only when asked for.
"Write to Kinetik in German, Sie."
Skillnoun
SKILL.mdA how-to for a whole task, in the same open format as Claude and ChatGPT skills. Yours, and two that come with Backbone: one on using the wiki, one on writing a good page.
"Invoice the month", "Onboard a new client".
§ 3Claude and ChatGPT read it before they work
Connect Backbone to Claude or ChatGPT once, through the AI Connector. From then on your always-on context and the list of your skills travel with the connection, so the AI knows the house rules from the first message.
When a question depends on how you work, the AI searches the wiki and names the page it used. When it works on a client, it is pointed to that client's context. A plain data request, like "list overdue invoices", needs no wiki call at all.[5]
search_wikiFinds pages. A short top hit comes back in full, so most questions take one step.read_wikiReads a page, a context file or a skill.get_contextThe context that applies to a topic, folder or client, in load order.write_wikiCreates or updates a page. Goes to review first.manage_wikiMoves, renames, deletes and restores. Always asks.Works in Claude, ChatGPT, Claude Code and other MCP clients. Reading the wiki doesn't count toward your plan's connector calls.
Your AI tool · Backbone connectedComing soon
What are our payment terms? Kinetik wants to know before they sign.
Backbone · search_wiki "payment terms" → Invoicing rules
14 days net for every invoice. Retainers are invoiced on the first working day of the month, for the month ahead. Hours are invoiced at month end, per client and project.
One thing for Kinetik: their front-end rate is €105.00 an hour, not the usual €110.00.
Sources Invoicing rules · v7Kinetik Studio · context
§ 4Billy knows your company
In the app, Billy doesn't have to look anything up first. The always-on context is already in the conversation, and a client's context arrives the moment you name the client. So Billy drafts the invoice at the right rate, writes in your voice, and follows your process, without being told again.
Ask about this page
From any wiki page, open the chat with the page attached. "Is this still right?" needs no searching.
Your data still wins
If the wiki and Backbone's records disagree, Billy says so and offers to fix the page.
Billy · Werkhaus StudioBackbone AI
Draft the October invoice for Kinetik Studio.
Read: Kinetik Studio (client context) · Invoicing
The draft is ready. Front-end is at €105.00 an hour, the rate on Kinetik's page, not the usual €110.00.
UX design · October · 22.0 h × €95.00€2,090.00
Front-end development · 16.0 h × €105.00€1,680.00
It is a draft. Nothing has been sent.
§ 5AI changes wait for your review
An AI that learns something useful should be able to write it down. It shouldn't be able to change the rules unseen. So every change an AI makes keeps its author and where it came from ("Claude for Sandra"), and, by default, waits under Wiki › Changes until someone applies it.
Review first, by default
Apply, edit first or reject, in a side-by-side diff. You can let pages go live with history instead.
Instructions always wait
Context and skills never go live from an AI write, whatever the setting. Not even from a prompt hidden in a pasted e-mail.
Nothing is lost
Every version stays, with its author and source: the app, Billy's chat, Claude or ChatGPT. Restore makes a new version and never rewrites history.
§ 6Bring your CLAUDE.md, AGENTS.md and SKILL.md
If your team already writes instructions for its AI tools, nothing has to be rewritten. Drop the files in, and they land where they belong.
| You import | It becomes |
|---|---|
| Markdown files in folders | Folders and pages, links included |
CLAUDE.md or AGENTS.md | The context of the folder it sits in |
A folder with a SKILL.md | A skill, with its other files |
A .zip of all of it | All of the above, up to 10 MB |
And out again, whenever you like: the whole wiki as a .zip, a context as CLAUDE.md or AGENTS.md for a code repository, a skill as a .zip in the Agent Skills format for Claude, ChatGPT, Claude Code and other tools that install skills.[4]
§ 7Who sees what
Folders carry the permissions
A folder is visible to the whole workspace, to finance (Owner, Admin and Bookkeeper) or to admins only. Client pages with rates go in a finance folder, so members don't see them.
The AI sees what you see
Claude and ChatGPT sign in as you, so the folders hidden from you are hidden from them. Owners and admins manage folders, context and skills; everyone writes pages.
No secrets in the wiki
Passwords, IBANs, card numbers and API keys are refused when a page is saved, with a pointer to the right place in Settings.
§ 8The twelve volumes
What a studio's wiki might hold, from the sample workspace in our concept screens. Yours will look different, and it can start with a single page.
The page your team and your AI tools check instead of asking you: rates, payment terms, VAT and when to remind. The AI names the page it used.
A client's own context: the exceptions to your rules. It is read the moment that client is named, so the invoice comes out at the agreed rate.
A context that loads when the topic matches: e-mails, quotes, wiki pages. Whoever writes for you, person or AI, in whichever tool, sounds like you.
A whole task as steps the assistant can follow, in the open Agent Skills format. The same skill works in Billy's chat and through the connector, or download it for tools that install skills.
Who does what, and how work gets done. A new colleague reads it on day one, and the AI tools they use read the same pages. The wiki follows Backbone's roles: everyone reads and writes pages.
The wiki lives in Backbone, not inside one AI. A new tool connects through the Backbone connector and reads the same pages, context and skills. And everything exports: the whole wiki as a .zip, a context as CLAUDE.md or AGENTS.md.
The instruction files you already keep for your AI tools. Import them and they become context and skills; export them again for a code repository.
A process, written once: the steps until the bookkeeper has everything. The folder's context tells the assistant to follow it, and never to guess a VAT rate.
One page per client: contacts, what you do for them, what is agreed. It sits next to the client's hours and invoices, and if the page and Backbone's records disagree, Billy says so. The folder is for finance only.
Where AI suggestions wait, from Billy, Claude or ChatGPT alike. Apply, edit first or reject. Context and skills always come through here.
Every version of every page, with its author, its source (the app, Billy, Claude or ChatGPT) and its change note. Restore creates a new version; history is never rewritten.
Questions
Coming soon. There is no date yet, and this page says so until it ships. Everything else in Backbone works today.
No. The wiki works in Backbone on its own, and Billy, the assistant built into Backbone, reads it. The Backbone connector adds Claude, ChatGPT and any other MCP client, whichever you use.
Nothing is lost. The wiki lives in Backbone, not in an AI tool. Connect the new tool through the Backbone connector and it reads the same pages, context and skills. You can also export everything: the whole wiki as a .zip, a context as CLAUDE.md or AGENTS.md, a skill in the Agent Skills format.
No. By default every change an AI makes waits for your review under Wiki › Changes. Context and skills always wait, whatever the setting. Every version keeps its author and where it came from, and can be restored.
Yes. Import Markdown files or a .zip: folders become folders, a CLAUDE.md or AGENTS.md becomes the context of its folder, and a folder with a SKILL.md becomes a skill. You can export the whole wiki as a .zip, a context as CLAUDE.md or AGENTS.md, and a skill in the Agent Skills format.
It shouldn't. Plain data requests, like listing overdue invoices, need no wiki call. The wiki is read when a request depends on your rules, a client's details or a process.
Folders carry the permissions: a folder is visible to the whole workspace, to finance (Owner, Admin and Bookkeeper) or to admins only. Claude and ChatGPT sign in as you, so the same folders are hidden from them. Passwords, IBANs, card numbers and API keys are refused when a page is saved.
Every plan.
Notes
- ^Markdown is plain text with light formatting:
#for a heading,-for a list. Every entry can be copied or downloaded as a .md file. - ^Through the Backbone connector, which speaks the Model Context Protocol (MCP), the open standard AI tools use to work with apps. Also Claude Code and other MCP clients.
- CLAUDE.md and AGENTS.md are instruction files that AI coding assistants read before they work in a folder. In the wiki, a context plays that part for a topic, a folder, a client or the whole workspace.
- Agent Skills is the open format for skills: a folder with a
SKILL.mdfile (a name, a description and the steps) and any files it refers to. - ^ChatGPT's connectors use MCP tools only, so everything in the wiki, skills included, is reachable through tools. That works in every client.
Write it down once. Every assistant reads it.
The wiki is coming soon. Everything else in Backbone works today: time, invoices, reminders, receipts and the export for your bookkeeper, with Billy and the AI Connector.
7 days free, card required. €0.00 due today.