Supabase
Authentication, Postgres, RLS, vectors, and application state.
Tube connects the database, media delivery, security, email, observability, and editorial assistance needed to run a serious site. Managed customers get the operating stack configured for them; Self-Host customers control each service directly.
Authentication, Postgres, RLS, vectors, and application state.
Persistent source storage, transcoded renditions, posters, and playback delivery.
Runs on infrastructure controlled by the operator.
Add what fits
Start with the operating essentials, then turn on the delivery, security, intelligence, and monitoring services that match your site.
Transactional email delivery.
Bot protection on signup and comments.
Request-level security: rate limit, bot detection, shield.
Optional metadata understanding and editorial assistance.
Error tracking (env-toggle).
Built-in /api/vitals endpoint.
Designed for operators
A clean service boundary makes setup easier, incident response faster, and future changes less risky.
Tube needs an application database and an operator-owned media path. Everything else is added only when your operating model calls for it.
Email, bot protection, request security, error tracking, AI access, and Web Vitals reporting are separate controls—not mandatory bundle clutter.
Readiness checks help separate database, media, email, worker, and license problems instead of turning them into one vague outage.
Managed customers
You make the editorial and business decisions. Pornographer.io handles the managed application, backups, updates, SSL, and core service configuration included with the plan.
Choose your operating model
Launch a managed branded site with the operating stack handled for you, or use the Self-Host documentation to operate Tube on infrastructure you control.