cboxdk/cbox-engine

The engine behind the cbox CLI and the Cbox Local desktop app — one local Kubernetes cluster running an application the way production does.

v0.1.1 2026-08-12 17:41 UTC

Requires

• php: ^8.3
• cboxdk/platform: ^0.11.0
• illuminate/console: ^12.0 || ^13.0
• illuminate/contracts: ^12.0 || ^13.0
• illuminate/http: ^12.0 || ^13.0
• illuminate/support: ^12.0 || ^13.0
• symfony/process: ^7.0 || ^8.0
• symfony/yaml: ^7.0 || ^8.0

Requires (Dev)

• larastan/larastan: ^3.0
• laravel/pint: ^1.18
• orchestra/testbench: ^10.0 || ^11.0
• pestphp/pest: ^3.5 || ^4.0

MIT

• Cbox

• laravel
• platform
• docker
• paas
• kubernetes
• local-development
• developer-experience
• cbox
• scale-to-zero
• gateway-api
• kind
• preview-environments

Published on Packagist.org on 2026-08-12 17:41 UTC

README

The engine behind the cbox CLI and the Cbox Local desktop app: one Kubernetes cluster inside Docker, running an application the way production runs it — same manifest, same cboxdk/platform compiler, same gateway, same proxy headers, same scaling.

It is a library, not a product. Two things consume it:

• cboxdk/cbox-cli — the standalone cbox binary, which is how a person, a server or an agent drives it.
• cboxdk/cbox-local — the desktop app, which is the same engine with a window in front of it.

Neither owns the engine, and that is the point: a command has one implementation and the two front ends cannot drift.

What is in here

src/ is the whole of it — Kind (the cluster), Kubernetes (apply and read), Platform (the capabilities a local target declares to the shared compiler), Project (a cbox.yaml becoming typed intent), plus addons, tunnels, sandboxes and the doctor. src/Console holds the 23 local:* commands.

resources/addons ships the rendered manifests for Gateway API, Envoy Gateway, cert-manager, CloudNativePG and KEDA, pinned to the versions a Cortex cell runs. They ship with the engine rather than with a consumer, because a copy per consumer is a copy that drifts.

Using it

composer require cboxdk/cbox-engine

The provider registers every command and merges config/cbox.php. The cluster's own state lives in ~/.cbox, not in the consuming application — the CLI and the desktop drive one cluster on a machine, and a path relative to whichever is running would give them two.

Verification

composer qa

Pint, PHPStan at level max with larastan, and Pest.