Infrastructure and data
You provide the server, public HTTPS origin, database, media storage, monitoring, secrets, and access controls. You decide where OpenPost data is stored and who can administer it.
Self-hosted deployment
Your server. Your data. The same OpenPost.
Run the complete AGPL-licensed product on infrastructure you control. You choose the data location and deployment settings, and you own the operating work described below.
For operators who want to run OpenPost on infrastructure they control.
Operating responsibility
Know what you take on before you deploy.
Upgrades and backups
You track releases and security notices, schedule upgrades, and back up the database, media, and required secrets together. Test restores before relying on those backups.
Provider projects
You create and maintain social network projects, callback URLs, permissions, reviews, and API budgets. OpenPost still sends requested content and access tokens to those networks.
Support boundary
OpenPost publishes documentation, source, issues, and community help. You operate the service, support its users, respond to incidents, and maintain the privacy and retention practices for your deployment.
One product
The deployment changes. The publishing model does not.
The Hosted service and a self-hosted deployment use the same OpenPost code and product terms. Hosted plan limits and operated services do not become part of your installation.
- One Go service with the SvelteKit app embedded
- SQLite and local media by default
- PostgreSQL and S3-compatible media options
- Database-backed scheduling without required Redis
- The same Publication, Rendition, Workspace, API, CLI, and MCP model
Start with the production checklist.
The documentation covers installation, configuration, provider projects, backups, health checks, logs, upgrades, and troubleshooting. Review the complete path before exposing an instance to users.