# a8s

- **Event:** [Claude Build Day](https://cerebralvalley.ai/e/claude-startups-build-day)
- **When:** Sat, Jun 13 at 9:00 AM – 10:00 PM (PDT)
- **Where:** San Francisco, CA
- **Team:** [Christine Baek](https://cerebralvalley.ai/u/cbaek)
- **GitHub:** https://github.com/viirii/agent8s
- **Demo video:** https://youtu.be/uewJ9V7NXnQ
- **Gallery:** https://cerebralvalley.ai/e/claude-startups-build-day/hackathon/gallery
- **Page:** https://cerebralvalley.ai/e/claude-startups-build-day/hackathon/gallery/96

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

---

Markdown version of https://cerebralvalley.ai/e/claude-startups-build-day/hackathon/gallery/96. Site index for agents: https://cerebralvalley.ai/llms.txt · full text: https://cerebralvalley.ai/llms-full.txt