Laptop or phone
Control it from anywhere
Open the same command center wherever you are. Watch work unfold, steer a session, approve an outward action, or stop it instantly.
The governed home for your agent swarm
KernYour cloud agent swarm. Always working. Always within bounds.
Run Codex, Claude Code, and open-model agents in parallel on one persistent cloud host. Give them real tools, durable work, and a security boundary you control.
- Many agentsone homeParallel sessions work with shared memory and context.
- Many jobsalways onScheduled and long-running work continues after you close the lid.
- One policyhard boundaryEvery agent and tool works through the same governed perimeter.
Deploy your own$git clone infiloop2/kern
Kern governed boundary5 agents0 policy escapes
Codexbuildingrunning
Claude Coderesearchingrunning
Codextestingrunning
Claude Codeadvertisingready
Hermesscheduled postscheduled
Operate your swarm from anywhere
Manage the work, not the terminals
One calm place to direct every agent. Use it on your laptop when you are deep in the work, or on your phone when you are not.
Conversation when useful
Chat with any agent
Drop into a session when judgment is needed, then leave the agent working without keeping a terminal or yourself attached.
Interfaces that evolve
Work through rich apps
Let agents turn recurring work into durable, purpose-built interfaces, so you interact with outcomes instead of rereading a transcript.
Governed internet access
One boundary around your entire swarm
Give every agent useful internet access without giving any of them a side door. Firewall enforcement, provider-aware guards, approvals, and audit logs share one host boundary.
01
No direct path
Kernel firewall
Every agent reaches the internet through the same fail-closed proxy. If the proxy is unavailable, connectivity stops.
02
Every request
Audit ledger
Allowed and denied network activity is recorded with the rule that made the decision.
03
Host injected
Credentials stay outside
The host adds provider credentials in transit, so reusable secrets never need to live with an agent.
04
Reviewable
Controlled access
Account-aware guards constrain integrations, and consequential writes can pause for your approval.
network policy
gmail.read_inboxauto approval
gmail.send_emailheld for approval
x.create_postheld for approval
instagram.publish_reelheld for approval
polymarket.read_marketsauto approval
ibkr.read_portfolioauto approval
Choose your trust boundary
Two ways to run Kern
Kern is live today: deploy it yourself from source or have it fully hosted on Kern Cloud. Either way, the boundary is yours.
Full self hosting
Deploy from source to your own AWS account and access via your own Cloudflare domain. Your data and keys never live on someone else's platform.
- Runs in your AWS account, and access through your own configured domain
- You run deploys, upgrades and manage all configuration
- Completely free, pay your own infra and AI bills
- Community support
Hosted on Kern Cloud
We provide all the infrastructure and run Kern for you on Kern Cloud, with integrated billing.
- One click, nothing to install or manage, runs on Kern Cloud
- Access through a personal domain configured for you
- Integrated billing for infra, pay your own AI provider
- Support included
Questions
Frequently asked questions
Real work with real accounts: read and send email, manage your calendar, search the web, write code against your repositories, and post to social accounts as tools land. Apps turn that into outcomes: builders, social media managers, shorts studios, and research desks, with more on the way. Sensitive actions always wait for your approval.
Codex, Claude Code, and Hermes today. Bring the accounts you already have, or run open-source models under the same host contract. Kern is a host, not a harness: it does not replace your agent, it runs it.
On an EC2 instance in AWS. Deploy it from source in your own account, or run it one-click on Kern Cloud.
Yes. The complete host is developed in the open at github.com/infiloop2/kern under the Business Source License 1.1. You can read every line that enforces the boundary, audit it, and self-host it.
Three fail-closed layers. The kernel firewall gives the agent no direct network path. The policy proxy checks every request against your rules before DNS resolution. Provider guards pin traffic to accounts you approved, so even a stolen key is not a way out.
Only after you approve them. Sensitive actions hold in a queue with the exact payload disclosed: the recipient, the subject, the repository, the event. The agent keeps working on everything else while decisions wait for you. Approval is a queue, not a modal.
Self-hosting is free forever: you pay only your own AWS, AI subscription, and tool API bills. One-click Kern Cloud folds infrastructure, AI, and tools into a single integrated bill.