Joplin Server
Personal-use self-hosted synchronization server for Joplin notes.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Cloudron package; Docker / Compose
Runs in
Documented customer environment
Joplin Server, database and persistent attachment storage.
- AWS: Customer cloud account
- DigitalOcean: Customer cloud account
- Linode: Customer cloud account
- Vultr: Customer cloud account
- Hostinger: Customer VPS account
- LumaDock: Customer VPS account
- AWS
- DigitalOcean
- Linode
- Vultr
- Hostinger
- LumaDock
Servers / containers
Operated by
Your team
Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- DigitalOcean: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- Linode: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- Vultr: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- Hostinger: Customer VPS account · Customer-operated
An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
Cloudron Store ↗ · Source checked 2026-11-19
- LumaDock: Customer VPS account · Customer-operated
An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
Cloudron Store ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Cloudron package; Docker / Compose |
|---|---|
| Infrastructure | Servers / containers Joplin Server, database and persistent attachment storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Source Available Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization. |
| License | Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
Joplin Server documents SAML user authentication using SP/IdP configuration and server environment settings. Its API and website must use the same base URL for SAML. Commercial organisational use requires the appropriate Server Business rights; this does not establish hosted Cloud plan entitlements.
Self-hosted Joplin Server SAML; supported clients, session policy and business licensing must be checked · Source ↗ · Server Business and self-hosted licensing context ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official server README provides versioned Docker images and a production PostgreSQL/Compose setup; the SQLite example is for testing. Configure public URL, database, credentials and reverse proxy before use. Select the appropriate commercial licence for an organisation.
Joplin Server application plus separately provisioned production database and persistent content storage · Source ↗ · Deployment artifact ↗ (dev (moving branch); use a compatible published server image tag) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Server Business guide lists two CPU cores/four threads, at least 4 GB RAM (8 GB recommended) and 50 GB SSD plus content growth. These are moderate-load deployment requirements, not the smaller Cloudron package allocation or a validated 100-user, 1 TB HA topology.
Joplin Server Business self-hosted baseline; provider-package allocations, external content storage and redundancy are separate · Source ↗ · Previously reviewed Cloudron app package allocation ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
Edition-dependentEvidence and scope for License pricing
Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization.
Joplin Server; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Edition-dependent · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
The Server Personal Use License permits personal non-commercial use and restricts use by business entities and commercial sharing without written permission. This is not a default option for a 100-user business deployment. Desktop/client licences and releases do not establish server rights or Server 3.7.6 publication dates.
Category fit
- Document management
- Personal-use self-hosted synchronization server for Joplin notes.
Compare within Document management
- Adobe Experience Manager 6.5 Forms (Correspondence Management)Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.
- AWS
- Azure
- Alfresco Content Services + Governance ServicesCustomer-operated content and records management with retention and record-declaration workflows.
- AWS
- Apache JSPWikiApache file-based wiki for documentation and knowledge content.
- Hostinger
- Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
- AWS
- Azure
- DocassembleSelf-hosted guided interviews and automated document assembly.
- AWS
- Hostinger
- DocspellSelf-hosted document ingestion, OCR, classification and search.
- Railway
- Hostinger
- DocuWare On-PremiseCustomer-operated document repository, email capture and document-workflow platform on Azure VMs.
- Azure
- eLabFTWOpen-source electronic laboratory notebook for tracked experiments, procedures and attached records.
- Hostinger
Showing 8 of 41 other listings in Document management. These products address related workflows; read their category-fit notes before comparing scope. See all of Document management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Cloudron Store ↗www.cloudron.io
- Hostinger ↗www.hostinger.com
- Joplin Server Personal Use License ↗raw.githubusercontent.com
- GitHub Releases ↗github.com
- Cloudron customer-server and named-provider installation ↗docs.cloudron.io
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Cloudron Store ↗ · AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock
Package platform documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.
- Cloudron Store ↗ · AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock
- Infrastructure evidenceChecked
- Licensing evidenceChecked