Skip to main content
Live project control plane. The released engine discovers nika.yaml from the working directory toward its ancestors. The file is optional when built-in defaults are enough. Its project-shape grammar is closed: nika · ceiling · arm · traces · registry. Direct runs and the cadence path (nika arm · nika serve) read the same file.
The word “server” hides several boundaries. Start with who initiates work and what protocol crosses the process edge.

Decision table

Request-driven application

The application owns the user experience and cancellation. The engine owns workflow admission, execution and the receipt. inputs carries literal typed values — see configuration for why the deprecated vars operator channel is not the app door.

Clock-driven project

Both lanes consume the same arm: registry. Choose based on who should own process lifetime and wakeups, not because one lane changes workflow semantics.

Inference provider

This process serves a pulled Qwen3-family model on loopback for the engine to call (NIKA_LLAMACPP_BASE_URL=http://127.0.0.1:8712, then model: llamacpp/<model id>). It does not accept Nika workflow jobs.

Loopback HTTP (opt-in)

nika serve --bind is not nika model serve, and it is not bare nika serve. The pinned OpenAPI exposes cancellation as an action; the runtime’s settlement determines the result. A settled job’s artifacts, listed from its sealed journal, download over the same door (Outputs and artifacts). Job listing and POST /v1/run remain absent.

Architecture view

PROCESS TOPOLOGY · NAME THE EDGE

Continue

Server surfaces

The compact truth table for similarly named commands.

Resident server

Run the stable project clock.

Remote client

Typed client. Measure it against the OpenAPI of the binary you hold.

Project setup

Place control, intent, application code and state.