Gaps & Roadmap
Known limitations, open decisions, and planned work as of June 2026.
Current Gaps
Production Environment
Production is not yet live. All traffic runs on Railway staging. The AWS migration plan is drafted (v2, May 2026) but not started.
Services Not Yet Deployed
The blitz monorepo contains 23 service directories. Only 6 are deployed to Railway staging. The remaining 17 are built (images exist in GHCR) but not actively running:
| Service | Status |
|---|---|
apimgmt, queue, events, wfwpdf, pdfwriter | Built, not deployed |
fs, rulesengine, mcp, scriptrunner | Built, not deployed |
jsontransformer, templaterenderer, classicml | Built, not deployed |
email, recon, remotecontrol, jobs, desktop | Built, not deployed |
Which of these come to production at AWS launch is an open decision.
RabbitMQ Streams — AWS Blocker
The stack uses RabbitMQ in two ways:
- AMQP (port 5672) — supported by Amazon MQ
- RabbitMQ Streams (port 5552) — NOT supported by Amazon MQ
This blocks a managed Amazon MQ migration. Options:
- Self-host RabbitMQ on ECS Fargate (more ops overhead)
- Replace Streams usage with standard AMQP where possible
Must be resolved before AWS Phase 4 (messaging layer).
IaC Tooling for AWS
CDK (TypeScript) vs Terraform (HCL) decision pending. Terraform is the current recommendation. Must be decided before AWS Phase 3 (compute layer).
Open Decisions
| # | Item | Status |
|---|---|---|
| 1 | RabbitMQ Streams — Amazon MQ vs self-hosted | Pending investigation |
| 2 | IaC tooling — CDK vs Terraform | Pending decision |
| 3 | Container registry — GHCR (unchanged) vs ECR | Deferred to AWS Phase 3 |
| 4 | Service scope for AWS — which 17 non-deployed services go live | Pending |
| 5 | jobs service — may overlap with queue; needs review | Pending |
| 6 | Ollama — replace with Bedrock or external API on AWS | Pending |
| 7 | Zoho SSO — IAM Identity Center + SAML setup | Pending (before Phase 1) |
| 8 | Hyderabad (ap-south-2) as DR target | Deferred post-launch |
AWS Migration Phases
See Infrastructure — AWS Migration for the full 7-phase plan.
| Phase | Scope | Status |
|---|---|---|
| 1 — Foundation | VPC, RDS, S3, Secrets Manager, IAM Identity Center | Not started |
| 2 — Data migration | Postgres + RustFS → S3 | Not started |
| 3 — Compute | ECS Fargate + ALB | Not started |
| 4 — Messaging | RabbitMQ, ElastiCache, Temporal Cloud | Not started (blocked on Streams decision) |
| 5 — Cutover | DNS, Railway decommission | Not started |
| 6 — Observability | CloudWatch, X-Ray, alerting | Not started |
| 7 — Security hardening | WAF, GuardDuty, KMS | Not started |