# How DotMock works

> Follow a definition from authoring through matching, state, rendering, publication, and delivery.

- Canonical URL: https://dotmock.com/docs/concepts/how-it-works
- Capability status: Available
- Last verified: 2026-07-24

## Prerequisites
- None

## In this guide
- A workspace owns one mock surface
- Configuration and runtime data are separate
- Every request follows one order
- Templates preserve JSON types
- Preview safely, then exercise the live URL
- Use the same system from every tool

## Verified boundaries
- Dry-runs disable persistent state writes, webhook delivery, proxying, and callouts.

Read the canonical guide for its complete examples and expected results: https://dotmock.com/docs/concepts/how-it-works