How It Works
Three commands. Full control.
Inspect, preview, deploy. Every step is transparent — you always know what's happening before it happens.
pikku deploy info
See what will deploy — units, queues, cron triggers, secrets, and which roles each worker needs. No changes made.
pikku deploy plan
Dry-run that shows exactly what will be created, updated, deleted, or drained. Review before you commit.
pikku deploy apply
Deploys everything to your Cloudflare account. Workers, queues, cron triggers, D1, KV, secrets — all wired up.
Units:
api-get-users http
api-create-order http
send-welcome-email queue
daily-cleanup cron
Queues:
welcome-emails consumer: send-welcome-email
Secrets:
DATABASE_URL bound to all units
STRIPE_KEY bound to api-create-order
+ create api-get-users worker
+ create api-create-order worker
+ create send-welcome-email worker
+ create welcome-emails queue
+ create daily-cleanup cron
~ update DATABASE_URL secret
- delete old-webhook-handler worker
3 to create, 1 to update, 1 to delete
Building workers...
+ api-get-users built 148 KB
+ api-create-order built 203 KB
+ send-welcome-email built 52 KB
+ daily-cleanup built 34 KB
Build complete.
Deploying to Cloudflare...
Deployment complete. 4 workers deployed.
What Gets Deployed
Everything your app needs. Auto-configured.
Pikku reads your function signatures and figures out which Cloudflare resources to provision. You don't write wrangler.toml by hand.
Workers
One per function or unit. Each worker is independently deployable and scalable.
Queues
Cloudflare Queues with consumers auto-wired to the right worker. No manual binding.
Cron Triggers
Scheduled tasks deployed as cron triggers. Set the schedule in your function metadata.
D1 Databases
For workflow state, session storage, or anything else. Bindings handled automatically.
KV Namespaces
Key-value storage for caching, config, or feature flags. Created and bound for you.
Secrets & Variables
Environment variables and secrets deployed to the workers that need them. No leaking across boundaries.
Prerequisites
Three things. That's it.
Install the deploy package, set two environment variables, and you're ready to go.
No wrangler.toml needed
Pikku generates all Cloudflare configuration from your function signatures. No manual config files.
Incremental deploys
Only changed workers get redeployed. Unchanged workers are left alone — fast and safe.
Rollback-friendly
Every deploy is traceable. Run plan before apply, and you always know what changed.
Ship to the edge
Your functions, deployed as Cloudflare Workers. Queues, cron, D1, KV — all handled.