How aniraku/aniraku-backend works
Aniraku Backend is a Go API service for web and Android clients, centered on episode lookup and playback coordination. Requests enter through the HTTP router; playback fans out to enabled streaming providers, while episode metadata uses AniZip/TMDB resolution. The service also exposes catalog, account, import/export, and sync capabilities, with JWT authentication and guarded upstream networking. The graph follows documented routes and capabilities; some unsampled subsystem links are omitted where source excerpts do not establish the caller.
Main entry points: router.go Chi router · handlers.go API handlers · proxy.go Playback endpoints · manager.go Provider manager
Components 19
API surface
- HTTP service
cmd/aniraku-server/main.go - Chi router
internal/api/router.go - API handlers
internal/api/v1/handlers.go
Playback
- Playback endpoints
internal/api/v1/proxy.go - Provider manager
internal/streaming/manager.go - Streaming providers
internal/streaming - Media proxy
internal/api/v1/proxy.go
Metadata
- Catalog API
internal/api/v1/catalog.go - AniList client
internal/api/v1/anilist_client.go - Episode lookup
internal/api/v1/catalog.go - AniZip / TMDB resolver
internal/tmdb/resolver.go
Identity and accounts
- JWT middleware
internal/auth/middleware.go - JWKS keys
internal/auth/jwks.go - Account API
internal/api/v1/account.go - Import and sync
internal/api/v1/importexport.go
Network safety
- SSRF network guard
internal/netguard/ssrf.go
Other components
- Web / Android clients
- Provider / CDN services
- Supabase
Connections 20
- Web / Android clients → Chi router: sends requests
README.md - HTTP service → Chi router: serves routes
- Chi router → API handlers: routes requests
internal/api/router.go - Chi router → JWT middleware: protects routes
internal/api/router.go - API handlers → Catalog API: serves catalog
README.md - Catalog API → AniList client: queries catalog
README.md - API handlers → Episode lookup: serves episodes
README.md - Episode lookup → AniZip / TMDB resolver: resolves titles
README.md - API handlers → Playback endpoints: serves playback
README.md - Playback endpoints → Provider manager: coordinates sources
README.md - Provider manager → Streaming providers: fans out
internal/streaming/manager.go - Streaming providers → Provider / CDN services: fetches streams
- Playback endpoints → Media proxy: proxies media
README.md - Media proxy → Provider / CDN services: fetches media
README.md - Media proxy → SSRF network guard: guards requests
README.md - JWT middleware → JWKS keys: verifies tokens
- Chi router → Account API: routes account
internal/api/router.go - Chi router → Import and sync: routes sync
internal/api/router.go - Account API → Supabase: reads and writes
README.md - Import and sync → Supabase: syncs account data