Most backends still treat HTTP as the “first-class citizen,” and everything else (WebSockets, queues, cron, mcp) feels bolted on with custom wiring and their own typings if any.
Pikku aims to take a different approach:
- Define a function once → invoke it from HTTP, WebSockets, queues, cron, or even Postgres.
- Deployment is your choice: single process, containers, serverless, or workers. Pick your own queue library, deploy scheduled tasks via lambda, the choice is endless.
- Fully typed, end-to-end → auto-generated clients are tiny, just thin wrappers over existing libs.
Built-in support for services, middleware, permissions, and auth.
Docs & examples: pikku.dev
Pikku aims to take a different approach:
- Define a function once → invoke it from HTTP, WebSockets, queues, cron, or even Postgres.
- Deployment is your choice: single process, containers, serverless, or workers. Pick your own queue library, deploy scheduled tasks via lambda, the choice is endless.
- Fully typed, end-to-end → auto-generated clients are tiny, just thin wrappers over existing libs.
Built-in support for services, middleware, permissions, and auth.
Docs & examples: pikku.dev