We don't claim what we haven't built. This page is the source of truth for REDIS.4U — reconciled against the codebase regularly so what you read here is what's actually working.
Every capability below is live in the codebase and exercised in the demo paths we run. Items shown grouped by area — nothing in this section is aspirational.
Multi-tenant SaaS infrastructure with strict tenant isolation.
Real-time, push-based. No nightly batch. No export file.
Product master with everything operations needs.
The customer master everything else reads from.
Draft to closed in one workflow.
Routing today, real-time optimization later.
Eight document types, printed where they belong.
Your customers see what they need to see.
Where the AI layer stands today.
Customer management module — opt-in per tenant.
Lead → Won, with one-tap conversion to customer.
Internal observability for platform admins.
Code may be on disk, but until it's exercised end-to-end with migrations applied and crons firing in production, it stays in this section. Honesty over optics.
Canonical reactive pipeline for sales-driven order intake. All ten stages and the Kanban view are code-complete; the verification pass to confirm migrations are applied and every cron/webhook fires correctly is the gating work.
Replacing the deterministic parser stub with a lean in-process Claude path, wired to a per-tenant learning loop that makes the next sighting of the same raw token exact, free, and instant. Highest-value gap in the pipeline.
Per-child customer splitting when an order targets a customer group. Each child gets its own draft order and Planned Recurring Order entry.
Drag-stage transitions are partial; bulk actions across selected cards currently return a not-implemented response. Both close out this slice.
The SMS half of the communications engine — templates, click-to-call, inbound replies, auto-logging to the pipeline. Gated on account setup and phone-number provisioning. Email side (Resend) is already live.
Native shell around the existing Next.js app. Native barcode scanner, native push notifications, native print dialog, encrypted on-device cache for walkthrough fingerprints.
CReMA Phase 2 polish — one-click pay link on outstanding balances, plus an editor for dunning rules so each tenant can tune their own escalation cadence.
The intelligence mesh is the centerpiece of the next year of work. Below: the engine roster with current status, followed by the rest of the roadmap grouped by area.
Ten engines plus a suite of agents. Order built reflects compounding value — E7 first because it makes everything else cheaper, then procurement and demand, then the rest.
This page is reconciled against the live codebase regularly. When something moves from in-flight to shipped, it moves here. When something we thought was shipped fails verification, it moves back to in-flight. The categories mean what they say.
Things not on this page yet aren't being hidden — they're decisions we haven't made. When they're decided they'll appear here, in the right column.
Questions about a specific item, or want context on why something is where it is? Drop us a line — we answer ourselves.