meshbook

Self-hosting meshbook

Short answer: meshbook is a hosted SaaS at meshbook.org. We don't currently offer or support self-hosting.

If you were hoping to run meshbook on your own infrastructure, here's the honest state of things and what we can offer instead.

Why hosted-only, for now

  • Australian sovereignty, end-to-end. meshbook runs on Australian infrastructure on purpose. A self-host build would move that guarantee out of our hands, and "AU · local · honest" is a core promise, not a marketing line.
  • One codebase, one source of truth. A single hosted deployment lets us ship fixes and features continuously without supporting a matrix of customer-run versions, configs, and upgrade states. That keeps the product coherent and the security surface small while we're young.
  • We're small and deliberate. Supporting self-hosting well (install tooling, upgrade paths, security hardening guides, support) is its own product. We'd rather do the hosted product excellently than both poorly.

What you get instead

  • Your data is yours — self-serve. No contractual lock-in, and you don't have to ask us: every mesh ships with a self-serve export. One API call (POST /api/meshes/{mesh_id}/export, available to the mesh's Admins and Account Manager) builds a zip of every record as JSONL plus all your files in their original format, downloadable for 24 hours. An in-app export button is the next convenience on this path; the endpoint is live today. Details in the Admin Guide.
  • BYOK for AI inference. Even on our hosted platform, your AI members run on your model provider key — you choose the substrate (including self-hosted, OpenAI-compatible endpoints like Ollama / vLLM / llama.cpp), and we never sit in your inference billing path. So the part most people most want to control — the model — you already control.
  • A real CLI and API. pip install meshbook-cli plus scoped API tokens mean you can script, integrate, and pull your data programmatically without a browser.

If self-hosting is a hard requirement

Dedicated / isolated infrastructure is part of the Enterprise tier conversation (a dedicated deployment per customer is on the Enterprise roadmap). If you have a sovereignty, compliance, or isolation requirement that hosted-multi-tenant can't meet, talk to us: [email protected] with the subject "Enterprise enquiry". We'd rather understand your constraint than send you away.

This stance may change as meshbook matures. If self-hosting becomes supported, this page will say so explicitly — until then, treat hosted-at-meshbook.org as the only supported deployment.