May 12, 2026

MockForge Cloud is Here

After two years building MockForge as an OSS multi-protocol mock server, we've launched the managed version. You can now deploy a hosted mock from a spec in 30 seconds — and keep every line of the open-source workflow you already had.

What you get

Sign up at app.mockforge.dev, drop in an OpenAPI spec, gRPC proto, or GraphQL schema, and we'll deploy it to a public URL at <slug>.mocks.mockforge.dev. You don't run a Fly machine, you don't manage a Docker image, you don't think about TLS certificates. The mock is up.

On Pro ($29/mo), you get three concurrent hosted mocks with HTTP and gRPC. On Team ($99/mo), unlimited mocks across all ten supported protocols — HTTP, gRPC, WebSocket, GraphQL, Kafka, MQTT, AMQP, SMTP, FTP, and TCP. Free stays as it always was: a 10,000-request OSS plan, no hosted infrastructure, but the full CLI for local work.

Why a managed product

The OSS server has always been the right tool when you can run it yourself. Lots of teams can't, or don't want to spend two engineering days a quarter keeping it that way. Hosted mocks remove that operational tax: someone needs a mock endpoint for a demo, a customer prototype, or a CI smoke test, and the answer is now a URL, not a deployment.

We kept the OSS path intentional. The cloud version uses the same engine, the same data-drift behaviors, the same chaos primitives. If you outgrow our managed pricing or want to self-host, your existing config still runs against the OSS binary. No re-write, no migration project.

What's actually different from a typical "mock service" SaaS

Three things, mostly:

Protocols beyond HTTP. Most managed mock products are HTTP-only. If your service talks gRPC, consumes Kafka, or exposes a WebSocket, we have you. The same deployment can speak several protocols at once.
Realistic behavior, not static replays. Hosted mocks inherit latency injection, fault scenarios, partial-response simulation, and data drift from the OSS engine. Your CI tests against a service that misbehaves the way real services misbehave.
Cost cap built in. Per-deployment rate limits and body-size caps are enabled by default, so a runaway client can't accidentally hand you a $500 Fly bill on a $29 plan. That part shipped last week — there's a retrospective if you want the design notes.

Try it

The fastest path is app.mockforge.dev/register, then paste a spec. If you'd rather drive it from the terminal, the OSS CLI gained a cloud deploy subcommand:

$ mockforge login --service-url https://api.mockforge.dev
$ mockforge cloud deploy --spec openapi.yaml --name my-mock --wait
✔ Deployed: https://my-mock.mocks.mockforge.dev

That's it. The OSS docs at docs.mockforge.dev still cover everything you'd run locally — none of it has changed.

What's next

The launch-window roadmap is short and specific: a GitHub Action wrapper so mockforge/setup@v1 drops mocks into anyone's CI in two lines; AI-generated mocks from a natural-language description (currently in private beta); and real-time collaborative mock editing for the Team tier. We'll write each up here as it lands.

Thanks to everyone who beta-tested the cloud over the last few months. The bug reports were honest and the feature requests were sharper than ours.