Documentation Index
Fetch the complete documentation index at: https://docs.mistle.dev/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The easiest way to get Mistle up and running is to use Docker Compose.Prerequisites
- Docker Desktop or Docker Engine
- Docker Compose V2
- Network access for image pulls
Quick Start
Choose one of these two entry points:- Recommended: from remote installer (no repository checkout required):
- Alternative: from a source checkout (recommended for contributors/workflow customization):
~/.mistle/local, preserves an existing .env,
and starts the stack by executing ./up.sh.
If you use the source checkout path, keep local changes in .env and .generated/runtime.env.
If you use the installer, keep your working files under ~/.mistle/local.
What ./up.sh does
- creates
.envfrom.env.examplewhen missing - validates required values such as
MISTLE_DOCKER_IMAGEandMISTLE_SANDBOX_DEFAULT_BASE_IMAGE - writes a per-run
./.generated/runtime.envand starts Compose services - starts base infra (
postgres,valkey,seaweedfs,mailpit) first - ensures the local object-store bucket exists
- starts the
mistleservice - sets callback behavior:
- if
MISTLE_SERVICES_CONTROL_PLANE_API_PUBLIC_URLis blank, it starts a Cloudflare tunnel for an ephemeral public callback URL - if set, that static URL is used
- if
Open the stack
- Dashboard:
http://localhost:3000 - Control Plane API:
http://localhost:5100 - Data Plane Gateway:
http://localhost:5202 - Tokenizer Proxy:
http://localhost:5205 - Mailpit UI:
http://localhost:8025
Verify your run
- Open the dashboard URL and complete authentication.
- Confirm health endpoints:
- If you cloned the repository locally, run the local smoke test:
Stop and cleanup
When you want to stop the local stack:deploy/compose/local instead of ~/.mistle/local.
To remove local data as well:
Public callback URLs
Provider callbacks and webhooks need a publicly reachable control-plane URL. That value isMISTLE_SERVICES_CONTROL_PLANE_API_PUBLIC_URL (or the generated quick-tunnel URL in local .generated/runtime.env).
Use Webhook and Callback URLs when configuring provider registrations.
Next steps
- Read Integrations Overview
- Confirm deployment settings in Configuration Reference
- Enable provider targets in Provision Integration Targets