Skip to content

Kubernetes for AI Agents. Build and run AI like microservices - scalable, observable, and identity-aware from day one.

License

Notifications You must be signed in to change notification settings

Agent-Field/agentfield

AgentField - Kubernetes, for AI Agents

Kubernetes for AI Agents

Deploy, Scale, Observe, and Prove.

License Downloads Last Commit Go Python Deploy with Docker

πŸ“š Documentation β€’ ⚑ Quick Start β€’ 🧠 Why AgentField


πŸ‘‹ Welcome Early Adopter!

You've discovered AgentField before our official launch. We're currently in private beta, gathering feedback from early users to shape the future of the autonomous software. Feel free to explore and test, and we'd love to hear your thoughts! Share feedback via GitHub Issues or email us at contact@agentfield.ai. Please note that features and APIs are still being refined before our public release.


πŸš€ What is AgentField?

AgentField is "Kubernetes for AI Agents."

It is an open-source Control Plane that treats AI agents as first-class citizens. Instead of building fragile, monolithic scripts, AgentField lets you deploy agents as independent microservices that can discover each other, coordinate complex workflows, and scale infinitelyβ€”all with built-in observability and cryptographic trust.

The "Day 2" Problem

Most frameworks help you prototype (Day 1). AgentField helps you operate (Day 2).

  • How do I debug a loop? (Observability)
  • How do I prove what the agent did? (Verifiable Credentials)
  • How do I scale to 1M+ concurrent runs? (Stateless Architecture)
  • How do I manage IAM for agents ? (Identity)
  • How do I integrate it with my backend/frontend ? (websockets/SSE/webhooks)

Write standard Python (or Go). Get a production-grade distributed system automatically.

from agentfield import Agent, AIConfig

# 1. Define an Agent (It's just a microservice)
app = Agent(
    node_id="researcher",
    ai_config=AIConfig(model="gpt-4o")
)

# 2. Create a Skill (Deterministic code)
@app.skill()
def fetch_url(url: str) -> str:
    return requests.get(url).text

# 3. Create a Reasoner (AI-powered logic)
# This automatically becomes a REST API endpoint: POST /execute/researcher.summarize
@app.reasoner()
async def summarize(url: str) -> dict:
    content = fetch_url(url)
    # Native AI call with structured output
    return await app.ai(f"Summarize this content: {content}")

# 4. Run it
if __name__ == "__main__":
    app.run()

What you get for free:

  • βœ… Instant API: POST /api/v1/execute/researcher.summarize
  • βœ… Durable Execution: Resumes automatically if the server crashes.
  • βœ… Observability: You get a full execution DAG, metrics, and logs automatically.
  • βœ… Audit: Every step produces a cryptographically signed Verifiable Credential.

πŸš€ Quick Start in 60 Seconds

1. Install

curl -fsSL https://agentfield.ai/install.sh | bash

2. Initialize

af init my-agent --defaults && cd my-agent

3. Run

af run

4. Call

curl -X POST http://localhost:8080/api/v1/execute/researcher.summarize \
  -H "Content-Type: application/json" \
  -d '{"input": {"url": "https://example.com"}}'
🐳 Docker / Troubleshooting

If you are running AgentField in Docker, you may need to set a callback URL so the Control Plane can reach your agent:

export AGENT_CALLBACK_URL="http://host.docker.internal:8001"

🎨 See It In Action

AgentField Dashboard
Real-time Observability β€’ Execution DAGs β€’ Verifiable Credentials

🧠 Why AgentField?

Software is starting to behave less like scripts and more like reasoning systems. Once agents act across APIs, data layers, and critical paths, they need infrastructure: identity, routing, retries, observability, policies. We built AgentField because agents should behave as predictably as microservices.

From Prototype to Production

Most frameworks (LangChain, CrewAI) are great for prototyping. But when you move to production, you hit walls: Non-deterministic execution times, Multi-agent coordination, and Compliance.

AgentField isn't a framework you extend. It's infrastructure that solves these problems out of the box.

Capability Traditional Frameworks AgentField (Infrastructure)
Architecture Monolithic application Distributed Microservices
Team Model Single team, single repo Independent teams & deployments
Integration Custom SDK per language Standard REST/gRPC APIs
Coordination Manual message passing Service Discovery & Auto-DAGs
Memory Configure vector stores manually Zero-config Scoped Memory & Vector Search
Async Roll your own queues Durable Queues, Webhooks, Retries
Trust "Trust me" logs DIDs & Verifiable Credentials

🎯 Who is this for?

  • Backend Engineers shipping AI into production who want standard APIs, not magic.
  • Platform Teams who don't want to build another homegrown orchestrator.
  • Enterprise Teams in regulated industries (Finance, Health) needing audit trails.
  • Frontend Developers who just want to fetch() an agent without Python headaches.

πŸ’Ž Key Features

🧩 Scale Infrastructure

  • Control Plane: Stateless Go service that handles routing and state.
  • Async by Default: Fire-and-forget or wait for results. Handles long-running tasks (hours/days) with Webhooks.
  • Shared Memory Fabric: Built-in, scoped memory (Workflow/Session/User) with Vector Search out of the box. No Redis/Pinecone required.

πŸ›‘οΈ Identity & Trust

  • W3C DIDs: Every agent has a cryptographic identity.
  • Verifiable Credentials: Prove exactly what the AI did.
  • Policy: "Only agents signed by 'Finance' can access this tool."

πŸ”­ Observability

  • DAG Visualization: See the logic flow in real-time.
  • Metrics: Prometheus endpoints at /metrics.
  • Logs: Structured, correlated logs.

πŸ”Œ Interoperability

Call your agents from anywhere. No SDK required.

Frontend (React/Next.js):

const response = await fetch("http://localhost:8080/api/v1/execute/researcher.summarize", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ input: { url: "https://example.com" } }),
});
const result = await response.json();

πŸ—οΈ Architecture

AgentField Architecture Diagram

βš–οΈ Is AgentField for you?

βœ… YES if:

  • You are building multi-agent systems.
  • You need independent deployment (multiple teams).
  • You need compliance/audit trails.
  • You want production infrastructure (Queues, Retries, APIs).
  • You want to use MCP tools without hassle.

❌ NO if:

  • You are building a single-agent chatbot.
  • You are just prototyping and don't care about scale yet.

🀝 Community

Agents are becoming part of production backends. They need identity, governance, and infrastructure. That’s why AgentField exists.

Built by developers who got tired of duct-taping agents together.
🌐 Website