AccessFlow
Self-hosted portal to manage users, subscriptions and invites for a personal Plex server. Built with FastAPI + Jinja2/HTMX on Docker Compose.
Ficha actualizada 23 sept 2026, 14:39 · upstream 23 sept 2026, 14:36 · release v1.3.1
Qué es AccessFlow
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
AccessFlow is a self-hosted management portal that centralizes user lifecycle management for a personal Plex media server. It eliminates manual tracking of who has access to what content by maintaining a single source of truth through subscription plans, role-based permissions, and automated renewal workflows.
The system supports multiple managers per user so different team members can collect payments independently while all users remain under one Plex account. Plans are flexible with free tiers available out-of-the-box, custom paid plans created on demand, and two-step renewal processes that keep expired subscriptions pending until payment is confirmed.
Key features include role-based access control (SuperAdmin, Admin, Moderator, User), financial reporting, Telegram notifications for expiration reminders, audit logging, soft-delete functionality with orphan protection, and full i18n support. The application runs as a single Docker container behind a reverse proxy, making it ideal for small to medium-sized Plex deployments.
- Centralize user management without maintaining multiple accounts per Plex server
- Automate subscription renewals with two-step payment collection and expiration tracking
- Generate financial reports on revenue collected versus pending subscriptions
- Send automated expiration reminders via email or Telegram to users at risk of losing access
- Manage multiple managers who each collect payments for their own set of users
- Runs as a single Docker container with SQLite database, reducing infrastructure complexity
- Supports role-based access control with granular permissions per user and manager
- Two-step renewal workflow ensures expired subscriptions remain pending until payment is confirmed
- Telegram bot integration allows users to link their own messaging account for automated reminders
- Full i18n support with translatable source strings in English, Spanish, French, German, Italian, Portuguese, and Russian
- No built-in payment gateway or billing automation — manual collection of payments is required
- Telegram bot integration requires users to manually link their Telegram account for notifications
- Database backups are not automated at the application level; external tools must be used
- No support for multi-plex server deployments beyond one Plex instance per user
- Custom paid plans require manual creation by SuperAdmin with no predefined templates
Capturas del proyecto
Imágenes reales detectadas en la documentación del repositorio.
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
Deploy via Docker Compose on Linux/Windows/macOS. Set environment variables from .env.example before starting: PLEX_API_KEY, APP_SECRET_KEY, DATABASE_PATH, NOTIFY_HOUR (for expiration checks), and ENABLE_SCHEDULER for background jobs. The app listens on port 8000 behind a reverse proxy like Nginx or Traefik. Use X-Forwarded-Proto header to preserve HTTPS URLs when behind an SSL proxy. For production, consider adding Redis for caching user sessions and rate limiting API endpoints.
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Puede sustituir a
Relaciones detectadas por el análisis del repositorio y su categoría.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.