Architecture
Open the scalable SVG version.
Idelium is designed as a separated administration, API, execution, and data platform. The Docker stack keeps the public surface small: users and execution agents enter through the HTTPS frontend, while API and database services remain inside the Docker network.
| Layer | Component | Responsibility |
|---|---|---|
| User and automation access | Browser, Idelium CLI, CI systems | Configure tests, launch cycles, and submit execution results |
| Edge | ideliumfe |
Serves the Vue application, terminates HTTPS, and reverse-proxies API traffic |
| Application | ideliumapi |
Authenticates users and API keys, manages projects, tests, cycles, and results |
| Initialization | ideliuminit |
Runs migrations and explicitly enabled seeders before API startup |
| Data | ideliumdb |
Stores tenant-owned application data in MariaDB |
| Execution providers | Selenium Grid, Appium, Postman targets, plugins | Execute browser, mobile, API, or custom test steps |
- A user opens Idelium Web through
https://localhostor the configured production origin. - Idelium Web calls the API through the frontend reverse proxy.
- Idelium API validates authentication, authorization, and tenant ownership before reading or writing data.
- Idelium CLI retrieves project, cycle, environment, and step definitions from the API using a customer API key.
- The CLI executes the selected Selenium, Appium, Postman, or plugin steps.
- Execution results are reported back to Idelium API and stored in MariaDB.
- Only the HTTPS frontend should be exposed to users.
- The API and database remain internal Docker services.
- Secrets are mounted as files or supplied by the runtime secret provider.
- Demo mode uses generated local secrets; production mode requires managed secrets and a trusted TLS certificate.
- Health checks gate startup order so the frontend is not reported ready before the database, initialization, and API are healthy.
For enterprise use, place the Docker stack behind the organization's network controls, use a trusted certificate chain, rotate secret files through a managed process, and keep API/Web/stack image references tied to reviewed source revisions. Execution hosts should be isolated by tenant or environment where required, and logs must redact credentials, API keys, session identifiers, and authorization headers.