English
Joplin Hosting
Synchronize Joplin notes, notebooks, resources, and encrypted data through your own server.
No setup fees-
One click deploy -
2 GB RAM Memory needed -
25 GB Disk Space Needed -
From 5 € Price
Official links
Joplin’s official links and original website
Joplin Website
More
Tech
- Docker image
- joplin/server:latest
- Default port
- 22300
- Database
- postgres
How Joplin works
Joplin users create and edit notes in desktop or mobile clients, then configure those clients to synchronise through Joplin Server. The server stores account data, synchronisation objects, note resources, and sharing state in PostgreSQL and persistent storage. A change made on one connected client is uploaded and later retrieved by the others.
The hosted server is not a complete browser-based replacement for the Joplin editor. Users still need a supported Joplin application to write, organise, and read their notebooks. Administrators manage server accounts, while sharing functions let supported clients collaborate on notebooks or publish selected content according to the upstream feature set.
Key Joplin features
Joplin clients support Markdown notes, notebooks, tags, attachments, search, and synchronisation. End-to-end encryption can be enabled within the client workflow so synchronised note content is protected before reaching the server, although users must manage keys and device setup correctly.
Joplin Server provides a dedicated sync target and supports account administration and sharing. Synchronisation performance depends on item count, attachment volume, client frequency, and the number of active devices. Very large first synchronisations can take longer than routine incremental changes.
Joplin vs Evernote
Joplin with Joplin Server separates the client applications from an operator-controlled synchronisation backend. Evernote is a provider-managed note service that bundles official clients, synchronisation, search, tasks, web access, and account administration within its commercial platform.
Evernote may suit users who want the vendor to operate the complete note service and client ecosystem. Joplin is more appropriate when open client applications, Markdown-oriented notes, optional end-to-end encryption, and control of the synchronisation endpoint are higher priorities.
Who uses Joplin
Individuals keep notes synchronised between computers and phones, while small teams share selected notebooks for procedures or research. Technical users often choose it when they want Markdown, attachments, and client-side encryption without storing the entire notebook collection in a proprietary hosted note account.
The system is a poor fit for people expecting the server URL itself to provide the full editing experience. Client installation, encryption setup, conflict review, and initial synchronisation remain part of the user workflow.
Self-hosting Joplin: requirements and cost
Resource use grows with user count, note and resource volume, synchronisation frequency, shared notebooks, and simultaneous client activity. PostgreSQL stores server accounts and synchronisation records, while attachments occupy persistent application storage. The included database remains unmanaged, and the confirmed RAM rule moves the full stack above its application-only base plan.
Joplin Server has no separate hosted-application fee, and AvaHost recommends Plan 3 at €10. One-click deployment, custom-domain support, automated HTTPS, automatic application updates, and scheduled backups are included. Users must install Joplin clients and should change the seeded administrator credentials before adding regular accounts.
F.A.Q
Joplin Server starts at €10 on Plan 3 after allowing for its PostgreSQL container. The price covers the hosted synchronisation stack, custom-domain support, automated HTTPS, application updates, and scheduled backups. User count, note resources, attachment volume, shared notebooks, and client synchronisation frequency influence future capacity requirements.
The deployment creates PostgreSQL and connects Joplin Server to it automatically. Accounts, synchronisation objects, sharing records, and server configuration depend on the database, while note resources also use persistent storage. PostgreSQL is included but unmanaged, so both areas should remain coordinated during maintenance, exports, migrations, or recovery.
A custom domain can be attached to Joplin Server with automated HTTPS after DNS points to the installation. Enter that final server address in each Joplin client and test authentication and a small synchronisation before migrating every notebook. Changing the hostname later requires updating all connected devices and checking shared links.
Joplin Server is primarily a synchronisation and sharing backend, not the full Joplin note editor. Users need supported Joplin desktop or mobile applications to create and manage notebooks. The web administration area handles server accounts and service settings, so the hosting plan should not be presented as a browser-only note-taking product.