Export your data under Settings, then Data, then Export.
Knowledge, ready
for anyone who asks.
Customers, developers, employees, and their AI agents all ask. GraphStaff gives them one trusted answer.
Everyone asks
All day, from every direction, someone is asking.
Different askers, same need: an answer they can trust.
A customer · Help center“Can I download invoices as a PDF?”
A coding agent · MCP“How do I paginate through all customers?”
An AI assistant · Company Brain“What changed in the March release?”
A prospect · Website“Do you support SAML SSO with Okta?”
A customer · Help center“Can I download invoices as a PDF?”
A coding agent · MCP“How do I paginate through all customers?”
An AI assistant · Company Brain“What changed in the March release?”
A prospect · Website“Do you support SAML SSO with Okta?”
A developer · API reference“What causes a 429 rate limit error?”
A teammate · Slack“How do I file an expense over $500?”
A support agent · Console“Which plans include audit logs?”
An on-call engineer · Runbook“How do I open a production incident?”
A developer · API reference“What causes a 429 rate limit error?”
A teammate · Slack“How do I file an expense over $500?”
A support agent · Console“Which plans include audit logs?”
An on-call engineer · Runbook“How do I open a production incident?”
Data exports run from the account dashboard.
Sure! You can export straight from the mobile app.
unverifiedwhich one of these is actually current?
GET /v2/exports returns 404. The reference still documents /v1/exports.
They all ask the same questions. Today they get different answers.
GraphStaff connects your knowledge into one governed graph. Every answer, for every asker, comes from it.
PEOPLECustomers · developers · teams
Governed knowledgeOne graph · one policyAI AGENTSClaude · ChatGPT · your stack
SIX SURFACES · ONE POLICY
WebsiteSearchAsk AIMCPllms.txtMarkdown
Start with the audience that matters now.
01For your developers
A developer · and their coding agent“How do I verify webhook signatures?”
Developer Docs and API Docs
Guides, API reference, and grounded answers, with MCP access for the coding agents they already use.
Explore the product →02For your customers
A customer · Help center“How do I add a teammate to my account?”
Knowledge Hubs
A branded help center where customers search, browse, or ask, and find the answer before they open a ticket.
Explore the product →03For your team and its AI
A teammate · asking Claude“How many PTO days carry over?”
Company Brain
The same governed company context for Claude, ChatGPT, and every approved internal AI.
Explore the product →AM
Alex MorganProduct · customers group
GraphStaff policy✓ Allowed contextVISIBLE TO ALEX AND THEIR AI AGENTProduct roadmap · Customer guidance
NOT RETRIEVEDFinance runbook · Executive notes
Questions, answered
Frequently asked questions.
The short version of what teams usually want to know before they see GraphStaff in action.
What exactly is GraphStaff?
GraphStaff is a knowledge platform with three focused products: developer and API documentation, customer-facing knowledge hubs, and a permission-aware Company Brain for internal AI. They share the same publishing, retrieval, access-control, and AI infrastructure.
Can we start with only one product?
Yes. Each product stands on its own. A team can begin with developer docs, a customer knowledge hub, or a Company Brain and expand only when another use case becomes useful.
Does GraphStaff work with AI tools we already use?
Yes. GraphStaff provides an MCP server and other machine-readable surfaces so your knowledge can work with Claude, ChatGPT, coding agents, and your own AI infrastructure without committing to one model vendor.
How do we see whether it fits?
Request a demonstration and tell us which audience and knowledge set matter most. We can plan a focused walkthrough or a proof of concept around your actual use case.
Your knowledge is readyGive it somewhere
Give it somewhere
useful to go.
Start with the audience that matters now. GraphStaff will make the same knowledge ready for everything that comes next.