How It Works

mockd runs at the edge, close to wherever your requests originate. Each project is isolated with its own state, so your endpoints, rules, and logs never interfere with each other.

Request Flow

1. A request arrives at <project>.mockd.sh/<path>
2. mockd routes it to the correct project based on the subdomain
3. The path and method are matched to an endpoint, mock rules are evaluated, and the configured response is returned
4. The request is logged automatically
5. Connected WebSocket clients receive the new log entry in real time

Per-Project Isolation

Each project operates independently with its own:

• Endpoints and mock rules — no conflicts between projects
• Request logs — scoped to the project
• WebSocket connections — live updates only for the relevant project
• Storage — dedicated data store per project

Global Distribution

mockd is deployed globally at the edge. Your mock endpoints respond with low latency regardless of where the request originates.