Two clients, one backend
Krewva Life and Krewva Biz share the same backend primitives but present different product surfaces.
Life ships as iOS, macOS, and web with swipe-deck approval cards. Biz ships as a separate web and Electron desktop app with a 3D office. Both talk to the same Fastify backend, SQS FIFO queues, card system, RDS data layer, Playwright browser pool, and DeepSeek v4 flash model layer.
Life: one unified agent
Krewva Life is not a bundle of separate public agents.
The Life agent works across the apps you connect: Gmail, Drive, Calendar, Slack, WhatsApp, iMessage, planned Instagram, banks, insurance, school portals, and MyChart. It compresses personal decisions into one approval feed. A per-user Erlang supervisor keeps the personal runtime coherent.
Biz: independent department agents
Krewva Biz is intentionally simpler than an orchestrated agent fleet.
Sales, marketing, finance, legal, HR, ops, PM, and analytics run as standalone processes. Each department agent has its own markdown system prompt and tool grants. There is no department router and no cross-department callback token flow. Agents coordinate through the shared business Drive tree.
Drive-as-graph
The shared Google Drive folder is the business system of record.
Biz agents read and write canonical files under /krewva-biz/{workspace}/{department}/. Sales can write a closed-deal note, finance can read it for billing, legal can read contract terms, and analytics can roll the outcome into a KPI memo. The graph is inspectable because it is made of files, not hidden state.