TULPAR

Docker Pod Management

Your Containers, in Plain Sight

Manage the containers running your cluster services from one screen: lifecycle, live logs, instant metrics and compose visibility — no SSH required.

Real-time

Log streams and container metrics arrive live over WebSocket — no page refresh.

Secure access

Not the raw Docker socket: a read-only socket-proxy bridge exposes only the required API.

TULPAR / Docker Pod Management
Docker Pod Management
Current TULPAR interface in Turkish · Sample test data

What's Inside

Container Operations from Lifecycle to Metrics

Every container running the panel stack and services is managed from one list.

01

Container List

All containers in one list with state, image and resource summary; one click to drill into details.

02

Lifecycle Control

Start, stop and restart from the panel — asynchronous, so the UI never blocks.

03

Live Log Streaming

Watch container logs in real time with an xterm.js-based terminal experience.

04

Instant Metrics

CPU, memory and network metrics refresh every 2 seconds over WebSocket.

05

Inspect & Details

Container inspect output, environment and mount information rendered readably in the panel.

06

Compose View

View the docker-compose.yml from the panel — the stack's source is always at hand.

TULPAR / Docker Pod Management

A Safe Window into the Stack's Heart

TULPAR itself runs on Docker — the panel manages its own stack with the same rigor.

Socket-proxy security
The backend never connects to the Docker socket directly; a read-only socket-proxy bridge exposes only the required API endpoints.
Live WebSocket streams
Logs and metrics stream over WebSocket rather than polling; if a firewall interferes, it falls back to HTTP polling automatically.
Service inventory
Redis, PostgreSQL, Prometheus, VictoriaLogs — the health of every service in the stack at a glance.
Asynchronous operations
Lifecycle commands run as asynchronous tasks; long operations never hold the panel up.
Docker Pod Management
A Safe Window into the Stack's Heart
Current TULPAR interface in Turkish · Sample test data

GOOD TO KNOW

Frequently Asked Questions

Got questions? Everything you need to know about installation, licensing and scaling is here.

How is TULPAR licensed?
TULPAR is an enterprise product offered under a commercial license. Licensing is annual, based on your cluster scale and the support coverage you need; every license includes the full feature set — there is no feature gating. Contact us through the contact page for a quote.
How long does installation take and what do I need?
An EL9-based head server is enough. tulpar-preflight.sh prepares the prerequisites, install.sh brings up the whole stack; you then enter the admin password, NTP, LDAP and SLURM settings in the web wizard. A typical installation completes in minutes.
Does it work with my existing Slurm cluster?
TULPAR talks to Slurm over the slurmrestd REST API and falls back to the CLI automatically, providing a stable, version-independent interface. Head Slurm components run natively on the host (dnf/systemd) and share the same repository and version as the compute nodes.
Can it be installed in an air-gapped environment without internet access?
Yes. RPM repositories travel with the product, the Slurm package repository can be imported as a GPG-signed offline bundle, and container images are loaded with docker load. Every component works on a closed network, including node installation, monitoring and central logging.

READY FOR YOUR NEXT COMPUTATION

Unleash your
infrastructure’s potential.

Let’s explore what TULPAR can do for your cluster.

Request a demo