Skip to content

Self-Hosting Docs

Use these docs when you operate OpenPost on your own infrastructure. Self-hosting has no software fee, but it is not a Hosted service plan or a zero-price tier of the Hosted service. You pay for your infrastructure and any provider or third-party services you use.

These pages assume that you manage the server, public HTTPS origin, access controls, secrets, database, media storage, monitoring, backups, upgrades, and incident response. You also support the people who use your deployment and maintain its privacy, retention, and recovery practices.

Responsibility boundary

  • Infrastructure and data: you choose and secure the server, database, media storage, logs, network, and data locations.
  • Upgrades and backups: you track releases and security notices, apply updates, back up the database, media, and required secrets together, and test restores.
  • Provider projects: you create and maintain social network projects, callback URLs, permissions, reviews, API access, and provider budgets. OpenPost still sends requested content and access tokens to those networks.
  • Support: OpenPost publishes documentation, source code, a public issue tracker, and community help. A self-hosted operator handles deployment availability, user support, incidents, and operator-specific configuration.

Review the OpenPost source, security policy, and current releases before exposing an instance to users.

Install

Configure

Providers

Operate

Adjacent docs

  • If you only need to use the product, start with User Docs.
  • If you are changing OpenPost code, start with Developer Docs.

Open source under AGPL-3.0-only.