Most backend frameworks focus on features. Blok
focuses on clarity. It gives developers the power to build modular, testable, observable systems from the ground up—without having to adopt complex orchestration platforms or serverless lock-in.
As a Blok
developer, you don’t build backends by routing HTTP requests into controllers. You build workflows composed of focused nodes, observe them in real time, test each unit independently, and deploy them across runtimes or teams.
This is backend development that finally feels intentional, measurable, and scalable in design, even before it’s deployed.
Because backend development shouldn’t be a black box.
It’s not a serverless platform. It’s not a monolith. It’s a clean developer-first architecture for building composable logic that can evolve over time.
Being a Blok
developer means:
npm run dev
and immediately get real-time Prometheus metrics on execution time, CPU/memory usage, and data I/O.And when it’s time to modernize existing legacy systems, the Blok
SDKs make it possible to invoke individual nodes directly from a wide range of programming environments—including older or enterprise-grade languages.
The SDKs act as a bridge—letting you modernize one node at a time, without needing a full rewrite or migration.
This isn’t just about what you build—it’s about how confidently and clearly you build it.
A node is the smallest unit of logic—self-contained, reusable, and testable. Nodes are registered and grouped in the src/nodes.ts
file.
A workflow defines how multiple nodes execute together. It includes branching logic, context passing, and output formatting. Workflows are defined in JSON.
The CTX is a shared execution object that flows through your workflow. It carries:
Workflows can be triggered by:
Triggers are defined declaratively and allow the same logic to be accessed from multiple interfaces.
Everything starts with the official CLI, nanoctl
:
Projects include Prometheus metrics out of the box and provide optional Docker + Grafana dashboards for real-time introspection.
You can even combine multiple runtimes in the same project, giving teams the freedom to write in the right tool for the task.
The Blok SDKs let you call any registered node from external code—no matter the language.
This means you can:
For example:
Blok
is not an orchestration platform or cloud service. It’s something different.
It’s a developer architecture. One that gives you:
And most importantly: it’s a framework that trusts you to build systems that grow well.