Module Reference

How each part of the code works. Every page follows the same layout: what the module is responsible for (Owns), how other code reaches it (Entry points), and the rules it enforces and depends on (Boundaries). The pages link to source files rather than listing every function, so check the code for the finer details.

To run the system, see Operations. For exact settings and API contracts, see the Reference section. The end-to-end test system is covered under E2E Testing.

Server

Module	Responsibility
Server Application	The OTP supervision tree and configuration.
Server Domain	Ash resources, data-layer authorization, and the generated JSON:API.
Server Web	Routing, request pipelines, operator permissions, LiveViews, and the terminal channel.
Server Devices	Device identity, registration, groups, the command queue, and remote-access leases.
Server Provisioning	AtomixOS bootstrap delivery.
Server Monitoring	Heartbeats, telemetry, alerts, offline detection, and notifications.
Server Scripts	The Stary script workbench.
Server Reporting	Custom telemetry reports.

Client

Module	Responsibility
Client CLI	The nixstasis command tree and configuration loading.
Client Transport	HTTP calls to the server and the connection policy.
Client Identity	Device identity detection and credential storage.
Client Starlark Runtime	Stary script parsing, execution limits, and builtins.
Client Command Handler	Running server commands and the command policy.
Client FRP Manager	Starting frpc and the client-owned route profiles.

Gateway

Module	Responsibility
Gateway Caddy	Public HTTPS, on-demand TLS, AuthCrunch, and gateway trust rules.
Gateway FRP	The FRPS tunnel server and device tunnel authorization.