Fast enough to feel local. Managed enough to stay stable.
Kaizen is tuned around native Apple Silicon execution, Apple Metal acceleration, and separated services that can be started, stopped, tested, logged, and monitored individually. Public pages describe the architecture at a product level without publishing private credentials, prompts, or operational endpoints.
Public Performance Signals
Runtime Improvements
The latest work focused on reliability, search quality, communications, delivery proof, public boundaries, and dashboard operations.
Search Quality
Search-grounded answers use cleaner result selection, source-aware summaries, and a local-first provider route: a private metasearch layer answers most queries with zero external API quota, with a paid provider as governed fallback.
Background Work
Long-running model requests are managed through runtime jobs so mobile sessions can resume more predictably.
Memory Controls
Memory editing, user separation, and stricter save behavior reduce low-value or duplicate memory injection.
Public Queue
KaizenAI Open uses a public request queue with daily limits and metadata-only logging for abuse monitoring.
SMS Delivery
Communications Hub stores inbound/outbound messages, call alert state, provider IDs, delivery status, contact mapping, timestamps, and message bodies for operator traceability.
Call Path
Real-time inbound phone conversations with Max are live for approved users, running on a dedicated low-latency speech tier tuned for conversation, behind the same approved-user boundary as every private lane.
Schedule Analysis
The project management decision tools run deterministic structural analysis — quality audits, logic checks, industry-standard assessments — at interactive speed against a local working copy, never a guess from a model.
Stack Health
A standing collector samples every service on a fixed cadence, the dashboard renders live health, and the assistant can answer stack-health questions from real probes instead of stale assumptions.
Reminder Scheduling
Durable reminder jobs are stored in SQLite and delivered through existing communication channels rather than a separate one-off notifier.
Beacon Watchdogs
Scheduled reliability workflows check for missed runs, failed processing, and missing carrier delivery proof instead of trusting local "sent" status alone.
Unified Logs
The dashboard exposes a redacted, read-only log catalog with tail, source search, cross-source search, severity filters, and downloads.
Operational Receipts
The credible proof is in dated status, logs, and release surfaces, not in a generated terminal aesthetic.
Service status
The local controller reports the Orchestrator, Gateway, Runtime, Search, Research, Planning, MCP Bridge, Memory, Voice, Communications Hub, Reminders, IMGEN, ComfyUI, HomeAuto, Caddy, Cloudflare, and callback surfaces as running or routed through protected services.
Release notes
The July 2026 changelog is dense: Communications Hub and reminders early in the month, then the project management decision platform, the live real-time voice lane, local-first search routing, per-user media workflows, and a stack-health lane the assistant itself can read.
Dashboard proof
The protected dashboard includes service control, observability, logs, notifications, communications, backups, Beacon workflows, access tiers, secrets, prompts, skills, and public-edge controls.
What Is Not Published
Performance marketing does not require exposing sensitive implementation detail.
No sensitive inventory
The public site avoids private hostnames, network maps, credentials, prompts, tokens, and control URLs while still showing enough architecture to verify the system shape.
No base model names
Public wording uses Kaizen product and release terms instead of upstream model names or internal aliases.
No operational endpoints
Ports, private URLs, routes, logs, prompts, and runtime configuration stay inside the protected dashboard.
