Build a simulator
Build a simulator with Diode Vibe
Use Diode Vibe to vibe-code and deploy a simulator app — not to monitor Diode itself (Website monitoring watches resource headroom of sites you deploy). A simulator is a container or static app you build that models something in the real world.
In this example, we'll cover creating a data center efficiency simulator that takes into account facility compute, power, and cooling so you can show how monitoring for efficiency would work.
This is a typical regulated-industry Vibe use case (for example NERC/CIP or SOC 2 environments). Ship something a domain expert can iterate on and a compliance team can accept. See What is Diode Vibe? and regulatory-compliant deployments.
1. Start a Vibe workspace
- Create a Vibe workspace and choose your coding tool (Cursor, Claude, Zed, or similar).
- Create a new project -> a new static site (no stored data) or container app (has stored data).
- Either provide your agent with the project "Agent Instructions" link or select "Auto generate"
2. Prompt the agent to mimic a data center
Tell your coding agent to build a simulator of the data center, giving it all of the systems you'd like to monitor. You can mention it is not a production data-center controller. Have it model the core systems operators actually watch for compute efficiency:
| System | What the simulator should show |
|---|---|
| Compute | CPU/GPU utilization, job queue depth, idle vs busy racks or clusters |
| Power | IT load vs facility load, PUE (or similar efficiency ratio), PDU/rack power |
| Cooling | Inlet temperatures, CRAC/CRAH or liquid-cooling load vs IT heat |
| Workload | Batch vs latency-sensitive jobs, placement that changes efficiency |
| Network / storage (optional) | Congestion or I/O wait that wastes compute |
Keep the first version synthetic: generate time-series metrics, a dashboard (efficiency, hotspots, what-if sliders), and alerts when PUE or utilization crosses a threshold.
TIP: You can make your simulated data feeds be replaceable with real data center feeds when you later wire real telemetry.
3. Deploy and operate the demo
Tell your agent to use the instructions to deploy the app with Vibe.
If you intend to use the simulator as part of a regulated production system, know that the Enterprise plan can place the workspace in an enclave so that the demo (and any later live data) will stay in a regime-bound pool.
4. Quick checklist
- [ ] Workspace and coding tool selected
- [ ] Agent built a simulator of compute, power, and cooling — not a Vibe status page
- [ ] Dashboard shows efficiency (for example PUE) and utilization over time
- [ ] App deployed on Diode; app-runtime monitoring is distinct from simulated facility metrics