Reference · 2 min read
Documentation map
Find the right Miton guide, reference page, essay or trust resource without leaving the public site.
- Product stage
- Pre-release development
- Last reviewed
- 2026-07-23
- Successful result
- The change is visible in the active project.
Choose by intent
| I want to… | Go to |
|---|---|
| Install Miton when beta access opens | Beta access and installation |
| Connect a cloud or local model | Connect models |
| Understand projects and shared state | Your first project |
| Design an interface | Canvas |
| Draft or revise a document | Writer |
| Build a repeatable workflow | Automation |
| Work with a software repository | Code |
| Understand routing and cost | Models, routing and costs |
| Review permissions and privacy | Safety and permissions |
| Recover from a failure | Troubleshooting |
Guides and reference
Guides are task-first: they state what the task accomplishes, what is available, what you need, the steps, the successful result and recovery paths. Reference pages define controls, files and terms you may need while following a guide.
- Keybindings
- Slash commands
- Permission modes
- Configuration files
- Environment variables
- Glossary
- Architecture concepts
- LAN access and mDNS discovery
Product arguments and trust
Docs explain how to use Miton. The rest of the public site explains why it exists and what evidence supports its claims.
- Why Miton — architecture, routing, token economics, local models and safety.
- Product walkthrough — one project across every workspace.
- Security — permissions, injection defence, egress and privacy boundaries.
- Roadmap — qualified future work that does not belong in current instructions.
- Journal — signed essays and white papers.
- Pricing — intended Australian-dollar pricing and licence scope.
Everything needed to understand or use a documented public capability is contained in this site. Internal plans, source records and contributor evidence are deliberately outside the Docs journey.