---
title: "Introducing the Cloudflare Simulator: an install without a real account"
summary: "A deliberately fake Cloudflare API, consent flow and dashboard for testing the real installer against controlled failures."
created: "2026-11-15"
updated: "2026-11-15"
revision: "1"
previous: ""
reviewedThrough: "b0b2ed37708d39699ee3007262c65b822b04790b"
sourceDigest: "9f9b75e1c10c134e0c3b60ca4518d4ff59283fae708c3bf72f23cb82a4bbca35"
---

With this, your mind can exercise an installer before it asks someone to authorize a real cloud account. The simulator plays Cloudflare’s side of an install: OAuth, account APIs, a dashboard of buttons and a simulated deployed mind. It asks for no real password, payment card or cloud credential and deploys no real Worker.

## An instance URL is its only key

`apps/cloudflare-simulator/app.ts` serves the public `fake-cf` host and its original `cloudflare-simulator` alias. Creating an instance returns a long URL. Anyone holding that URL can read and change that simulated instance; it is not an authenticated private workspace. Share it only when sharing the test state is intended, and put no real personal data or credential into it.

```js
// Against your own simulator host, with no real account involved:
const r = await fetch("/instances", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({ scenario: "free-account" })
});
const instance = await r.json();
```

`instance.ts` defines events, presets and scenarios; `backend.ts` folds an instance record. The API families are split into `api-account.ts`, `api-domain.ts` and `api-workers.ts`, with shared envelopes in `api.ts`. `store.ts` keeps simulated resources as mind files and the state documents an installer sent. Worker code uploaded to the simulator is not executed. `hosts.ts` plays the auxiliary hosts, `mind.ts` the resulting mind, and `cloud.ts` the enrollment and handover service; `signed.ts` supplies the matching simulated statement checks.

## Fail honestly

The important feature is a visible unknown-call error. If the installer calls an API family the simulator does not implement, it receives a Cloudflare-shaped failure with the route named, and the instance records that gap. Presets can refuse consent, omit an account, expire a token or slow an answer. The test suite has a drift check against the routes of actual installer runs so a new production call does not silently become an untested success.

## Rebuild and verify

Keep every page visibly branded as a simulator and retain the made-up-person restriction. Use a newly generated instance and point the installer’s approved alternate cloud base at it; do not proxy its traffic to real Cloudflare as a fallback. The implementation needs the complete simulator folder, its processor and ordinary mind file storage, but no real cloud account, token or paid subscription for the played deployment. Tests cover model reduction, API families, state storage, the played mind and Cloud, and route drift. Simulated success is a contract test, not proof that a real provider accepts a deploy. [The install wizard](/introducing/cloud2) is its principal client; [the blog](/introducing/blog) keeps these public contracts separate from private run records.
