Sign in
NewsNov 19, 20255 min read

Introducing Guild.ai

James Everingham

    Today, I'm excited to share something we've been building: Guild.ai.

    I've spent my career building tools that help developers build — from Borland C++ to Mozilla to the developer infrastructure supporting thousands of engineers at Meta. One thing has always stayed true: the best systems don't replace people. They bring people together to build.

    When we open-sourced Mozilla, I saw how openness and transparency could turn a codebase into a living community. We learned faster, fixed things faster, and shipped things no single team could have created on its own.

    That lesson stuck. And it's exactly what's driving Guild.ai.

    Why Now

    Building with AI today is powerful but fragile. Everyone is reinventing the same workflows, debugging the same unpredictable behavior, and stitching together the same integrations — alone. The tooling doesn't feel shared. It doesn't feel open.

    Software used to be something you could inspect, understand, and shape with others. Open source made code social. We think AI development is ready for a similar shift — one that lets us share not just code, but the context and intelligence that surround it.

    What We're Building

    Guild.ai is a platform for the next generation of intelligent systems, built for developers who care about craft, reliability, and scale.

    Our mission is simple: make building with AI as open, reliable, and collaborative as open source.

    We're creating tools that let builders move faster, ship with confidence, and learn from one another as they shape what comes next. We believe transparency isn't a nice-to-have — it's the foundation of secure, high-quality systems. And openness isn't ideology — it's how durable software gets built and improved.

    What's Next

    We're just getting started, with much more to share soon. The next era of software won't be built by one company. It'll be built by all of us.

    If you want to help shape what's next, join the early waitlist at Guild.ai.

    FAQs

    Guild.ai is the control plane for AI agents: the governance layer that runs, observes, and controls agents in production, regardless of how they were built. Teams bring agents from any framework, and Guild handles credentials, access scoping, session logging, and cost controls in one place. Guild is not an agent builder; it is the layer that makes the agents you already have safe to run at scale.

    An agent control plane is the infrastructure layer that governs AI agents in production. It manages what each agent can access, injects credentials at runtime so agents never hold keys, records every run in an audit-ready session log, and tracks cost per agent. Frameworks like LangChain or CrewAI are what you build agents with; a control plane is what makes them governable once they ship.

    Most AI tools help you build agents: frameworks, no-code builders, prompt and evaluation tooling. Guild governs agents after they ship, whatever built them. It is framework-neutral by design: credentials are injected at runtime and sessions capture the same events whether an agent uses Guild's SDK, LangChain, CrewAI, or custom code. Builders and Guild are complementary layers, not competitors.

    Guild.ai is built for engineering organizations running AI agents in production. That means platform and security leaders who need visibility, governance, and cost control across every agent in the company, and the engineers who already have agents built with LangChain, CrewAI, Claude Code, or custom code and want to run them safely without rebuilding anything.

    Agents are non-deterministic: what they do emerges at runtime, not from reading the code. Without a record of every run, they are black boxes that cannot be debugged, audited, or trusted. Guild makes every agent run a session: a read-only log of each LLM call, tool invocation, and error, with timestamps. Engineering uses it to debug in minutes; security uses it to answer exactly what an agent touched.

    Guild's developer tools are open source: the TypeScript Agent SDK and CLI are MIT-licensed, so you can build and test agents locally with no cloud dependency. The control plane itself, the governance, observability, and deployment infrastructure, is the commercial product. Open tools to build with, a governed platform to run on.

    One control plane.
    The complete agent lifecycle.
    Get a working agent in under 10 minutes.
    No credit card required.
    Explore docs