> For the complete documentation index, see [llms.txt](https://docs.datarhei.com/core/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datarhei.com/core/readme.md).
# About
 [](https://github.com/datarhei/core/actions/workflows/codeql-analysis.yml) [](https://github.com/datarhei/core/actions/workflows/go-tests.yml) [](https://codecov.io/gh/datarhei/core) [](https://goreportcard.com/report/github.com/datarhei/core) [](https://pkg.go.dev/github.com/datarhei/core)
The datarhei Core is a process management solution for FFmpeg that offers a range of interfaces for media content, including HTTP, RTMP, SRT, and storage options. It is optimized for use in virtual environments such as Docker. It has been implemented in various contexts, from small-scale applications like Restreamer to large-scale, multi-instance frameworks spanning multiple locations, such as dedicated servers, cloud instances, and single-board computers. The datarhei Core stands out from traditional media servers by emphasizing FFmpeg and its capabilities rather than focusing on media conversion.
\_\_
## Objectives of development
The objectives of development are:
* Unhindered use of FFmpeg processes
* Portability of FFmpeg, including management across development and production environments
* Scalability of FFmpeg-based applications through the ability to offload processes to additional instances
* Streamlining of media product development by focusing on features and design.
## What issues have been resolved thus far?
### Process management
* Run multiple processes via API
* Unrestricted FFmpeg commands in process configuration.
* Error detection and recovery (e.g., FFmpeg stalls, dumps)
* Referencing for process chaining (pipelines)
* Placeholders for storage, RTMP, and SRT usage (automatic credentials management and URL resolution)
* Logs (access to current stdout/stderr)
* Log history (configurable log history, e.g., for error analysis)
* Resource limitation (max. CPU and MEMORY usage per process)
* Statistics (like FFmpeg progress per input and output, CPU and MEMORY, state, uptime)
* Input verification (like FFprobe)
* Metadata (option to store additional information like a title)
### Media delivery
* Configurable file systems (in-memory, disk-mount, S3)
* HTTP/S, RTMP/S, and SRT services, including Let's Encrypt
* Bandwidth and session limiting for HLS/MPEG DASH sessions (protects restreams from congestion)
* Viewer session API and logging
### Misc
* HTTP REST and GraphQL API
* Swagger documentation
* Metrics incl. Prometheus support (also detects POSIX and cgroups resources)
* Docker images for fast setup of development environments up to the integration of cloud resources
## Quick start
{% content-ref url="/pages/ZbpQnDmXgUkfeffDtHps" %}
[Beginner](/core/guides/beginner.md)
{% endcontent-ref %}
## Changelog
{% embed url="" %}
## Releases
{% embed url="" %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.datarhei.com/core/readme.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.