PE Tube¶
Self-hosted video platform at
videos.448.global. Likely a PeerTube instance (open-source YouTube alternative) — or a similar self-hosted video service.
| Field | Value |
|---|---|
| Public URL | https://videos.448.global |
| Audience | [CONFIRM] (internal staff? selected partners?) |
| Criticality | low-medium |
| Maturity | [INFO NEEDED] |
| Owner | [INFO NEEDED] |
| Last reviewed | 2026-05-05 |
Interview block¶
- Is "PE Tube" a PeerTube instance or a different self-hosted video product?
- What is it used for? (training videos, customer demos, internal communication, recordings)
- Who can view? (public, signed-in staff only, specific groups)
- Roughly how many videos / GB of storage?
- Where is the video data stored? (locally on host, MinIO, external S3?)
- Hosting details — IPs, host?
- Vault entries for admin?
1. At a glance¶
A self-hosted video platform for internal or limited-audience video content. Likely PeerTube based on the naming convention. [CONFIRM]
2. Business purpose¶
[INFO NEEDED] — training? archive of recorded meetings? customer-facing video?
3. Audience¶
[INFO NEEDED]
4. Hosting & cloud infrastructure¶
Infrastructure map¶
| Item | Value | Notes |
|---|---|---|
| Public hostname | videos.448.global | |
| Public IP(s) | [INFO NEEDED] |
|
| Open ports | 443 [CONFIRM] |
possibly streaming ports |
| TLS cert | [INFO NEEDED] |
|
| Reverse proxy | [INFO NEEDED] |
|
| Container image / version | [INFO NEEDED] (likely chocobozzz/peertube) |
|
| Host server name | [INFO NEEDED] |
|
| Storage backend | [INFO NEEDED] (local disk or MinIO) |
|
| Database | PostgreSQL [CONFIRM] if PeerTube |
|
| Redis | [CONFIRM] if PeerTube |
|
| Total video storage used | [INFO NEEDED] |
Credentials in Vault¶
| Secret type | Vault path / link | Last rotated |
|---|---|---|
| Admin login (root) | [INFO NEEDED] |
|
| Database password | [INFO NEEDED] |
|
| MinIO/S3 access keys (if used) | [INFO NEEDED] |
|
| SMTP credentials | [INFO NEEDED] |
5. Technology behind it¶
- Type: off-the-shelf
[CONFIRM] - Product (likely): PeerTube (Node.js + PostgreSQL + Redis + storage backend)
6. Data it handles¶
- Video files (potentially large; possibly proprietary content)
- User accounts + comments (PII)
- Viewing history (depending on settings)
7. External dependencies¶
- Storage backend (MinIO / external S3)
- SMTP for account email
- Possibly Authentik for SSO
8. Authentication & access¶
[INFO NEEDED]
9. Maturity assessment¶
[INFO NEEDED]
10. Known risks & vulnerabilities¶
[INFO NEEDED]Storage growth — videos grow fast; disk-full = service-down.[INFO NEEDED]No backup of video files — backups can be cost-prohibitive at scale; common pitfall is to back up DB but not videos.[INFO NEEDED]Public visibility settings — videos meant to be private accidentally listed publicly.[INFO NEEDED]Federation — PeerTube federates by default; if open, content auto-mirrors elsewhere.[INFO NEEDED]Bandwidth / abuse — public video service is a bandwidth-DoS target.
11. Impact if it goes down¶
[INFO NEEDED] — depends on use case.
12. Owner & on-call¶
[INFO NEEDED]
13. References & links¶
- Public URL: https://videos.448.global
- PeerTube docs: https://docs.joinpeertube.org
- Likely storage: MinIO
- Domain: see domains.md