Understand how AKStream.Next works

Start with four questions: Where is the device? Which channel carries the picture? Is media flowing now? Who may view it? You can follow the installation guide first and return here when adding more devices, deploying multiple servers, or writing an integration.

flowchart LR
    D["Camera / NVR / GB28181 platform"] --> C["AKStream.Next manages devices and channels"]
    C --> M["MediaServer carries audio and video"]
    M --> P["Browser / app playback"]
    C --> R["Recording jobs and file indexes"]
    C --> A["Identity, permissions, short-lived tickets"]
    A --> P

AKStream.Next manages identities, channels, jobs, and APIs. MediaServer handles media connections and protocol outputs. NodeAgent manages an allowed set of service lifecycle actions. The database stores configuration, state, and indexes. All these services can be healthy while a camera is offline or a viewer's network cannot reach the stream.

Find the explanation you need

Question	Read next
Why does a channel exist without a picture?	Devices, channels, streams, and media nodes
What happens after someone clicks Play?	The path from live view to recording
Which component owns which data and recovery action?	Services, nodes, and data
Why are login sessions and playback tickets different?	Identity, permissions, and tickets
How are snapshots and meeting recordings different?	Kinds of video output

These pages explain cause and effect without asking you to memorize every API field. For hands-on tasks, continue with Using the features; developers can follow API integration or RTC SDK integration.