No description
This repository has been archived on 2026-10-05. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
kayg 6d38283ea7 Link each step to its Forgejo issue
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-21 22:43:51 +05:30
docs Link each step to its Forgejo issue 2026-09-21 22:43:51 +05:30
scripts Add dev VM provisioning and record where work runs 2026-09-21 20:28:17 +05:30
.gitignore Start infraternal: decisions, design, plan and operating contract 2026-09-21 20:05:01 +05:30
AGENTS.md Start infraternal: decisions, design, plan and operating contract 2026-09-21 20:05:01 +05:30
CLAUDE.md Jobs track their own Forgejo issues over HTTPS; performance rule 2026-09-21 22:43:36 +05:30
DECISIONS.md Plan the first usable slice as numbered steps; add UI spec 2026-09-21 22:40:47 +05:30
LICENSE Start infraternal: decisions, design, plan and operating contract 2026-09-21 20:05:01 +05:30
README.md Start infraternal: decisions, design, plan and operating contract 2026-09-21 20:05:01 +05:30

infraternal

One place to run your containers and reach your hosts, for people and for AI agents.

infraternal manages Docker and Podman containers and gives you a fast terminal to any host over SSH, from the browser, the command line, or an AI agent through MCP. Kubernetes and LXC are next.

Status: early design. Nothing to install yet. See DECISIONS.md for what is settled and docs/PLAN.md for what is being built first.

What it does

  • Containers: see every container across your hosts, live. Start, stop, restart, stream logs, open a shell.
  • SSH plane: a host inventory and a terminal built for speed. Sessions survive a closed tab or a dropped connection.
  • Many hosts, no open ports: a small infraternal agent on each host or network connects out to your server.
  • Built for AI agents: everything in the web UI is also in the CLI and the MCP server, with scoped tokens, dry runs and an audit trail.
  • Your login: passkeys, or single sign-on with your OpenID Connect provider.
  • Self-host it as one binary, or use the hosted service.

License

AGPL-3.0. All of it.