Deployment topologies

The word “server” hides several boundaries. Start with who initiates work and what protocol crosses the process edge.

Decision table

Need	Use	Status	Boundary
Product code starts a workflow	`LocalNika`	Live	argv + NDJSON to the local binary
The project clock starts work	`nika serve`	Live	`nika.yaml arm[]` to the resident firer
The host scheduler starts work	`nika arm --emit`	Live	launchd or systemd to `nika arm fire`
The engine needs local inference	`nika model serve`	Live	Loopback OpenAI-compatible model API
An application needs remote workflow jobs	Root `Nika` client	Preview	Intended HTTP + SSE workflow API

Request-driven application

const handle = nika.run('workflows/support.nika.yaml', {
  vars: { ticket: request.id },
  signal: request.signal,
})

for await (const event of handle) render(event)

The application owns the user experience and cancellation. The engine owns workflow admission, execution and the receipt.

Clock-driven project

container / bare VM ── nika serve ──────┐
                                         ├── one firer ── run + ledger
managed host ───────── launchd / systemd ┘

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

nika model serve --model Qwen/Qwen3-0.6B-GGUF --port 8712

This process serves a model on loopback for the engine to call. It does not accept Nika workflow jobs.

Remote workflow horizon

The root SDK already types jobs, workflow listing, SSE, artifacts and webhook verification. The reference engine does not ship the compatible workflow HTTP service today. nika serve and nika model serve are not substitutes.

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

Explore the preview HTTP contract.

Project setup

Place control, intent, application code and state.

Overview

Start

Project · live

Local API · live

Runtime · live

Remote API · preview

Operations

Reference

Deployment topologies

Decision table

Request-driven application

Clock-driven project

Inference provider

Remote workflow horizon

Architecture view

Continue

Server surfaces

Resident server

Remote client

Project setup

​Decision table

​Request-driven application

​Clock-driven project

​Inference provider

​Remote workflow horizon

​Architecture view

​Continue

Server surfaces

Resident server

Remote client

Project setup

Decision table

Request-driven application

Clock-driven project

Inference provider

Remote workflow horizon

Architecture view

Continue