Ownership and delivery

A clear boundary at handover.

Æltum defines the checks with you, tests the delivery against saved cases, and hands over a sealed package. After handover, it runs in your environment under your credentials, terms, and data.

● Zero Subscription ● Zero Telemetry ● Zero Hosted Custody

Ask about a delivery Explore solutions

Delivery Architecture One-Way Handover

Build Phase

Frozen Acceptance

Verified against saved acceptance cases and diff records prior to handover.

🔒 Sealed Package

→

Your Hardware

Your Machine

Runs on your laptop or private server. Local keys, zero telemetry.

Delivery boundary

What is delivered, where it runs, and who holds what.

Standalone by design does not remove external limits. It means the delivery boundary is explicit, verifiable, and enforceable.

01 / The Deliverable

Hermetic Package & Runbook

You receive standalone executable code, typed tool definitions, and a comprehensive operations manual. The entire deliverable is tested against frozen acceptance suites before handover, running completely free of any ongoing connection to Æltum infrastructure.

Delivery Invariant Zero Drift · Package is sealed and never mutates without a new verified delivery.

02 / The Runtime

Your Machine, Your Infrastructure

You decide where and how the software runs. Runs directly on your laptop, a private server, or a Kubernetes cluster with zero external telemetry, zero tracking beacons, and zero runtime callbacks to vendor servers.

Runtime Invariant Total Autonomy · Continues executing indefinitely without vendor availability.

03 / The Custody

Your Data, Keys & Secrets

Credentials, API tokens, and execution results remain exclusively on your computer or server. Your environment holds all LLM tokens, database credentials, and research logs. Æltum never sees your keys, and charges $0 in recurring SaaS taxes.

Custody Invariant 100% Client Custody · Local secret vault, zero vendor markup, zero seat fees.

Evidence & records

Different records answer different questions.

A recommendation or delivery should reveal the basis for it. We distinguish between build verification, file package integrity, and runtime operational traces.

Ask about a delivery →

Audit & Records

Three-Tier Architecture

Three Levels of Delivery Records

Level 1 · Pre-Handover Verification

Records whether the exact delivery candidate passed agreed acceptance checks and regression tests before transfer.

Level 2 · Package Integrity

Signed cryptographic hash guarantees delivered files and tool definitions are intact and unaltered in transit.

Level 3 · Runtime Execution Traces

Cryptographic receipts and raw evidence retained locally during execution inside your environment.

Questions

What the boundary does and does not promise.

Clear expectations make the handoff easier to review and operate.

Does the program need Æltum to keep running?

No. The delivered program runs independently of the build system. The APIs, models, data sources, and other external services it uses still have their own availability, credentials, and terms.

Can the delivery be changed later?

Yes, through a new verified delivery. A changed package is a different candidate and carries the verification appropriate to that change.

Do you host it or keep a copy of my data?

No. The package runs where you choose. Credentials and data stay under your control, and nothing phones home.

Who can access an inquiry?

Use the contact page to prepare a draft inquiry. Nothing is sent from this static site unless a connected delivery channel is explicitly provided.