Risk register

Make technical, commercial, and compliance risks visible before scale.

UmamiEdge should scale only after core risks have named owners, mitigation paths, and customer-facing evidence. This register is built for investor review, pilot governance, and engineering prioritization.

Open risks5

tracked in demo register

High priority2

must be mitigated before paid production

Operating modelOwner-led

every risk has accountable function

Review cadenceWeekly

pilot and executive readiness review

Register

Current launch and scale risks.

Runtime proxy not connected to real vLLM/Ollama/TGI service

high

Product · likelihood medium · owner API · mitigating

Add runtime health table, signed runtime URL config, timeout budget, and provider failover before paid production traffic.

Node agent needs signed release and retry queue

high

Infrastructure · likelihood medium · owner Infra · mitigating

Package agent with systemd, buffered telemetry queue, release checksum, and upgrade channel.

Customer quota enforcement is still conceptual

medium

Commercial · likelihood high · owner Platform · open

Add customer API key middleware, usage_events write path, hard quotas, and admin override workflow.

Supabase migrations may be run out of order by operators

medium

Database · likelihood medium · owner Platform · mitigating

Keep compatibility SQL first, add migration center page, and document SQL order in guides.

Regional residency proof must be exportable for regulated buyers

medium

Compliance · likelihood medium · owner Security · open

Add exportable evidence bundle with routing decisions, policy IDs, audit events, and incident attestations.

Risk Register | UmamiEdge