Build. Ship. Run Containers. Powered by Quents Runtime. Docker Compatible.
Launching July 24, 2026 at midnight IST
Docker Migration
Same workflow. More capabilities. Switch in seconds — your existing Docker knowledge transfers completely.
| Docker | Quents |
|---|---|
| docker run | quents run |
| docker pull | quents pull |
| docker ps | quents ps |
| docker compose up | quents compose up |
| docker build | quents build |
| docker push | quents push |
| docker exec | quents exec |
| docker logs | quents logs |
Quents has its own daemon (quentsd) and native C runtime. No dockerd, no containerd, no runc — just direct kernel syscalls.
Your existing docker-compose.yml works out of the box. Point it at Quents and run — zero migration effort.
Pull images from Docker Hub or any OCI registry. Or use Quents' own native registry at registry.quents.dev.
The Quents Ecosystem
Quents is a Docker-compatible container platform built from the ground up — with its own runtime, daemon, registry, and networking layer.
Native Linux container execution engine built in C. Direct syscalls, zero overhead. No runc, no containerd intermediaries.
quents-runtimeBackground management engine (quentsd) that handles container lifecycle, networking state, and system events.
quentsdStore, distribute, and pull Linux images. Public hub or self-hosted private registry — your choice.
registry.quents.devNative container networking with veth pairs, bridge, NAT, and port mapping. Full network namespace isolation.
qnatDefine multi-container applications in YAML. Docker Compose compatible syntax. One command orchestrates everything.
quents composeWeb-based management for containers, images, volumes, logs, and network graphs — no external tool needed.
quents dashboardArchitecture
Quents doesn't wrap Docker or containerd. Every layer is purpose-built — from the Rust CLI down to the native C runtime that talks directly to the Linux kernel.
Your interface to the full ecosystem. Written in Rust.
Background daemon managing container state and events.
Native C runtime — namespaces, cgroups, seccomp.
Direct syscalls. No abstraction layers. No overhead.
Native Runtime
Quents' biggest strength is what it doesn't have — and what it directly owns instead.
What Quents Removes
No Docker Engine — no background dockerd process eating memory
No dockerd — no intermediate process between CLI and containers
No containerd — no secondary daemon required
No runc — no wrapper binary in the execution chain
What Quents Uses Instead
Native Linux APIs — direct kernel interfaces
Kernel Namespaces — PID, mount, net, IPC, UTS, user
cgroups v1 & v2 — hard resource enforcement
OverlayFS — layered container filesystem
Netlink + veth — full network isolation
Core Features
Quents is Docker-compatible and production-grade — built in Rust + C for performance, reliability, and security from day one.
Full PID, mount, network, UTS, IPC, and user namespace isolation — raw syscalls, no wrapper runtimes between you and the kernel.
Memory limits, CPU shares, and PID caps enforced at the kernel level. Containers can't escape their resource boundaries.
Define multi-container apps in YAML. quents compose up orchestrates all services in one shot.
Extend Quents with first-party and community plugins. Install, update, and remove entirely via the CLI.
CLI-First Platform
Quents is CLI-first by design. Over 20 commands covering container lifecycle, networking, registry, compose, and deployment.
Security
Quents was designed with isolation and security at its core — not bolted on afterward.
Kernel-level isolation with namespaces, cgroups and capability controls. Built for production containers from day one.
Every container runs in its own PID, mount, network, and user namespace. Complete isolation from host and sibling containers.
CPU, memory, and PID limits enforced at the kernel level. Containers cannot exceed their allocated resource boundaries.
Docker-compatible seccomp profiles and capability dropping. Rootless mode eliminates the host root attack surface entirely.
All registry images are checksummed and integrity-validated on pull. Signed packages supported out of the box.
Host your own private Quents registry. Full air-gapped deployments supported — your images never leave your network.
Roadmap
Quents ships in phases. Each release expands the platform — from runtime to full cloud infrastructure.
Built For
Whether you're shipping apps, running security labs, or managing cloud workloads — Quents is designed for you.
Build and test applications in isolated Linux environments. Consistent across machines. No "works on my machine" ever again.
Spin up Kali, Parrot, or BlackArch in seconds. Fully isolated pentest labs with zero host contamination.
Deploy container workloads with Quents CLI. Self-hosted or cloud — your infrastructure, your rules, no lock-in.
Isolated, reproducible environments for autonomous AI agent execution. The automation layer for the next generation of AI infrastructure.
Quents Lab
Be the first to run the Quents runtime. Get early access, exclusive updates, and help shape the future of the platform.
No credit card · No obligations · Early access on launch