Skip to content

How it works Security Documentation

Menu

How it works Security Documentation Open console

chalupa

Operational signal for ephemeral environments. Compute can be torn down while persistent data follows its own lifecycle.

Product

How it works Security Console

Learn

Quickstart Concepts API and schema

Built for ephemeral operations, not forgotten resources.

All displayed costs are estimates.

Operations manual

From Compose to an observable environment, without losing control.

Guides, contracts, and runbooks to validate, launch, connect, observe, and sink a Chalupa with explicit security boundaries.

Search the documentation

/

13 versioned guides•Bun only•Private services over SSH

Recommended path

Start with the irreversible decisions.

The reading path follows a safe operation: inference first, secrets second, and readiness last.

Validate without touching the cloud

Create chalupa.yml and inspect the complete redacted inference.

Deliver secrets per process

Use tvault allowlists; never copy values to files or logs.

Prepare private operations

Verify readiness, migrations, rollback, and known boundaries.

Start here

Reach a safe first preview and configure secrets.

QuickstartFrom a local Compose file to a connected environment.Secrets with tvaultLeast-privilege injection without files or values in logs.

Operating model

Understand what is ephemeral, what persists, and how access works.

ConceptsThe mental model: inference, compute, and data.chalupa.yml referenceDeclarative fields and a complete example.LifecyclePrepare, launch, observe, and sink.Tunnels and securityPrivate services, local access, and secrets.Data and seedsSeparate persistence and repeatable restores.

Control plane

Interpret signals, costs, suites, and artifacts.

Control plane and agentHow heartbeats reach the control plane.Suites and artifactsResults, comparisons, and evidence references.Costs and idle observationEstimates and the informational inactivity window.

Reference

Operate, diagnose, and consult exact contracts.

Private operationsReadiness, deployment, rollback, and staging boundaries.TroubleshootingSafe diagnosis for the most common failures.API and schemaPublic ingestion and read contracts.