One command. Everything deploys.
Each function becomes its own serverless worker on Cloudflare's edge. APIs, queues, cron, agents — all live in seconds. You don't configure any of it.
Hybrid Runtime
Edge when you can. Server when you need to.
Most of your functions run as serverless workers on Cloudflare's edge — fast, cheap, scales to zero. But sometimes you need heavy compute, native addons, or libraries that are just too big for Workers. Fabric spins up a managed server for those automatically.
Dashboard
See functions, not infrastructure.
Your dashboard shows sendReminder and what it's wired to — not worker IDs and queue ARNs. When something breaks, you see which function failed and why. Not which container returned a 500.
Credentials
Your session follows you everywhere.
When a user triggers an action, their identity doesn't stop at the HTTP handler. Queue jobs, workflow steps, agent tool calls — they all know who the user is and what they're allowed to do. You don't have to manually thread tokens through message payloads or re-authenticate at every hop.
Plugins
2,500+ API integrations from any OpenAPI spec.
Point Fabric at any OpenAPI spec and it generates typed Pikku functions for every endpoint. Use them in workflows, expose them as agent tools, wire them to cron. Stripe, GitHub, Slack, Notion — if it has a spec, it's already a Pikku function.
Deploy
Push code. Everything is live.
No Cloudflare account to set up. No API tokens to rotate. No Wrangler configs. Just push your code and your entire backend goes live — APIs, queues, cron, agents, all of it. Staging, production, and branch previews come for free.
Observability
Logs and metrics per function.
Every invocation gets logged with a trace ID that follows the request across surfaces — HTTP, queue, workflow, agent. You can see what happened, per function, in the Fabric dashboard. No extra setup.
Built in
Workflows and AI agents. No extra infrastructure.
If you self-host, workflows need a persistence layer, a replay engine, failure recovery. Agents need conversation state storage and tool execution infra. On Fabric, you just write the function — state persistence, retries, conversation memory are all handled for you.
Teams
Environments, previews, access control.
Branch previews for your entire backend — not just the frontend. Team members with scoped access. Shared secrets per environment. Rollbacks that drain in-flight work before cutting over.
Zero lock-in.
Pikku is open-source and runs anywhere. Your code works on Fabric, on your own Cloudflare account, on Fastify, Express, Lambda, Bun — wherever you want. Same project, your call.
Pricing
The framework is free forever. Fabric adds managed serverless deployment.
Open Source
Free
forever
The full framework. Self-host on your infrastructure.
Fabric Starter
Free
100K invocations / month
Deploy your Pikku project for free.
Fabric Pro
$29/mo
2M invocations included
For production workloads that need room to grow.
Enterprise
Custom
annual contract
Dedicated infrastructure, SLAs, and your own cloud.
FAQ
Can I use Pikku without Fabric?
Yes. Pikku is open-source and runs on any runtime. Fabric is optional managed deployment.
What counts as an invocation?
Each time a function is called — via HTTP request, queue message, cron tick, agent tool call, etc. One invocation = one function execution.
What happens when I hit the Starter limit?
Requests are rejected until the next month. Upgrade to Pro for higher limits and overage billing.
Can I migrate from self-hosted to Fabric?
Yes. Same code, same project. Push to Fabric instead of deploying to your own infra. No rewrites.
When does Fabric launch?
Fabric is in development. Join the waitlist to get early access.
Get early access to Fabric.
One email when it launches. No spam.