Local Server Recording
Positioning, differences from cloud recording, deployment model, capabilities and boundaries.
Local Server Recording
Local server recording (Agora's "On-Premise Recording" product line) runs the recorder on the customer's own Linux server: the process joins a channel as a virtual participant and writes media to local disk, or hands it to a co-located egress service.
ni-meet provides local server recording as a Linux C++ SDK: 54 interfaces, 100 methods and 48 enums, aligned with Agora on-premise recording Linux C++ v4.4.151.
Local versus cloud recording
| Aspect | Local server recording | Cloud recording |
|---|---|---|
| Runs on | Customer server (Linux) | ni-meet managed region |
| Control path | In-process C++ calls + local REST | HTTPS REST + callbacks |
| Output | Local disk / customer object storage | Platform object storage |
| Billing | Server/concurrency licence (see Limits & pricing) | Per recorded minute |
Pages
| Page | Contents |
|---|---|
| Concepts | Engine, sink, session, output |
| Enable the service | Project credentials and quotas |
| Quick start | Build, initialise, record a first MP4 |
| Recording modes | Individual / composite / page |
| State machine | idle → starting → recording → stopping → stopped / error |
| API reference | C++ surface plus the local REST control plane |
| Callbacks | IRecordingEngineEventHandler / IAgoraMediaRtcRecorderEventHandler |
| Error codes | ERROR_CODE_TYPE and the negative-return convention |
| Limits and pricing | Concurrency, disk, formats, billing |
| Changelog | Versions and compatibility |
Most members are fully implemented; members that need a real media renderer, encryption or per-stream routing are not supported and return
ERR_NOT_SUPPORTED = 4instead of silently succeeding. See Error codes for the full list.