Self-hosted backends overview
A self-hosted backend is the same backend we host, shipped as an image you run in your own network. It serves the same providers, answers the same way, and takes the same scenarios and contexts. The difference is where it runs: on your machines, with no calls to us unless you let it fetch its license.
For a backend we run for you, see the hosted pages.
Who it is for
Teams whose tests cannot reach the internet: a closed CI, data that must stay inside, or a security review that rules out outside calls.
It also suits heavy load. A hosted backend's requests count toward your plan's monthly requests and throughput. A self-hosted backend has no such limit: it answers as many requests as your own machines can take.
If your tests can reach us and fit your plan, a hosted backend is less to run.
From trial to a running container
- Try it. Ask for a free trial of a type, such as payments. We read every request and email you the decision.
- Make a backend. It has a name, the name its image is pulled as, and the providers the image includes.
- Build an image. Each build puts a new version of the image in your own registry, with the license inside.
- Pull it. Sign in to your registry with a credential, directly or through Artifactory, Nexus or Harbor.
- Run it. Anywhere an image runs: docker, compose or Kubernetes. It keeps its data in memory, in SQLite or in a database of yours.
Each step has a page of its own, listed at the end of this one.
What you get
- An image in a registry of your own, at
<your-org>.registry.mockzilla.org. Pull it directly or through Artifactory, Nexus or Harbor, or carry it to a host with no network at all. - The license inside the image, so it runs with no connection to us.
- A security report for every build: the components the image holds, its known vulnerabilities with what we say about each, and a scan of the base it runs on.
- Every storage driver the release ships, such as SQLite, PostgreSQL or MongoDB. An image can include all of them, at no extra cost.
- Your own scenarios and contexts, packed into the image when you build it. A config folder you mount when you run the image overrides them, file by file, with no new build.
- Setup steps for your team: a quick start for docker, compose and Kubernetes, and a README next to the image that anyone with a registry credential can read, with no Mockzilla account.
Where you find it
- Backend store, switched to Self-hosted: the types you can run, their trials, and buying.
- Self-hosted, in the sidebar: your self-hosted backends, each with its image, license, builds and setup.
- Settings, under Image registry: the credentials that pull your images. The tab appears once you have a self-hosted backend.
Owners and admins ask for trials and manage self-hosted backends. An order also needs your billing details, which only an owner can fill in.
The license
Every image carries a license that says which providers it may serve, and until when. How a new license reaches a running image depends on how you pay:
- Monthly, by card: the image fetches its license from one address of ours and checks it every hour, so each month you pay reaches it by itself.
- Yearly, on invoice: the image needs no connection to us. It can fetch its license the same way, or carry it inside and read a file you mount.
See Licenses.
Paying
Self-hosted providers are bought one by one, for self-hosted backends only. A provider you hold for hosted backends does not cover a self-hosted one, and your plan makes no difference.
- Monthly, by card: it renews on the 1st, and you cancel it under Billing, in Subscriptions.
- Yearly, on invoice: an invoice follows the order, due in 30 days. Once it is paid, the providers are yours for a year. A year costs as much as ten months.
Either way, an order needs your Billing details first.
See Buy self-hosted providers.