Try the live demo

You can try Zilean without installing anything at https://demo.zilean.dev.

What you get

Select Start demo on the landing page, complete the verification check, and wait for the instance to start (usually under a minute). You receive:

• A private instance. It is yours alone; nothing you do affects another visitor.
• Automatic sign-in. You land in the admin UI already signed in as a Super Admin. The banner at the top of the page shows the login, and if you log out, the login page shows it too, so you can sign back in.
• Sample data. Six sample HTTP jobs in the groups Demo/Payments, Demo/Marketing and Demo/Ops (cron, rate, looping, failing, one-off and disabled examples), 24 hours of call history so the activity bars are populated, and a manual workflow named Demo/Health probe.
• A demo banner with Reset demo (discards your changes and starts a fresh instance) and End demo (closes your session and discards its data). Both ask for confirmation.

Time limits

A demo ends after 15 minutes without activity, or after 1 hour in total, whichever comes first. When it ends, the instance and everything you created in it are destroyed. Opening the demo address afterwards shows an expired page, and you can start a new demo.

What is not available

The demo never runs operator-supplied code and sends nothing outward, so these actions are refused with a message ending in is not available in the demo. Direct requests receive a 403. A job import (NDJSON) still responds 200, reports each refused row as a row error with the same message, and imports the other rows. Listing users, roles and invites still works, and the admin UI shows the refused controls disabled with a hint:

Area	Refused
Script jobs	Creating or editing (403), or importing (row error), a job of type bash, javascript, typescript or groovy
Workflows	Saving a workflow that contains a script block
SMTP	Changing SMTP settings; sending a test email
Notification targets	Creating, changing or deleting targets; testing a target
MCP	Changing MCP settings (creating and revoking MCP tokens still works)
Passwords	Changing a password
Users	Creating, editing, resetting the password of, or deleting a user
Roles	Creating, editing or deleting a role
Invites	Creating or resending an invite

The demo instance also has no access to the internet. HTTP jobs that call external addresses fail; the sample jobs call a built-in echo service instead.

Limits per visitor

• One demo at a time per network. The limit applies to your IPv4 address, or to your IPv6 /64 prefix, so a different browser or tab on the same network does not get a second demo. Ending or resetting your demo frees the slot.
• A global capacity cap. Only a fixed number of demos run at once across all visitors.
• A start rate limit. Starts and resets are limited separately: more than three starts, or more than three resets, in a minute from the same network is refused.

When a request is refused, the page shows a message; clients that ask for JSON receive an error code instead:

Situation	HTTP status	error code	Page message
You already have a demo running	429	ip_limit	You already have a demo running
All demo slots are in use	503	busy	Demos are busy, try again shortly
More than three starts, or more than three resets, in a minute	429	rate_limited	(JSON response only)
New demos are paused	503	paused	Demos are paused
Verification check failed	403	turnstile	The landing page is shown again
Demo could not be prepared	503 or 502	unavailable	Demo temporarily unavailable

Pausing stops new starts; demos already running are not ended by the Worker. To run Zilean yourself, see Installation.