Does Worklist offer self-hosting?
Yes. Worklist Self-hosted is available as a licensed Docker image for teams that want to run Worklist on their own infrastructure.
What it is
Yes, Worklist offers a self-hosted option. It is a paid, licensed Docker distribution for customer-operated infrastructure. It is not an open-source edition. Self-hosted is $11.99 per seat per month, sold on a 12-month minimum contract with a 5-seat minimum.
Common questions
Is Worklist Self-hosted open source?
No. Worklist Self-hosted is not an open-source edition. Worklist publishes cryptographic implementation and decryption tooling on GitHub, but the self-hosted product distribution is licensed commercially.
How is Worklist Self-hosted priced?
Self-hosted pricing is $11.99 per seat per month, billed on a 12-month minimum contract. The minimum self-hosted purchase is 5 seats, so the annual minimum starts at $143.88 per seat per year before tax. For hosted plans, Personal pricing is $6.90 per month or $59 per year, and Team pricing starts at $8.50 per seat per month or $85 per seat per year, with a 14-day trial and no card required.
Can Worklist staff read self-hosted workspace content?
No. Workspace content is encrypted on the client before it reaches the server. The zero-knowledge design means Worklist does not hold the keys needed to decrypt task titles, bodies, comments, checklists, list titles, or attachments.
What infrastructure does Worklist Self-hosted require?
Worklist Self-hosted is delivered as a Docker image for customer-operated infrastructure. The supplied Compose stack runs Worklist, PostgreSQL, and bundled MinIO object storage by default; teams are responsible for hosting, operations, backups, access controls, and deployment maintenance in their own environment.
Who should consider Worklist Self-hosted?
Self-hosting is for teams with infrastructure requirements, internal hosting policies, or data-residency constraints that make a customer-operated deployment preferable to the hosted Worklist cloud.
Deployment facts
Use this table to confirm the deployment, licensing, privacy, and operations boundaries before starting a self-hosted evaluation.
| Area | Current fact | What it means |
|---|---|---|
| Distribution model | Licensed Docker image plus a Compose template with PostgreSQL and bundled MinIO object storage. | Self-hosted users can inspect the default operating model before buying and operate their own deployment instead of using the hosted Worklist cloud. |
| Open-source boundary | The self-hosted product is not an open-source edition. | Open-source cryptographic tooling does not mean the full product distribution is open source. |
| Encryption model | Workspace content is encrypted on-device before upload with zero-knowledge key handling. | The same content-privacy claim applies across hosted and self-hosted deployment models. |
| Licensing model | $11.99 per seat per month, sold on a 12-month minimum contract with a 5-seat minimum. | Self-hosted uses public per-seat pricing, but it is an annual-contract product rather than a month-to-month cloud plan. |
| Operational responsibility | Customer teams run the infrastructure for the self-hosted deployment. | Hosting, backups, monitoring, network controls, and deployment maintenance belong to the customer environment. |
Deployment requirements
- Docker Engine or Docker Desktop in the customer environment.
- Persistent PostgreSQL and bundled MinIO volumes, or an operator-managed external S3-compatible object store.
- Customer-managed infrastructure, backups, monitoring, and access controls.
- 12-month minimum commercial license for at least 5 self-hosted seats.
- Security review of local network, storage, identity, and backup practices before production use.
Next steps
Install and operate self-hosted Worklist
Public operator guide covering Docker, license files, secrets, MinIO defaults, reverse proxy setup, backups, renewals, and external R2/S3 options.
Security architecture
Zero-knowledge design, server visibility, cryptographic primitives, and trade-offs.
Contact Worklist
Self-hosted inquiries, support channels, security contact, and response expectations.
Need to run Worklist yourself?
Tell us about your infrastructure requirements, seat count, and deployment constraints. We will route the self-hosted conversation to the right person.
Discuss self-hosting