Prox OS Internal Docs
TrustTrust Safety

Self-Hosting Responsibility

Self-hosting is an important Prox OS boundary. The software can be used in operator-owned environments, but that does not make every deployment a Prox Cloud hos

Self-hosting is an important Prox OS boundary. The software can be used in operator-owned environments, but that does not make every deployment a Prox Cloud hosted service.

Operator Control

A self-hosting operator controls:

  • Domain and DNS.
  • Deployment environment.
  • Database and object storage.
  • Access policy and users.
  • Backups and retention.
  • Content moderation and operational response.
  • Local security posture.
  • Local compliance obligations.

Responsibility Boundary

Prox OS software should not be used to support illegal activity, phishing, malware, terrorism, targeted harassment, doxxing, or other platform abuse. Prox OS documentation should explain boundaries without providing evasion or unlawful operation guidance.

Responsibility Matrix

PartyResponsible ForNot Responsible For
Software authorSoftware design, documentation, defaults, security posture, and project-level trust guidance.Day-to-day operations of independent self-hosted deployments.
Self-hosting operatorDomain, hosting, database, storage, access, local users, backups, local policies, and local operational decisions.Prox Cloud hosted-content operations unless they also operate that service.
Prox Cloud operatorHosted infrastructure, access control, abuse reporting, takedown workflows, backups, privacy operations, security operations, and billing operations for Prox Cloud.Independent third-party self-hosted instances.
End userAccount behavior, content they create, workspace choices, and respect for platform rules.Platform-level enforcement systems and infrastructure operations.

On this page