> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nometria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# STRATEGIC BACKLOG

# Strategic Backlog — Nometria Platform

Items deferred from the automation hooks & deployment infrastructure sprint.
These are multi-week infrastructure projects requiring architectural decisions.

## InsForge-Competitive Features

### C2: AI Model Gateway / LLM Proxy

* **What:** `/api/ai/chat` endpoint on deployed instances proxying to user's configured LLM provider (OpenAI/Anthropic/Gemini)
* **Why:** InsForge bundles multi-provider LLM access. Every vibe-coded app needs LLM access in production.
* **Effort:** 5-7 days
* **Depends on:** Per-instance env var routing, provider SDK integration

### C3: Native Stripe Integration

* **What:** Auto-detect Stripe during migration, pre-built webhook endpoint template, proper secrets handling
* **Why:** Both InsForge and Bolt Cloud bundle payments. Standardizing this reduces migration friction.
* **Effort:** 3-5 days
* **Depends on:** Migration pipeline changes, webhook template system

### C4: WebSocket / Realtime Pub-Sub

* **What:** Managed WebSocket connections for chat, notifications, collaborative editing
* **Why:** InsForge has this built in. Currently requires manual Supabase Realtime config.
* **Effort:** 5-7 days
* **Depends on:** Nginx WebSocket proxy (partial — exists for Supabase), standalone WS server

### C6: Edge Functions (Global)

* **What:** Globally distributed Deno functions beyond single-region EC2
* **Why:** InsForge's Deno-based edge functions reduce latency for global users.
* **Effort:** 7-14 days
* **Depends on:** Partnership with Deno Deploy or Cloudflare Workers, routing layer

## Infrastructure

### I8: CloudFront CDN Layer

* **What:** CloudFront distribution in front of each EC2 instance, auto-configure on deploy
* **Why:** No CDN currently — static assets served directly from EC2 via nginx
* **Effort:** 3 days
* **Depends on:** AWS CloudFront API integration in deploy\_v2, DNS changes

### I11: Multi-Cloud DNS

* **What:** Support Cloud DNS (GCP), Azure DNS, not just Route53
* **Why:** Multi-cloud deployments currently all route through Route53 regardless of provider
* **Effort:** 3-5 days
* **Depends on:** Provider-specific DNS API wrappers in deploy\_v2/operations/

## Strategic / Community

### C8: Open Source Community Setup

* **What:** Public GitHub repos for CLI + SDK + MCP plugin, CONTRIBUTING.md, CI/CD for releases
* **Why:** InsForge has 7.2k GitHub stars. Open source builds trust and community.
* **Effort:** 3-5 days (legal review, repo setup, CI)
* **Depends on:** License decisions, which components to open-source

### G8: CSR → SSR/SSG Upgrade Path

* **What:** During migration, detect CSR-only apps, offer optional prerender/SSR upgrade
* **Why:** Lovable/Base44/Bolt apps are CSR-only and invisible to Google
* **Effort:** 3-5 days
* **Depends on:** Vite SSR plugin integration, rendering detection tool

***

## Reference: Completed Items

See the full implementation report in the PR description. 52+ items implemented across 10 commits including:

* 6 automation hooks (auto-deploy, security gate, cost guardian, PR preview, live preview, auto-rollback)
* 8 new CLI commands (list, rollback, ssh, db, cron + subcommands)
* 5 new slash commands (/logs, /env, /domain, /rollback + /nometria-login updates)
* 5 backend Deno functions (cliDb, cliCron, cliExec, cliDeployments, cliTelemetry)
* 3 new DB tables (deployment\_history, deployment\_events, scheduled\_tasks)
* Python SDK with 18 methods
* 2 frontend tools (CostCalculator, ExitScore)
* 66 automated tests
* Nginx security hardening, input validation, framework detection for 8 frameworks
* Complete domain migration (ownmy.app → nometria.com)