Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.memorycrystal.ai/llms.txt

Use this file to discover all available pages before exploring further.

Self-hosting means you run important infrastructure yourself instead of using Memory Crystal’s hosted backend.

​
Pick the right path

PathUse whenStart here
Local-first Docker backendYou want Memory Crystal data on one machine with installer-managed Docker ConvexLocal-First Setup
External self-hosted backendYou operate your own service/deploymentRailway deployment
Hosted cloudYou want the simplest managed pathQuick Start
Local-first still uses hosted Memory Crystal auth/license. External self-hosting may require additional environment variables and deployment setup.

​
Public boundary

Public docs should explain supported deployment behavior without exposing hosted SaaS-only internals such as billing, admin, private dashboard code, or internal planning docs.

​
Source material

The strongest public sources are:
  • mcp-server/README.md
  • apps/docs/self-hosting/railway.mdx
  • .env.example
  • scripts/convex-local-up.sh
  • scripts/convex-local-doctor.sh

​
Common mistakes

  • treating local-first as accountless/offline licensing
  • mixing private SaaS architecture with public self-hosting guidance
  • documenting the root web app deployment as if it were the MCP deployment path
  • linking public users to internal contributor docs instead of the public local-first guide