SELF-HOSTED

Tortoise on your own infrastructure

Your data, your ops — the same epistemic memory graph, fully self-managed.
Prefer zero-ops? Try hosted →

What you get: a local FalkorDB graph (or embedded), the MCP server over stdio, and the same 5-question onboarding prompt your agent walks you through. The MCP tool names are identical to hosted — only the transport differs (stdio vs Streamable HTTP).

1Install

Python 3.11+ required. No Docker needed for the embedded mode.

pip install tortoise-graph   # or: pip install -e . from the repo

2Onboard (5 steps)

Run tortoise onboard from your repo — it chains init → index → demo → doctor automatically:

tortoise onboard

Step 1/5: Ensure Tortoise SDK is installed
  ✅ Tortoise installed
Step 2/5: Initialize graph
  ✅ graph ready
Step 3/5: Index repository
  Found 42 markdown files. Indexing…
Step 4/5: First memory demo
  ✅ demo points created
Step 5/5: Health check
  ✅ doctor OK

Onboarding complete.
Next: tortoise serve  — start MCP server for agents
      tortoise setup  — configure per-role memory

Idempotent — re-running skips already-done steps. When it finishes, it prints the canonical onboarding prompt URL — paste that into your agent to complete setup.

3Start the MCP server (stdio)

Connect your agent over stdio (local process) instead of Streamable HTTP. Pick your harness:


    
  

4Role memory (optional)

Configure how Tortoise filters memory per role:

tortoise setup --role developer   # researcher | strategist | developer

Or run tortoise setup interactively — it walks through episodic / epistemic / semantic / procedural / working memory per role.

5Docker vs embedded

Embedded (default)Docker / FalkorDB
SetupZero deps — tortoise onboard uses the embedded default when no URI is configureddocker run falkordb/falkordb + set TORTOISE_DB_URI
DurabilitySingle-node, file-backedAOF + backups, multi-node
Best forSolo dev, laptopTeams, production
Inittortoise init resolves: --pathTORTOISE_DB_URI (docker:// / redis:// / rediss://) → legacy FALKORDB_*TORTOISE_DB_PATH → embedded defaulttortoise init connects to the docker:// / redis:// / rediss:// URI from TORTOISE_DB_URI
Onboarding prompt: after setup, paste the canonical prompt into your agent — it drives the same 5 yes/no questions (connect sources, record sessions, demo graph, ingest docs, verify) against your local MCP server. Fetch it at premiselabs.co/onboarding-prompt.md or run tortoise onboard and copy the URL it prints.
Hosted (zero-ops) → GitHub →