---
title: "How does the Tale platform work?"
description: "Tale connects agents, pools knowledge, runs automations, and governs every action — self-hosted for data-sensitive teams in Switzerland and the EU."
---
# How does the Tale platform work?

Tale is the orchestrator for AI agents: one place where your agents share knowledge, run automations, and answer to the same approvals — self-hosted, on your terms.

> Animated product demo: a platform overview question is typed into Tale, Auto routes it to the Orchestrator Agent, and the reply names the modules that answer it with two cited sources.

## How the platform fits together

Every window below is one module telling its own story — ground it in Knowledge, run it through Automations, hold it at Governance, compare it in Arena. Open any module for the full tour.

01 Agents

### Every agent, one roster

Claude Code, Codex, Hermes, OpenClaw — docked beside in-product agents so work routes to the tool your team already runs.

> Animated demo: the hub Agents sampler — Orchestrator Agent, Support Agent, Docs Agent, Invoice Agent, and Policy Agent, each with its model.

02 Knowledge

### One library, cited everywhere

The product manual, the docs crawl, the price list, an FAQ entry — one indexed library every agent cites.

> Animated demo: the hub Knowledge sampler indexes the platform overview, the module map, the trust center crawl, and an onboarding FAQ.

03 Automations

### Delegate multi-step work

An invoice pipeline extracts line items, holds anything over CHF 5,000, and files the rest to the ERP — every run logged.

> Animated demo: a hub sampler workflow digests overnight module activity, checks for open approvals, and posts a morning brief to Slack.

04 Governance

### Held until someone decides

Even a knowledge write waits for a person. Approve, and the decision lands in the audit log with the budget in view.

> Animated demo: the hub sampler holds a cross-module publish until a person approves; the journal records the decision.

05 Arena

### Two drafts, one brief

One announcement brief, two models side by side — the stronger draft ships.

> Animated demo: the hub Arena sampler compares two module-overview drafts so the stronger intro ships on the platform page.

06 Projects

### Scope by team

Every window above ran inside one workspace. Projects decide which agents, libraries, and members sit together — and who sees the runs.

> Animated demo: hub Projects sampler — Platform core, Customer pilots, Partner enablement, and Internal ops, each with its own roster.

## Platform modules

Chat, Projects, Knowledge, Agents, Automations, and Governance — each is useful alone; together they make one governed system. Open a module for its own tour.

- [ChatsEveryday AI with citations, tools, and Arena.](https://tale.dev/platform/chat)
- [ProjectsShared workspaces where agents pick up tasks.](https://tale.dev/platform/projects)
- [KnowledgeDocuments, websites, and records agents cite.](https://tale.dev/platform/knowledge)
- [AgentsOrchestrate Claude Code, Codex, Hermes, and OpenClaw.](https://tale.dev/platform/agents)
- [AutomationsTyped workflows with triggers and approvals.](https://tale.dev/platform/automations)
- [GovernanceApprovals, audit trail, and spend controls.](https://tale.dev/platform/governance)

## Platform FAQ

### What is the platform in Tale?

### Which modules does Tale include?

### Is Tale open source?

### Where should I start?

## See Tale on your stack

Book a guided demo or talk to the team about self-hosted deployment, pricing, and hardware.