Skip to content
behold

Run it in five minutes

Both demos below need Docker and nothing else. No cloud account, no credentials, no cost. Each ends with a resource changing colour while you watch, which is the thing worth seeing.

The AWS demo: your first apply

Section titled “The AWS demo: your first apply”

One S3 bucket, deployed to a local Floci emulator through the CloudFormation API.

  1. Start it:

    Terminal window
    git clone https://github.com/INTENTIUS/behold && cd behold
    npm install
    npm run demo

    That installs the bundled example-writes project’s dependencies, boots its emulator, and serves it at http://localhost:4600.

    No checkout? npx @intentius/behold demo runs the same demo from npm, copying the example project to ./behold-demo (yours to edit).

  2. Look at the graph. The bucket and its TLS policy are blue: declared in source, not yet deployed.

  3. Click ▶ Deploy (floci-apply) on the floating control panel’s Deploy tab. The now-line streams Build → Apply → Verify as the bucket is created in the emulator.

  4. The nodes flip green. behold observed the live emulator and found them.

That is the whole loop: declared → applied → observed. Nothing was mocked, and behold did not do the applying. It triggered an Op the project committed.

The Kubernetes demo, and three things only k8s can show

Section titled “The Kubernetes demo, and three things only k8s can show”
Terminal window
npm run demo:k8s

Brings up a single-node k3d cluster, serves an nginx Deployment + Service, and tears the cluster back down on Ctrl-C. Same blue → ▶ Deploy → green loop, applied server-side with chant’s own field manager.

Then three things that exist on no other substrate:

Runtime children. Zoom into the Deployment and its Pods appear, owned by the cluster through ownerReferences and never declared. “Deployment exists” tells an operator almost nothing; a crashlooping Pod tells them everything.

Field-level ownership. Run kubectl scale or kubectl label out of band, refresh, and see which fields chant’s field manager owns versus the one that just wrote. Foreign-owned reads differently from drifted, because a field the HPA legitimately owns is not a problem.

An honest refusal. Switch away from the bound kubectl context and behold reports unobserved, which means “I did not look” rather than “all gone”.

Then what

Section titled “Then what”