Overview

Nakama is an open-source platform for building teams of AI agents.

Every agent has a role. Together, they're your nakama.

The easiest way to think about it:

• One Nakama server can host many organizations
• Each organization can have many members
• Each organization can have many profiles
• Each profile is a bot with its own behavior, memory, and tool access

Core mental model

If you are using Nakama, most of the product can be understood through these four ideas.

1. Organization

An organization is the main boundary in Nakama.

It keeps one team's data separate from another team's data, including:

• Members
• Profiles
• Sessions
• Tools
• Skills
• MCP servers
• Usage data
• Org memory — shared facts for the whole organization

2. Profile

A profile is an agent on your team — the bot users talk to.

Each profile has a role. It defines:

• The bot's identity
• The bot's instructions
• Which model it uses
• Which tools it may call
• Which knowledge base it can search

If two profiles should behave differently, make two profiles.

Org memory holds team-wide facts every profile shares; profile MEMORY.md holds per-bot continuity. See Org memory and Profiles.

3. Tool access

Profiles do not automatically get every capability.

You choose which tools a profile can use, such as:

• Web search and web fetch
• File access and Word document generation (write_docx)
• Knowledge base search
• Email
• Skill creation
• Sub-agent delegation (sub_agent, opt-in)

Bundled skills extend profiles with system workflows such as memory writes (update-profile-memory), memory archives (archive-profile-memory), artifact saves (save-artifact), automations (create-automation), skill authoring (manage-skills — see Self-improving skills), the coding agent (coding-agent skill), and interactive browsing (agent-browser skill). External SaaS apps connect through Composio. See Skills, Coding agent, Agent browser, and Builtin tools.

This is how you keep one bot safe and narrow while another bot can be more capable.

4. Channels

The same Nakama profile can be used from different places:

• Web dashboard
• CLI
• Telegram
• WhatsApp
• Discord

How to run Nakama

Nakama can run:

• As a live demo — sign in with demo@getnakama.cloud / demo1234 to explore without installing
• On managed hosting — sign up, create an instance, and open your dedicated URL (for example acme.getnakama.cloud)
• Locally with Bun for development
• In Docker on your own infrastructure

See Quickstart for setup steps.

Typical setup

Most deployments follow this pattern:

1. Create the first organization
2. Add members
3. Create one or more profiles
4. Assign tools to each profile
5. Upload knowledge base documents if needed
6. Let users chat with the right profile

Who Nakama is for

Nakama is a good fit when you want:

• A team of AI agents, not a single general-purpose assistant
• Each agent with a distinct role, tools, and behavior
• Your own open-source agent platform — self-hosted or on managed hosting
• Team or tenant separation across organizations
• Web and messaging channels on top of one backend

It is less about writing one prompt and more about assembling and operating your nakama.

Next steps

• Multi-tenancy — org model, members, and roles
• Profiles — how each bot is defined
• Builtin tools — what profiles can do
• MCP servers — extend profiles with external tools