Web framework for Koru.
Orisha is a web framework built on Koru. It supports traditional REST endpoints, but its killer feature is accepting Koru source code over the wire - clients send entire flows instead of making multiple round trips. The server executes them within budget constraints, with automatic resource cleanup.
Static Routes
Pre-compute HTTP responses at build time. Files read, headers formatted, ETags computed - all before deployment. Runtime just writes bytes to the socket.
Koru Over the Wire
Accept Koru flows from clients. One request replaces multiple round trips. Error handling is part of the flow, not client-side retry logic.
Budgeted Execution
Operations have semantic costs. Clients have budgets. When budget runs out mid-flow, resources clean themselves up via auto-discharge.
Tiny Deployments
Static binaries with no runtime dependencies. FROM scratch Docker images. Runs on edge, lambda, embedded - anywhere binaries run.
Budget as Contract
Semantic cost metering, not request counting. A lookup costs 1, an export costs 500. Clients know their budget. Servers enforce it.
Automatic Cleanup
Phantom types track resource obligations. The interpreter knows how to release them. Budget exhausted mid-flow? Open handles are auto-discharged.
Scope Isolation
Different scopes expose different capabilities. Handles can't cross scope boundaries. Untrusted code runs in constrained scopes.
Tiny Deployments
Static binaries with no runtime dependencies. FROM scratch Docker images. Runs anywhere binaries run.
Documentation
API Reference
Events, types, and patterns for building web services
Static Routes
Compile-time route collection and response generation
Budgeted Interpreter
Scopes, costs, handle pools, auto-discharge
Deployment
Docker, edge, configuration
Examples
Real-world patterns and recipes
Roadmap
What's done, what's next