Engineering

Sleeping for 14 days without a server

How step.sleep works under the hood, and why a sleeping run costs nothing.

Lena Ferris

Founding engineer

4 min read

Sleeping for 14 days without a server cover

A trial-expiry workflow sleeps for 14 days between signing up and sending an offer. Nothing should be running during those 14 days.

Sleeping is a scheduled event

When your code calls step.sleep, the run’s state is saved and a wake-up is scheduled. Your process can exit, deploy or scale to zero.

Waking up

At the scheduled time, the runtime calls your code again, restores finished steps from memo, and continues from the line after the sleep.

Get started

Ship the agent. Keep the receipts.

Free for 50,000 steps a month. No credit card, no separate workers, and your first durable workflow deployed before lunch.

orrindel

Durable runtime for AI agents and automations. Every run, in plain text.

Book a 20-minute demo →
All systems normal
99.99% uptime · last 90 days
90 days agotoday
regions us-east · eu-west · ap-south
soc 2 type ii · gdpr · hipaa (baa)
sdk v4.2.1 · node · python · go
© 2026 Orrindel Labs, Inc.PrivacyTermsSecurityMade in plain text.

Create a free website with Framer, the website builder loved by startups, designers and agencies.