Faxas Hub
Faxas Hub is a self-hosted operations dashboard built for homelabs running GPU-intensive workloads. It unifies telemetry from Beszel, Uptime Kuma, and Glances through a BFF architecture — giving you a single pane of glass for your entire infrastructure.
Titan
Storage Devices
Authentik SSO
Quick access to identity management
Services
USER
Self-hosted photo and video management
42msSelf-hosted file sync and collaboration platform
118msMedia server for movies, TV, and music
23msOpen-source media streaming server
31msSelf-hosted password manager
12msPrivacy-respecting metasearch engine
205msSelf-hosted audiobook and podcast server
67msAI
Local large language model runner
89msWeb interface for local AI models
134msLocal AI API compatible with OpenAI
312msNode-based AI image generation workflow
156msADMIN
Lightweight server monitoring agent
8msSelf-hosted uptime monitoring tool
15msDocker container management UI
22msCross-platform system monitoring tool
19msReverse proxy management with SSL
6msIdentity provider and SSO platform
45msZero-config mesh VPN
3msThis is a simulated interface. All data shown is illustrative.
Supported App Ecosystem
89 services auto-categorized across 4 groups
Faxas Hub auto-discovers and categorizes Docker containers using custom faxas.* labels and a curated registry of 89 known services. Each service is assigned to a group — User, AI, Admin, or Other — with offline brand icons and deterministic fallbacks.
User Apps
Immich
Self-hosted photo and video management
Nextcloud
Self-hosted file sync and collaboration platform
SearXNG
Privacy-respecting metasearch engine
Plex
Media server for movies, TV, and music
Jellyfin
Free media server for movies, TV, and music
Vaultwarden
Lightweight Bitwarden-compatible password server
Audiobookshelf
Self-hosted audiobook and podcast server
AI Services
Ollama
Local large language model runner
Open WebUI
Web interface for local AI models
LocalAI
Local AI API compatible with OpenAI
ComfyUI
Node-based Stable Diffusion interface
Admin Tools
Beszel
Lightweight server monitoring agent
Uptime Kuma
Self-hosted uptime monitoring
Portainer
Docker container management UI
Homepage
Application dashboard and launcher
Nginx Proxy Manager
Reverse proxy management with SSL
Glances
System monitoring at a glance
Authentik
Identity provider and SSO platform
Tailscale
Zero-config mesh VPN
Infrastructure
Faxas Hub
GPU-first self-hosted ops dashboard
Docker
Container auto-discovery via socket proxy
Faxas Hub auto-categorizes 89 services across 4 groups using Docker labels and a curated service registry.
Architecture
Four-layer BFF with security boundaries
The architecture follows a strict Backend-for-Frontend pattern. The browser talks only to Next.js API routes — never directly to upstream services. Credentials stay server-side, SSRF protections guard internal network access, and HMAC gates validate upstream connectivity.
Browser
Glassmorphic React UI with mobile-first responsive layout and three service view modes.
Next.js API Routes
BFF layer that aggregates, caches, and normalizes data from upstream APIs. All credentials stay server-side.
Integration Adapters
Contract-based adapters with consistent interfaces. Each adapter normalizes upstream data into stable v1 contracts.
External Services
Upstream monitoring and infrastructure services providing raw telemetry, health data, and container info.
Security Boundaries
Credentials Server-Side
Upstream API keys never reach the browser. All credentials are managed in the BFF layer.
SSRF Protection
RFC 1918 blocklist prevents server-side requests to private network ranges.
HMAC Enablement Gates
SHA-256 HMAC gates validate adapter connectivity before exposing data paths.
Integration Intelligence
6 adapters with isolated failure containment
Each upstream service has a dedicated adapter that normalizes raw API data into stable v1 contracts via Zod schemas. If an upstream goes down, the adapter returns null data with a health status — no cascading failures, no broken UI.
Beszel
System MetricsPrimary telemetry source for CPU, RAM, GPU, and storage metrics across hosts and containers.
Returns null data with health=down; UI shows stale indicator
Raw Beszel API → stable v1 metrics contract via Zod schemas
Uptime Kuma
Health MonitoringService health checks, uptime percentages, and latency monitoring with alerting support.
Returns null data with health=down; monitors show unknown status
Kuma push API → v1 health contract with normalized status enum
Glances
Device TelemetryPer-device breakdowns of CPU, memory, disk, and network. Optional GPU fallback when Beszel lacks support.
Returns null data with health=down; device metrics unavailable
Glances REST API → v1 device contract with unified metric shapes
Docker
Container DiscoveryContainer auto-discovery via socket proxy, status tracking, and label-based service categorization.
Returns null data with health=down; service list shows cached state
Docker socket API → v1 services contract with faxas.* label parsing
Nginx Proxy Manager
Proxy ResolutionReverse proxy URL resolution for exposed services. Matches container names to proxy hosts.
Returns null data with health=down; URLs fall back to direct IPs
NPM API → v1 proxy-host contract mapping container → domain
Tailscale
Network OverlayVPN mesh network integration for LAN discovery and Tailscale-based link generation.
Returns null data with health=down; links fall back to LAN addresses
Tailscale API → v1 device-hostname contract for link generation
Operational Readiness
Engineering metrics from the source repository
Faxas Hub ships with comprehensive test coverage, a minimal Docker footprint, and security hardening built into every layer — from SSRF protection to encrypted sessions.
Security Hardening
- SSRF protection with RFC 1918 blocklist
- HMAC-SHA256 enablement gates
- Rate-limited authentication endpoints
- Encrypted session cookies (iron-session)
- Docker socket proxy isolation
Project Access
Source code and documentation
Why no live demo?
Faxas Hub runs on private homelab infrastructure with real upstream services — there is no public browser demo.
All capability claims are backed by verified captures from the running system, architecture documentation, and engineering metrics from the source repository.