Idelium is designed for organizations that need control over data, network boundaries and execution hosts without giving up a shared testing platform.
Control plane in your network
The Docker stack exposes the web frontend while keeping API and database services isolated behind the reverse proxy.
- HTTPS frontend as the public entry point.
- API and MariaDB isolated inside the Docker network.
- Initialization and migrations handled by the stack.
Execution remains flexible
CLI agents can run outside the web stack, which makes it easier to reach internal browsers, devices, test data and private APIs.
- Separate execution hosts.
- CI/CD runner integration.
- No vendor lock-in for runtime infrastructure.
Implementation steps
- Map the runtime boundaryDefine the public frontend URL, internal API endpoint, MariaDB persistence path and the network segment where execution hosts can reach browsers, devices and private APIs.
- Bootstrap the platform servicesStart the Web, API, database and initialization container, then verify migrations, health checks and reverse-proxy routing before opening the platform to users.
- Register execution capacityInstall Idelium CLI on CI runners or isolated hosts, bind it to the self-hosted API and validate that each runner can reach the systems it is expected to test.
Common questions
- Is Idelium free to self-host?
- Yes. Idelium is positioned as an open-source and free-to-use project.
- Can I keep test data inside my network?
- Yes. The platform and execution agents are meant to run inside infrastructure you control.