Skip to content
sambadocs
ProductWorkflowsPricingDocs
Sign inGet early access
ProductWorkflowsPricingDocsSign in

A home for docs, people & AI

Knowledge that
keeps up.

Bring your docs, repositories, and team knowledge together. Give your people and AI the context to do their best work.

Get early accessExplore the product

Start with a blank page. Connect more when you’re ready.

SambaDocsAcme workspace / Product handbookInteractive preview
AAcme workspace
All bases

Knowledge base

Product handbookDocumentsSourcesPublishing

Workspace

ChatbotsWorkflows
JLJamie LeePersonal workspace
Documents / Getting startedSaved Draft

PRODUCT HANDBOOK

Build something
worth sharing.

Everything you need to get started with Acme.
A little context goes a long way.

Welcome to the teamYour first stop for guides, decisions, and the details that make our product work.

Your first API request

# Let’s make a connection
curl https://api.acme.dev/v1/projects
 -H "Authorization: Bearer $API_KEY"
Edited by Jamie · Just nowmain
Good answers start here.

Give your assistant the context behind your docs.

AVAILABLE CONTEXT
acme/platformRepository source
Product handbookKnowledge base
“Explain authentication using our API source and getting started guide.”
You choose what AI can access.

Write together. Keep a history. Publish when you’re ready.

At home with the tools you use.

GitHub
Claude Code
Codex
Slack
Discord
MCP

One place. A lot of possibilities.

From “where’s that doc?”
to everyone on the same page.

A product handbook. A public help center. A wiki for your codebase. Give each its own space, with the right context and the right access.

01 / COLLECT
acme / platformRepository
Team handbook.mdFile
Product knowledgeBase

A little less scattered.

Write documents and add repositories or files as sources. Import Markdown from your notes, Obsidian vault, or Notion export.

02 / CREATE
Getting startedMake yourself at home.Every good project starts with a little context.

Keep the knowledge moving

Your code changes.
Your docs can follow.

Turn a GitHub event, a schedule, or a manual trigger into a documentation workflow. Give an agent the context and instructions to suggest the next update.

  • Arrange steps on a visual canvas
  • Add conditions and your own prompts
  • Review proposed changes before applying
Build your first workflow
Keep API docs up to dateExample workflow
  1. A pull request is mergedacme/platform · main
    01

Good context. Better answers.

Your knowledge, wherever
the conversation happens.

Ask your product assistantExample

How do I authenticate with the API?

Create an API key in your workspace, then include it in the Authorization header.

Authentication guide

Start with what you need

A blank page.
Or a head start.

Pick a starting point, make it your own.
Connections and AI can come later.

Product documentation

Quickstarts, guides, API references, and release notes.

A wiki for your repository

Bring code context and architecture guides together.

Your team’s shared memory

Internal playbooks, decisions, and the answers people need.

Room to grow

Start small. Build your knowledge.

A plan for your workspace. Your AI usage stays with your provider.

Free

For getting started

$0/ month

A home for your first knowledge base.

  • 1 knowledge base
  • Hosted docs on a SambaDocs subdomain
  • Documents, sources, and MCP access
  • Bring your own AI provider
Start with Free

Pro

For growing teams

$39/ month per workspace

More space for your projects and your people.

  • Unlimited knowledge bases
  • Invite your team to collaborate
  • Remove the SambaDocs badge

A few things worth knowing.

Do I need GitHub or an AI key to start?

No. Start with a private base and write your first document. Add a repository, import files, or connect AI whenever it helps.

Is my knowledge public?

New bases start private. You choose what to publish and which content your readers, chatbots, and MCP clients can access.

Can I use my ChatGPT or Claude subscription?

Compatible MCP clients use their own account and model. Built-in AI needs a provider API key; a consumer chat subscription doesn’t replace one.

Will an agent publish changes automatically?

The workflow shown here proposes changes for you to review. Applying a proposal saves the document; publishing is a separate step.

Let’s make room for what you know

Great work starts
with shared context.

We’re opening SambaDocs to early users.
Tell us what you’re building. We’ll save you a spot.

Get early access

What will you use it for?

We’ll email you when your spot opens. No spam.

sambadocs

A little more connected.

DocumentationPricingEarly access
© 2026 SambaDocs
sambadocs.com
BIH₁≡Write something great

Made for the way you think.

Write in a visual editor or Markdown. Work with an AI assistant, review document history, and keep your content in Git.

03 / SHARE
Getting startedPublished · Public
Engineering playbookPrivate · Your workspace

Share what you mean to.

Publish a docs site for your readers. Keep internal knowledge private and choose what each assistant can access.

  • Check what changedContinue if API files were updated
    02
  • Suggest a docs updateYour agent · Your instructions
    03
    • authentication.mdNeeds review

    − Tokens expire after 24 hours.+ Tokens expire after 7 days.
    + Refresh a token before it expires.

    Proposed changes. You decide what ships.

    An assistant that knows your product.

    Choose a model, instructions, tools, and knowledge for your chatbot. Connect it to Discord or Slack, or enable reader chat on your docs site.

    You choose the content each audience can use.
    MCP
    Your knowledge bases

    Your provider. Your key. Your choice. Built-in AI uses your API key from OpenAI, Anthropic, Google, or OpenRouter. Model usage is billed by your provider. No SambaDocs AI credits.

  • Bring your own AI provider
    • Get Pro early access

    AI usage is billed separately by your provider. Prices in USD.

    Search docsEdit a pageAdd a source

    Bring the AI you already work with.

    Connect Claude Code, Codex, or a compatible MCP client. Search and edit across your bases, with scoped permissions you control.

    Your AI app handles its own account and model.