From core to skin — how KiwiStack grows, layer by layer.
Four layers, each with its own purpose and pace.
Identity, storage, and database — the heart of every kiwi node.
Central identity provider — OAuth2/OIDC, WebAuthn/Passkeys. Single source of truth for all users & groups.
Distributed file storage — S3-compatible, erasure coding, multi-node sharding.
Lightweight, local-first, replicable embedded database — the quiet foundation.
Colorful, independent microservices — each a seed exposed via MCP.
Email, calendar & contacts via JMAP. Network boundary keeps your code Apache 2.0.
Matrix homeserver — hybrid real-time via native client, CRUD via MCP.
Video/audio calls, screen sharing, recording. SFU architecture.
Projects, tasks, kanban boards. MCP-native, no traditional UI needed.
Knowledge base with collaborative editing, full-text search, version history.
The connective tissue — real-time sync and search across every service.
Real-time collaborative editing — Peritext/Fugue CRDTs, offline-first, version history.
Typo-tolerant instant search across emails, chats, files, docs, tasks. One query, all services.
The outer shell — everything the user sees and the gateway for AI agents.
AI-driven frontend shell — embeds native clients for Matrix, LiveKit, and Loro alongside MCP-driven panels.
Unified MCP server — one connection gives AI agents access to all services: mail, calendar, tasks, docs, search.
No dates, just the right order — each phase unlocks the next.
Identity, database, mail, and the MCP gateway — the minimum viable kiwi.
Real-time chat, video calls, and cross-service search — the kiwi starts talking.
Task management, knowledge base, and real-time collaborative editing.
Distributed file storage with S3 compatibility and erasure coding.
The AI-driven frontend shell that ties every seed into one unified experience.
Multi-node orchestration — one install, N nodes, one workplace. The kiwi becomes a cluster.