Playground — try Pulse in your browser

Zero install ⏱ 2 min to first event no signup

Open the playground →

The playground gives you an isolated, ephemeral Pulse sandbox in the browser: write a pulse.yaml, deploy it, send events, and watch the stream process live — the exact same engine and API surface every tutorial on this portal uses.

What you get

• A private sandbox (its own organization, JWT-scoped) — nobody sees your events, you see nobody's.
• The real deploy path: your AppSpec goes through POST /api/pulse/apps and Pulse synthesizes the typed OpenAPI descriptor, a downloadable SDK, a persisted collection and a live SSE stream — the same artifacts pulse deploy . generates.
• The orchestrator view: see how n8n / LangGraph / Temporal / your framework would call the app you just deployed — the same two HTTP calls documented here.

Honest limits (by design)

Limit	Value
Sandbox lifetime	~20 minutes, then auto-cleanup
Engines	streaming + rule-based (no llm/mcp — no keys to leak, no bills to run)
Quotas	2 pipelines · 3 agents · 100 events/min · 64 MB

Everything the sandbox can't do, the quickstart can — locally, in 5 minutes, with all four engines.

From playground to keyboard

The pipeline you built in the browser is a pulse.yaml. Copy it out, then:

pulse server start --dev
mkdir my-app && cd my-app     # paste your pulse.yaml here
pulse deploy .

Same file, same engine — now with LLM/MCP stages, secrets, and no TTL.