Skip to main content
LightForgeAEGIS
Menu
Drawing set · a hybrid engineering team

Your agents, side by side, on your machine.

AEGIS Connect: the hybrid agentic development environment.

AEGIS is accepting beta customers. Talk to us to find out how to deploy governed agent teams in your org.

Sign in
Illustrative diagram, not a screenshot: two agent sessions, one Claude Code and one Codex, running next to each other on a developer’s machine.

Run them side by side.

Connect runs Claude Code and Codex side by side on your machine. AEGIS also runs agents on open-source models, served through vLLM or OpenRouter.

Illustrative plan, not a screenshot: one developer’s machine with two local runtimes, Claude Code and Codex, working on the same repo.

Connect runs agents in a sandbox.

Agents that Connect launches work inside a sandbox on your machine. The sandbox decides what they can read, write and reach.

Illustrative plan: an agent that Connect launches works inside a sandbox on your machine. System files are read-only and the workspace is writable. Network access is denied by default: the AEGIS SDK reaches AEGIS, and the agent tool reaches its model provider.

  • Files

    The agent runs as an unprivileged user. System directories are read-only, and writes stay in the sandbox workspace.

  • Network

    Network access is denied by default and allowed per program: only the AEGIS SDK reaches the AEGIS API, and only the agent tools reach their model providers.

  • Provider keys

    For AEGIS’s own agent engine, the provider key is never written into the agent bundle or its environment. It arrives for each session over an authenticated, audited channel.

  • Signed policy

    Governance policy is signed by AEGIS. The sandbox holds only the public key. It can verify a policy, but it cannot create one that another runtime would accept.

  • Readiness

    A runtime is marked ready only after it sends a signed description of its sandbox that passes AEGIS’s checks. Editing its governance files after startup marks it not ready.

  • Tool calls

    AEGIS’s own agent engine checks each tool call against policy before it runs, and blocks the call if the check cannot complete.

Bring them onto the team.

Local agents join the same team as your cloud agents.

Illustrative drawing: the people and the cloud agents already sit at the team table. The Claude Code and Codex agents on a developer’s machine join it through AEGIS Connect and take the empty seats; then a cloud agent hands work to a local agent, and a local agent reports to Maya, at the same table.

AEGIS is accepting beta customers.

Talk to us to find out how to deploy governed agent teams in your org.

Talk to us

Tell us about your team and we’ll reply by email.

Team size (choose one)
How can we help? (choose any)

Thanks. Your message is on its way.

We’ll reply to .