Technology

Fujin is a high-performance fabric for commands, events, WebSockets, and machine telemetry. Every service speaks through it instead of calling each other directly.

A command issued in the UI, a sensor reading from a machine, or a progress event from a print job all travel the same bus with the same delivery guarantees. Live screens update over WebSockets without polling.

Because traffic flows through one fabric, it can be traced, replayed, and rate-limited in one place.

Outcome: services stay decoupled, live updates work out of the box, and every event in the workshop is observable.

Centimatus runs explicit workflows: multi-step processes defined as data, executed step by step, with retries and compensation when something fails.

Services never depend on each other directly. Instead of a chain of synchronous calls, a workflow coordinates them — an order moves from payment to slicing to production as steps complete.

Every run leaves an audit trail: what started, what finished, what was retried, and why. Long-running production jobs survive restarts.

Outcome: business processes are visible and resilient, and services can be replaced without rewiring the workshop.

Resonus is one realtime interface for voice calls, media streams, transcription, and AI provider adapters. Calls with customers, shop-floor audio, and AI assistants all plug into the same layer.

A conversation can move from a phone call to a transcript to an AI summary without changing systems. Provider adapters keep the workshop independent of any single AI vendor.

Media is treated as first-class data: recordings attach to orders, machines, and events instead of living in a separate tool.

Outcome: voice and media live inside the workflow, and AI features can be swapped or upgraded without rebuilding telephony.

Ptah is the deployment orchestrator. Depending on the installation type — Edge, Server, or Cluster — it manages the creation and distribution of containers and data across the topology.

Unlike traditional managers, control logic is written as TypeScript scripts while the core is written in Zig. The core consumes only a few megabytes of memory, yet the scripts can carry complex business logic: placement rules, rollout order, failover, and data distribution.

Scripts update dynamically without rebuilding the core, so deployment behavior evolves with the workshop instead of requiring new releases.

Outcome: one orchestrator covers every installation type, stays tiny in memory, and updates its logic on the fly.

Cruller is a multithreaded runtime framework optimized for sustained loads — from UI delivery to machine control. It is not a single engine: it carries three separate JS engines for different tasks behind one common interface.

V8 takes heavy computational work where raw throughput matters. WebKit fits where memory and computation must stay balanced. QuickJS covers the cases where microscopic memory consumption is the requirement.

The core talks to files, HTTP, WebSockets, and ZMQ transports, while the engines execute business logic in isolated threads. The workload decides which engine runs — the interface stays the same.

Outcome: one runtime from lightweight UI to heavy compute, with the right engine and only the memory each job needs.