Your own AI agent — chat, agent, memory, and Workspace, on a server you own. Log in and follow the guided setup.
AI is becoming everyday infrastructure. So it is strange that who you talked to and what you taught it keeps piling up on someone else’s server. Takos keeps chat, agent, and memory inside a server you own.
Conversations, memory, and files all sit inside your own VM or cloud. Nothing piles up on a vendor’s servers, and you can export everything and move to another environment anytime.
Tied to neither a SaaS nor a black-box vendor stack. The distribution worker is provisioned as an OpenTofu module; the official target today is Cloudflare. Conversations, memory, and state stay on your origin, and Git plus Backup let you move to another host or environment.
AGPL, with all code public. Fork it for your needs — add features or remove them. You are never boxed into a black-box “as offered” scope.
Chat to talk, agents to act, memory that accumulates, and a Workspace that ties it together. They become your own AI environment only when they mesh — not as standalone features.
Many models, one thread.
Use cloud LLMs and local models, switching between them in the same conversation. Threads are organized inside a Workspace, and all history stays on your own server. What you said to which model never leaves for a vendor.
Calls tools, touches files, runs steps.
A Rust agent engine handles tool calls, file operations, and multi-step runs. Over MCP it reaches installable apps too — let an agent write docs or update a sheet.
The more you talk, the more context grows.
Memory accumulates in the Workspace from your interactions and carries context into the next chat. Memory also lives on your own server — never trained on, never sent out.
The unit of people, agents, apps, and data.
A Workspace is the unit of activity. Each Workspace is isolated, with its own permissions, and you can add the apps you need — yurucommu for social, yurumeet for talk-first messaging, and more.
First-party apps that work with Takos. Install only the ones you want, and remove them when you no longer need them.
An office suite that unifies docs, slides, and sheets in one worker. Agents can edit files directly over MCP, so you replace Google Docs / Slides / Sheets inside your own Workspace.
A computer-use environment your agents can call — hand off browser actions and command execution to automate routine, multi-step work.
Self-hosted ActivityPub / community social. An independent product that connects to the fediverse and can be added to your Workspace as an app — your data stays with you while you reach out.
A LINE-like talk-first messenger in the yurucommu family. Use the same yurucommu account and API through a talk-centric UI. Install and remove it as a normal app.
How running Takos on your own server differs from delegating to a SaaS provider — typical trade-offs framed around who owns the data (not true of every product).
| Takos (self-host) | SaaS chat (delegated) | |
|---|---|---|
| Where data lives | Your own VM / cloud | The vendor’s servers |
| Memory / history | Kept in your Workspace | Held by the provider, may train on it |
| Vendor lock-in | Export / migrate anytime | Migration is often hard |
| Customization | Fork freely under AGPL | Only what is offered |
| Adding apps | Install the apps you need | Only what the vendor ships |
| Price (self-host) | Software is free (infra only) | Per-seat / usage billing |
The hosted entry and the self-host deployment guide are separate. Takosumi manages accounts and deployment history, while Takos owns your Workspace and data.
