Deploy and URLs

Updated Sep 29, 2026·3 min read

Everything you stage in the app - endpoints, services, settings - reaches the world through a deploy. This page is about that moment: the URL a simulation answers on, what the Deploy button actually does, and the habits that keep deployments optimal.

The URL

A simulation answers at a host of its own:

https://<hostname>.api.<domain>

Its API starts at the top of that host, with no path in front: https://petstore.api.mockz.io/pets.

You name the hostname when you create the simulation. The Deployment tab lets you change it until the first deploy. After that it is fixed, so the address never breaks behind your consumers' backs. A simulation deployed from GitHub takes its repository's name, or the name its workflow asks for. When another simulation already holds a name, yours gets a number after it: petstore-2.

The domain is the Host row on the same tab, and it is fixed at the first deploy too. Six are available, all serving the same platform:

mockz.io - the default
mockz.org
mockz.net
mockzilla.org
mockzilla.de
mockzilla.net

A pull request or a branch deployed from GitHub gets a host of its own beside the simulation's.

See Simulations from GitHub.

Need a domain of your own? Contact us.

What a deploy does

Deploy packages the simulation's current state and ships it to the runtime. The status pill walks through deploying to Active, and the URL serves the new state.

The first deploy of a simulation takes around a minute: the runtime is being placed, in your preferred region when it has capacity. Redeploys are much faster - the runtime exists, only the content changes - which is why the edit-deploy loop feels closer to a save than to a release.

The Deployment tab shows the placement and the runtime numbers each deploy runs with: region, memory, timeout.

See Usage and limits for what shapes those numbers.

Take it offline

A simulation you are not using has no reason to stay deployed. Take offline, in the simulation's menu, stops serving the URL; everything you built stays exactly as it is, and Bring online puts it back.

Build limits

Each deploy is a build, and plans carry a soft allowance for how many builds a month makes sense - Deployments, on the usage panel, counts yours against it. Soft means what it says: the limits exist to keep the platform honest, not to get in your way. If yours do not fit how you work, contact us and we can consider lifting them.