Architecture: Session 121: How to harden Vitto for production?

Documentation for Sessions

🏗️ Architecture: Session 121: How to harden Vitto for production?

Date: 2026-02-19
Time: 03:35:32 UTC
Session: gspace1-121.2
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Session 121: How to harden Vitto for production?

Task: Not specified

🎯 Decision Made

Chosen:

Railway Redis + E2B + Browserless (managed services)

Options Considered:

Railway Redis + E2B + Browserless (managed services)
Self-hosted Docker + Playwright (DIY)
Upstash Redis + local exec (hybrid)

💭 Reasoning

Railway Redis chosen over Upstash because BullMQ idle polling racks up Upstash command-based billing (~$10/month fixed vs ~$3.65 on Railway). Railway Redis runs on same private network as APIs (sub-ms latency). E2B chosen for sandbox (Firecracker VMs, $0 free tier, used by Cursor/Vercel). Browserless chosen for browser automation ($0 free tier, proper CDP WebSocket). All managed = zero maintenance for solo developer. Total cost: $3.65-29/month. Also fixed: context window tool pairing (atomic groups), sandbox endpoint gating (ENABLE_SANDBOX), Redis reconnect, workflow step wiring, meeting LLM analysis.

📁 Files Involved

No files specified

🔗 Related

Decision ID: dev_1771472131984_kgg4cza
Session: 121
Workspace: gspace1

Auto-generated by MCP Smart Consolidation