// the find
deskree-inc/blok
Blok is an open-source framework that enables developers to build lightweight, modular, and scalable backend applications using nanoservices.
Blok is a TypeScript framework for building backends as "nanoservices": small, single-responsibility nodes wired into workflows via triggers, with a CLI (nanoctl) for scaffolding, running, and deploying them. It's aimed at teams who want microservice-style isolation without standing up a fleet of actual services.
The monorepo has real architectural boundaries, not just naming: core/runner is a gRPC/protobuf-based execution engine (proto/node.proto, NodeGrpcClient, NodeGrpcNativeClient) separate from core/shared's base types and core/workflow-helper's programmatic workflow builder. The CLI is a genuine toolchain rather than a thin wrapper — create, build, deploy, login, monitor, publish, and an AI-assisted node generator with its own prompt files. They ship a full observability stack for local dev (Grafana, Prometheus, Loki, Tempo, Telegraf docker-compose under infra/metrics), which signals they've actually run these workflows in something resembling production. There's real test coverage across the runner, workflow-helper, and CLI packages instead of the usual zero-test side-project pattern.
Using gRPC/protobuf for inter-node calls is a heavy choice for something pitched as "lightweight" — buf codegen, a native gRPC client, and proto schemas add real operational overhead versus just composing functions, and the README doesn't justify why this beats simpler in-process composition. The CLI bakes in login/deploy/publish flows pointing at a hosted service, so it's worth checking before adopting how much of the actual workflow lives behind deskree's commercial control plane versus staying fully open and self-hostable. The README leans on vague value-prop language ("modular," "future-proof," "efficient and scalable") without a single non-trivial workflow example, so it's hard to judge real ergonomics without installing nanoctl and trying it yourself. There are stray binary .dat files and a toc.dat checked into infra/development, which is a small but telling sign of housekeeping gaps for a project selling engineering rigor as its main pitch.