You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your own knowledge system. Connect to the fleet. Make everyone smarter.
Quick Start
docker run -d --name plato -p 8847:8847 -v plato-data:/data ghcr.io/superinstance/plato-server
# Submit your first knowledge tile
curl -X POST http://localhost:8847/submit \
-H "Content-Type: application/json" \
-d '{"room":"my-project","question":"What is FLUX?","answer":"A markdown-to-bytecode runtime for AI agents","agent":"me"}'
What It Does
PLATO is a standalone knowledge server that captures, stores, and shares structured knowledge tiles (Q&A pairs). Run it locally, let your agents learn from it, and optionally sync with the Cocapn fleet to share what you learn and learn from everyone else.
Solo mode (default): Your agents interact with PLATO via HTTP. Everything stays on your machine. Fleet mode (opt-in): Your tiles sync to the Cocapn fleet via Matrix. Fleet tiles flow back. Everyone learns from everyone. PLATO can also spawn its own agents — describe what you want, and it picks the right "armor type" (Scholar, Builder, Scout, etc.) and model from your bring-your-own-keys configuration.
Architecture
PLATO Server is the knowledge system layer of the SuperInstance ecosystem. It stores tiles in SQLite, serves them via HTTP, and optionally federates with other PLATO instances via Matrix sync every 5 minutes. It connects to the PLATO Engine Block family for embedded/edge deployments, and to FLUX agents that use PLATO as their knowledge substrate.
POST /submit
{
"room": "my-domain",
"domain": "architecture",
"question": "Your question here?",
"answer": "Your answer — at least 20 characters, specific, no absolutes",
"agent": "your-name"
}
Tiles are validated: answer must be ≥20 characters; blocked words include always, never, impossible, guaranteed, nobody — encouraging specificity over absolutes.