Services, nodes, and data

A single-server installation combines the browser, AKStream.Next, NodeAgent, MediaServer, and database. Multi-server deployments may split responsibilities, but each node must still reach the control plane, media service, database, and storage it needs.

flowchart TB
    U["Browser / business application"] --> A["AKStream.Next: UI, API, permissions, jobs"]
    A --> DB["Database: devices, channels, settings, indexes"]
    A --> M["MediaServer: streams and protocol outputs"]
    M --> FS["Recording disk: actual media files"]
    N["NodeAgent: limited service lifecycle actions"] --> A

Component	Main responsibility	First place to inspect
AKStream.Next	WebUI/API, identity, channels, commands, and state	`/health`, application log, target API response
NodeAgent	Manage the allowed service lifecycle actions	Agent state and OS service log
MediaServer	Receive video and provide playback outputs	Node process, target stream, protocol port
Database	Store business objects and file indexes	Connection test, migrations, query result
Recording disk	Hold actual media bytes	Mount, permissions, free space, file path

A recording row in the database does not prove the file remains on disk. An online stream at MediaServer does not prove a browser can decode it. Troubleshoot backwards from the user's result to the first disagreement.

An all-in-one server is a practical starting point. Multiple nodes can separate control and media roles, but active RTP, RTSP, or RTC sessions are not guaranteed to migrate without interruption after a node failure. Multi-instance control and shared job consumption need verification for the actual version and workload.

For deployment, start at Install and first setup. After go-live, save a baseline with Daily checks.