Backups
Protect both state and media: database backups cover catalog and accounts; volume snapshots cover source files, renditions, and posters.
Post-purchase operations
From signed license to a live Tube deployment.
A provider-neutral operating guide for the infrastructure you own: application, database, media origin, DNS, workers, and launch verification.
Operating boundary
What arrives. What stays yours.
Included
- Licensed Tube application release
- Signed annual entitlement for one deployment
- Complete viewer, editorial, moderation, and operator surfaces
- Coolify-ready deployment contract
- Updates during the active license term
Operator owned
- Application host and persistent media volume
- Supabase project and database credentials
- Domain, DNS, TLS, and optional edge delivery
- Email provider and operational alerting
- Backups, moderation policy, and legal compliance
Cost model
The license is fixed. Operations follow usage.
| Cost driver | Owned through | What it covers |
|---|---|---|
| Application host | Docker / Coolify host | Web app, workers, and scheduled jobs |
| Database | Supabase | Auth, Postgres, RLS, and metadata |
| Media | Persistent volume | Source files, renditions, posters, and delivery |
| Network | DNS and optional edge | TLS, cache policy, and transferred bytes |
| Operations | Your team | Monitoring, backups, updates, and response |
Media storage and delivery dominate variable spend. Model transferred bytes, retention, renditions, and cache behavior against your own audience before committing to an infrastructure budget.
Launch sequence
Six controlled handoffs.
- 01
License the deployment
Complete Self-Host checkout. Once the payment network confirms the transaction, the annual license key appears in your account and arrives by email.
- 02
Prepare the host
Provision an adult-content-compatible Docker host with persistent storage. Coolify is the supported deployment surface for the delivered image and workers.
- 03
Connect the data layer
Create the Supabase project, choose the region closest to the host, and retain the project URL, public key, service-role key, and database connection values.
- 04
Allocate the media origin
Mount persistent storage for source files, generated renditions, and posters. Keep that volume in the backup plan and place an edge cache in front only when your delivery profile requires it.
- 05
Set DNS and TLS
Point the selected hostname to the application host, attach it in Coolify, and wait for the production TLS certificate before enabling public indexing.
- 06
Deploy and verify
Apply the delivered environment template, start the application and worker services, then confirm health, license verification, upload, transcode, and playback before opening traffic.
.env
PORNOGRAPHER_IO_LICENSE_KEY=TUBE-SOURCE-XXXXX-XXXXX-XXXXX-XXXXX
PORNOGRAPHER_IO_LICENSE_SERVER_URL=https://pornographer.io
LICENSE_KEY=TUBE-SOURCE-XXXXX-XXXXX-XXXXX-XXXXX
LICENSE_SERVER_URL=https://pornographer.io
SITE_URL=https://your-domain.com
NEXT_PUBLIC_SITE_URL=https://your-domain.com
NEXT_PUBLIC_SUPABASE_URL=...
NEXT_PUBLIC_SUPABASE_ANON_KEY=...
SUPABASE_SERVICE_ROLE_KEY=...
STORAGE_DRIVER=localUse the complete environment template delivered with your release. The block above shows the identity and service boundaries, not every runtime variable.
Reference topology
The license authority stays out of the media path.
Reference topology01 / 01
Your domain
DNS authority
Edge network
TLS · cache · policy
HTTPS
Operator infrastructure · Docker
Tube application
Next.js
Workers
Ingest · AI · jobs
Cache
Optional
Private services
Postgres
Auth · data · vectors
Media origin
Volume · object storage
Pornographer.io
License verification
Your host serves the application and workers, Supabase holds identity and catalog state, and your media origin stores and delivers video. Pornographer.io verifies the signed entitlement; it does not proxy viewer traffic.
Day-two operations
Keep state, media, and workers observable.
Monitoring
Watch application health, database readiness, worker heartbeat, queue depth, storage capacity, and public playback from outside the host.
Updates
Deploy signed releases during an active license term, rehearse database migrations, and keep a known-good application image available for rollback.
FAQ
The operating questions that matter.
Should I choose managed cloud instead?
Choose managed cloud when you want us to own the deployment, patching, backup, and uptime workload. Choose Self-Host when your team wants direct control of infrastructure and media economics.
Can I deploy the full stack to a serverless host?
Not as a complete production installation. Tube includes persistent media and long-running workers, so the supported shape is a Docker host with durable storage.
Can I put a CDN in front of media?
Yes. The origin remains under operator control; an edge layer can be added when geography, throughput, and cache economics justify it.
What happens when the annual license expires?
The signed entitlement becomes inactive. Renewing restores an active term, and the renewal flow extends from the later of the previous expiry or the renewal date.
What should I validate before launch?
Check the public health endpoint, license verification, authenticated admin access, upload, transcode completion, signed playback, email delivery, backups, and an external DNS/TLS probe.
Deployment decision