Mental model in 5 minutes

Guilde is an AI company in a box. Hire operators, give them work, they run.

The product looks dense at first — sidebars, tabs, settings pages, integrations. The model under it is small. Five pillars cover every concept you'll meet.

The pitch

You don't manage agents one prompt at a time. You hire operators — AI workers with a job (Marketing Strategist, SDR, Engineer, Support Agent). They hold context, follow instructions, use real tools, and keep working when you're not watching.

Humans collaborate alongside operators in the same guild (your AI company). Members chat with operators, review their work, and approve the things that matter.

The 5 pillars

Everything in Guilde is one of these five.

1. People & roles

Humans and operators, both first-class. Operators have roles — like real employees — and you hire, retrain, or let them go. Members (humans) have access roles too: owner, admin, editor, viewer.

→ See Operators and Members.

2. Work

How operators are given things to do.

• Conversations — threaded chats, ad-hoc.
• Work items — tracked deliverables: objectives, initiatives, tasks. Same hierarchy a real company's roadmap has.
• Routines — scheduled jobs (a daily standup, a weekly support digest).

→ See Conversations.

3. Files & artifacts

Where operators read and write.

• Workspaces — file storage backends (local FS, GCS, S3, GitHub). Yes, the word workspace means storage here, not the AI company. The AI company is a guild.
• Artifacts — outputs operators produce.
• Canvases — visual deliverables (briefs, decks, plans).

→ See Workspaces.

4. Capability

What operators can actually do.

• Connectors — third-party SaaS integrations (HubSpot, Stripe, Google).
• MCP servers — tool catalogs over the Model Context Protocol.
• Skills — installable bundles of capability.

These three look similar. They're not. See the Capability overview for the disambiguation.

5. Reach

How operators show up outside the Guilde app.

• Channels — Discord, Slack, Telegram. Operators reply where your team already works.
• API keys — programmatic access for your own code.

→ See Channels.

Glossary — the words that look the same but aren't

Workspace vs Guild — a guild is your AI company. A workspace is the file storage backend operators read and write to. Different things.

Operator vs Agent — operators have a job (a role in your company). Every operator is implemented as an agent under the hood. You'll see "agent" in code, "operator" in the UI.

Connector vs MCP vs Skill — a connector is one third-party integration. An MCP server is a catalog of tools over a standard protocol. A skill bundles capabilities into a named installable unit. Skills are recipes; connectors and MCP are ingredients.

Routine vs Work item — a routine runs on a schedule. A work item is a specific tracked thing. Routines often produce work items.

Now, hire your first operator →

The fastest path: Quickstart walks you from sign-up to your first operator reply in about a minute.