Internal · Infrastructure Map
Avium Infrastructure
Every service, every layer, every connection. Top-to-bottom, from user click to persisted data.
Updated · 2026-05-21
App version · v2.4.0
Owner · Brian Akers
01
Audience
End User
Engineering managers, PMOs, and sprint leads running engineering teams on Jira or any work management tool. They open Avium when they need to know who's working on what, whether the team has capacity, and where delivery is at risk.
Chrome Safari Firefox Desktop primary Mobile responsive (planned)
HTTPS · TLS · www.getavium.com
02
Surface
Front End · React
A single-page application served as static assets directly from Railway. Tailwind for styling, React Router for client-side navigation, Zustand for auth state.
Login · Setup · Password Reset Dashboard Workload (Board · Phases · Matrix · List) Intelligence (Sprint Matrix · Patterns) Docs · Admin · Billing
REST · JSON · JWT
03
Engine
Middleware · Express on Node 22
The brain of the platform. Authenticates every request, enforces plan-tier gates, applies rate limiting, and routes traffic to the right domain handler. Every business rule lives here.
auth · org · super-admin jira · tickets · planning allocations · phases · dashboard demo-data · import/export stripe webhook + checkout
✦ Avium Signals Engine · Proprietary
Avium IP · not a vendor
The deterministic rules library that produces every insight card on the Insights page. No LLM, no vendor — domain-specific rules authored against real engineering teams. This is the moat. Customers on Team+ get the full engine; the AI layer (Anthropic, layer 4) is additive narrative on top.
Sprint Risk Over-Allocation Rebalance (same-dept) Velocity Drift Blocked / Stale Data Quality Lead Time (configurable) Time in Status (configurable) Dwell card Reopen Rate (configurable) Sprint Scope-Change (configurable) Sprint Creep card Flow Efficiency (configurable) Hand-off Cost (configurable) Workflow Sankey (configurable) Ping-Pong card (configurable) Dashboard KPI strip
server/src/lib/intelligenceEngine.ts server/src/lib/leadTimeService.ts server/src/lib/timeInStatusService.ts server/src/lib/reopenRateService.ts server/src/lib/sprintScopeChangeService.ts server/src/lib/flowEfficiencyService.ts server/src/lib/handOffCostService.ts server/src/lib/workflowSankeyService.ts server/src/lib/pingPongService.ts pure functions · unit-tested runs without an Anthropic key Team+ tier
ReportConfig model (Phase 5) TicketTransition + TicketFieldChange via expand=changelog org default · per-user views · ad-hoc in-place rename · delete · clear org default unified page-level Date Range filter (presets + custom) never truncates output
04
Reach
↘ In-Data · Imports
External Sources
Where customer data enters the platform. Every record carries its origin tag.
Jira REST API · per-org token Excel / CSV upload (1k Free · 5k paid) In-app ticket create (Avium-native) GitHub auto-deploy webhooks
↓ Core · Persistence
Database
The system of record. Every ticket, allocation, time log, and resource lives here.
⚠️ No off-platform backups — critical pre-paying-customer gap.
↗ Out-Comms · Integrations
Outbound Services
Where Avium reaches out — for emails, payments, AI, and operational comms.