Focused AI services, not one exposed chatbot.
Kaizen is divided into runtime areas with different trust levels. Max is the private assistant. KaizenAI Open is the public assistant. Search, voice, memory, automation, and orchestration remain separated so each path can be secured, logged, and tested. A recent rebuild split the core runtime into independent service areas and added tier-based access control so capability is granted deliberately, not by default.
Access Boundary
Assistant Layers
Each layer has a narrower job and a clearer security boundary.
Max
The private assistant layer for authenticated owner workflows, memory-aware conversations, iOS continuity, and model routing.
KaizenAI Open
The public assistant layer for limited general chat and search-grounded answers. It has no private memory and no internal system access.
Orchestrator
The management layer for service health, prompt editing, memory tools, public chat controls, audit output, and operational diagnostics.
Current Runtime Setup
The active stack is organized around daily use, testing, observability, and controlled public access. It was recently split into separated service areas so each path can be secured, scaled, and tested on its own instead of one process doing everything.
Chat Runtime
Routes private and public conversations through the correct prompt, search, memory, and safety path. A front-door gateway now handles sign-in, identity, and access-tier checks before a separate execution area runs the conversation.
Search Runtime
Handles current web questions, source-aware summaries, weather and finance lookups, and response cleanup. It now runs as its own dedicated service so search can be tuned and tested without touching the chat path.
Voice Runtime
Supports speech input, speech output, runtime status messages, and mobile voice workflows, with smoother turn-taking and cleaner spoken-response handling.
Public Runtime
Queues and rate-limits KaizenAI Open requests on its own isolated path while blocking private tools and personal memory. The recent split keeps the public lane structurally separate from private execution.
Access & Governance
Who can reach which capability is decided at the gateway, before a request ever reaches a model — not left to the client to enforce.
Access Tiers
Every user belongs to an access tier that decides which models, tools, and limits they get. The owner tier is unrestricted; trusted and guest tiers are progressively narrower, and the rules are applied centrally rather than trusted to each device.
Concurrency Control
A runtime governor caps how many heavy local requests run at once and queues the rest, keeping the platform responsive under load instead of overcommitting hardware.
Operator Dashboard
A protected control plane manages users and tiers, memory, conversation-sync health, public-chat limits, prompts, service status, and per-service logs in one place.
Development Agents
Kaizen also uses command-line AI agents for its own software work, audits, and documentation loops.
Code Operations
CLI agents can inspect source trees, patch services, run tests, compare diffs, and prepare controlled releases through the private development workflow.
Audit Loops
Automated checks and guided agent reviews validate runtime health, public boundaries, memory separation, search quality, access-tier enforcement, and mobile client regressions across every separated service area — with a repeatable test battery run before and after each change.
Skill Updates
Reference skills and stack notes are updated as the platform changes so agents can keep context aligned with the current Kaizen release.
Mobile Apps
Kaizen is being built beyond the browser, with mobile clients focused on real conversation workflows.
iOS App
The native iOS app runs on TestFlight with chat, advanced voice, runtime status messaging, diagnostics, and private assistant continuity. Recent builds added reliable history management across devices, conversation pinning, live formatted responses while the model is still typing, and faster, smoother streaming.
Android App
The Android client is planned/in development for the same public and private assistant patterns. Public access will follow announcements or direct approval.
Capability Areas
Public copy is intentionally high-level. Specific model identities and private endpoints are not published.
Search
Current-information retrieval, source-aware response generation, and output cleanup for readable answers.
Voice
Speech input, speech output, runtime status messages, and native mobile interaction patterns.
Memory
Private semantic recall, per-user memory management, strict user separation, and stricter policies for saving new facts — with add, edit, search, and cleanup handled per person from the operator dashboard.
Automation
Private tool routing for home and infrastructure operations, with operator-gated access controls.
Coming Next
Near-term work is focused on safer access, clearer runtime controls, and better mobile continuity.
Agent governance
Access tiers and centralized gateway enforcement are now live. Next is finer-grained, per-tier policy for exactly which users and routes can reach memory, automation, public chat, and future specialized agents.
Public queue visibility
Cleaner public messaging for queued requests, daily limits, route availability, and early-access contact paths.
Specialized agents
Additional private agents for infrastructure awareness, media workflows, home operations, and personal productivity will remain gated by role and policy.
Public Safety Rules
KaizenAI Open operates with a smaller trust envelope than Max.
No private memory
Public prompts do not receive personal profile context, relationship memories, historical chats, or user-specific preference injection.
No device control
Public prompts cannot route to private automation tools or operate lights, locks, alarms, network equipment, or other devices.
No internal disclosure
Public responses use Kaizen release terminology and do not disclose base model identities, private prompts, hostnames, ports, keys, or infrastructure maps.
