Mocko

Mocko Docs

Dynamic HTTP mocking

Mocko Cloud

Overview

Mocko Cloud is the hosted version of Mocko. Instead of running the CLI or deploying to your own cluster, you sign in at app.mocko.dev and get a public HTTPS mock server that your whole team can reach. The mocks, templating, and flags all behave the way they do everywhere else. What changes is where Mocko runs and what it adds around it.

The same core, hosted for you

A mock in the Cloud is the same kind of mock you would write locally. You match on method and path, render the body with the same templating language, and drive stateful flows with the same flags. If you already know how to build mocks in the open source control panel, you already know how to build them in the Cloud. Those pages are the reference for the mock itself; this section covers only what the hosted platform adds on top.

What the Cloud adds

  • A public URL out of the box. Every project gets its own HTTPS address, so a mock is reachable from a teammate's laptop, a CI job, or a partner's environment with no tunnels or port forwarding to set up.
  • Nothing to run or maintain. There is no CLI to keep open and no image to deploy. You sign in with GitHub and start creating mocks.
  • Team projects. Invite teammates to a project so the same set of mocks is shared, not copied between machines.
  • Request logs. See every request that reaches your project, including its headers and body, to confirm a client is calling what you expect.
  • Local Tunnels. Expose a service running on your own machine through your Cloud host, with your mocks layered on top of it.

Cloud or open source

The two are not competing versions of the same thing. They share a core and then lean in different directions. Open source is built to run inside your own environment; the Cloud is built to remove the running entirely.

Reach for the Cloud whenReach for open source when
You want a shareable mock URL without standing up any infrastructure.Mocks must live in your repository as code and be reviewed like any other change.
A whole team should collaborate on one set of mocks from the browser.Mocko has to run inside your own network, CI, or Kubernetes cluster.
You are demoing, prototyping, or unblocking frontend work quickly.You want to drive mocks from tests with the SDK or manage them in bulk as HCL files.
You do not have to pick one forever. A common path is to prototype in the Cloud, then move the mocks that stick into HCL files so they live with your project.

Next

Sign in and create your first public mock in Getting Started. It takes about the same time as reading this page. If you would rather run Mocko yourself, start with the CLI instead.