Skip to content

a8s

Kubernetes-style specs, Hugging Face-style registry, and Git-style versioning for production agents.

Core trick

Stores agent specs as versioned declarative manifests with a registry and deployment mappings that point to external runtimes.

Tags

Description

Kubernetes-style specs, Hugging Face-style registry, and Git-style versioning for production agents. agent8s is a vendor-agnostic agent control plane for defining, versioning, deploying, and observing agents across external runtimes. Agents are moving from demos into real production workflows: orchestrators, specialist subagents, automation agents, support agents, internal tooling agents, and workflow agents. But most teams still manage them like scattered implementation details — prompts in code, model configs in framework files, runtime status in vendor dashboards, and history reconstructed manually from Git diffs. That is fine for a prototype. It breaks down once agents become part of critical systems. Production agents need the same discipline we expect from services and models: * A declarative spec for what the agent is * A registry for discovering which agents exist * Version history for prompts, models, tools, context, and runtime configuration * Clear who/what/when/why metadata for every change * Deployment mappings to external runtimes like Vercel, Bedrock AgentCore, LangGraph, or internal platforms * Status and run visibility without owning the runtime itself

The linked repo returns 404, so it was deleted or made private.

Team