Ownership & Network

Ownership: why Agentlas doesn't host your agents

Agentlas is built on one rule: the agent, its memory, and the keys it uses are yours, not ours. That shapes how the desktop app is built, not just how it's marketed.

Bring your own model (BYOM)

Agentlas does not relay or host model calls. It detects the AI accounts and API keys you already have — Claude, Codex, Gemini, and others — and runs your agents through those, on your own usage and billing. There is no separate per-token markup for model usage; the meter you already pay is the only one that runs.

Where your data actually lives

Agent state

Stored locally, not on an Agentlas server, so it moves with your machine.

API keys

Settings-saved keys live in your OS keychain. Imported .env / CLI credential files may remain local files under your control.

Portability

An agent is a package of files (instructions, skills, memory contract) you can move between runtimes — it isn't locked into one vendor's hosted format.

Why this matters

Most AI agent products keep your agent's memory, configuration, and execution inside their own hosted runtime — cancel the subscription and you lose the agent. Agentlas's local-first design means the files, memory, and credentials stay under your control even if you stop using the web app.

NOTE · What this doesn't mean

Agentlas Desktop itself is closed-source (distributed as a built app). What's open is the engine underneath it, Hephaestus (Apache-2.0, public on GitHub) — see the Agent OS page for what that covers.