How workweave/router works
Weave Router is a model-routing gateway with an admin dashboard and policy-serving control plane. The principal flow is a client request entering the HTTP server, passing through proxy handling and routing, then reaching a provider; usage and routing outcomes support analytics. The tree indicates additional policy, subscription, billing, and HMM capabilities. Source excerpts confirm server route registration and the composition-root role, but most runtime links are not shown, so those are marked unverified rather than asserted.
Main entry points: service.go Request proxy · server.go HTTP server · router.go Model router · executor.go Provider dispatch
Components 16
Gateway and routing
- HTTP server
internal/server/server.go - Request proxy
internal/proxy/service.go - Model router
internal/router/router.go - Provider dispatch
internal/dispatch/executor.go - Provider clients
internal/providers - Identity and auth
internal/auth/service.go
Policy and control plane
- Policy client
internal/policyclient/client.go - Policy registry
internal/policyregistry/serving_controller.go - HMM routing
internal/router/hmm
Accounts and analytics
- Provider subscriptions
internal/subscriptions/manager.go - Billing
internal/billing/service.go - Routing analytics
internal/analytics/service.go - Postgres repositories
internal/postgres/repository.go
Admin interface
- Admin dashboard
frontend/src/app/(app)/dashboard/page.tsx - Admin API
internal/api/admin
Other components
- API client
Connections 18
- API client → HTTP server: sends requests
- HTTP server → Request proxy: routes requests
- Request proxy → Model router: requests decisions
- Request proxy → Provider dispatch: dispatches inference
- Provider dispatch → Provider clients: calls providers
- Request proxy → Identity and auth: uses identity
- Model router → Policy client: consults policy
- Policy client → Policy registry: fetches serving data
- Model router → HMM routing: uses HMM routing
- Request proxy → Provider subscriptions: leases accounts
- Request proxy → Billing: checks or records spend
- Request proxy → Routing analytics: emits outcomes
- Routing analytics → Postgres repositories: persists analytics
- Billing → Postgres repositories: persists billing data
- Admin dashboard → Admin API: calls admin routes
- HTTP server → Admin API: registers admin routes
internal/server/server.go - HTTP server → Request proxy: registers metrics handlers
internal/server/server.go - Model router → Provider clients: wired at startup