Run an MDK site
Choose and run an MDK site deployment topology.
Overview
Use these guides to choose a site deployment shape.
If Kernel, Gateway, Worker, manager, or thing are unfamiliar, read terminology first. If you are choosing between topologies, read deployment topologies.
Choose a guide
- Run a multi-Worker site as separate, PM2-supervised processes, from one machine up to a cross-host deployment, using supervised services
- Configure MDK on managed infrastructure with the hosted-site reference configuration: networks, allowlists, a monitoring-only and a delegated-writes profile, and MCP off or on loopback
- Keep every process off the public HyperDHT with the local and air-gapped profile: private bootstrap nodes and an explicit bind interface, on one machine, an isolated LAN or Docker
Next steps
- Understand the trade-offs before you choose your deployment topology
- Measure real CPU, RAM, disk, and latency for your own hardware and device count with the benchmark harness
- Check published benchmark results, measured limits, and recommended operating envelopes before sizing a site
- Browse the functions that wire together the Kernel, device Workers, and the Gateway HTTP
- Follow the site security blueprint: identity, allowlists, and network options for a real site