The network-interactive container control API.
Ignite Containers
Ignite Containers is an API-first control API for containerised networks on Kubernetes and Docker. Two services do the work: the control plane for central management and the node agent for execution on the nodes.
- Network-interactive control API
- Control plane and node agent
- Kubernetes and Docker
- Port allocations for exposure
- Containerised networks
- Admin Center and simplified desktop UI
- Scoped API keys instead of user accounts
Overview
Built for providers and platforms that want to automate containerised workloads. Ignite Containers handles networking, ports, templates and lifecycle; customers, invoices and pricing stay in the external system.
- Services
- Control plane, node agent
- Runtime
- Kubernetes, Docker
- Network
- Port allocations, bind IPs, TCP/UDP
- Tenants
- API keys with server allow-list
- Admin
- Admin Center, simplified desktop UI
- API
- OpenAPI 3, Swagger UI
- Clients
- Rust, TypeScript, PHP
Details
Network-interactive API
Every capability is available over HTTP. Containers, networks, ports and exposures are controlled through an API; the admin UI is a thin client. OpenAPI 3, Swagger UI and a raw API escape hatch in the clients are included.
Containerised networks
Ignite Containers creates and manages containerised networks on Kubernetes and Docker. The desired state is stored in PostgreSQL. Agents on the nodes regularly check whether containers and networks match it and correct deviations.
Ports and exposure
Ports are created per node in bulk and claimed atomically with FOR UPDATE SKIP LOCKED. Primary and additional ports, TCP/UDP, dedicated bind IPs and separate listeners for API, admin UI and public ports are supported.
Kubernetes and Docker
Docker is the production focus; Kubernetes is supported. Workloads run in separate environments. Rootless Docker and Sockguard reduce the attack surface.
Templates and Pterodactyl eggs
PTDL_v1 and PTDL_v2 import, semver-versioned templates, canonical digests, optional Ed25519 signatures and signed auto-update feeds. Pterodactyl eggs remain available as a compatibility path for game hosting.
Security
Scoped API keys, HMAC-signed agent communication with nonce and timestamp checks, argv-first startup, path sandboxing, hard container limits, rootless Docker and Sockguard with default deny.
Admin Center and desktop UI
The Admin Center brings together keys, nodes, templates, containers, backups, schedules and Caddy. A simplified desktop UI adds a local interface with a live console. Rust, TypeScript and PHP clients plus OpenAPI and Swagger UI are included.
Status
Docker is the production focus. Kubernetes is supported; the file manager and backups currently run on Docker. Server transfer and live migration are on the roadmap.
Services
Two services, clear roles.
The control plane manages centrally; the node agent executes on the nodes.
ignite-containers-api
Control plane
Accepts API requests, verifies API keys and scopes, manages ports, templates and containers and writes audit events. The API stores the desired state.
ignite-containers-agent
Node agent
Runs on every node, creates, starts and stops containers, streams console, logs and stats and reports the actual state back. If a node deviates, the agent corrects it.
Technical status
Ignite Containers is not a billing system. It connects to Ignite or your own panel. The API stores the desired state. Agents on the nodes regularly check whether the containers actually run that way and correct deviations.
Request Ignite Containers.
Talk to us about nodes, templates and connecting the control API to your panel.