Skip to main content
Three surfaces can sound like a server. They do different jobs and accept different clients.

Truth table

The resident firer and local model endpoint ship in the released engine. The workflow HTTP API does not. Similar names do not make them compatible protocols.

Local application path

This path requires no daemon.

Local model path

The engine calls that inference endpoint as a provider. Application code does not submit workflow jobs to it.

Remote workflow path

NAME COLLISION ยท THREE DIFFERENT BOUNDARIES

Continue

Remote client

Explore the intended application boundary.

Local models

Run inference on your own machine.

LocalNika

Use the released application seam today.

ARM and servers

Read the stable deployment reference.

Resident server

Operate the project clock on a container, VM or bare server.

Server runbook

Supervise and probe the foreground process in production.

Deployment topologies

Choose a boundary by the job it owns.