
# Document management on Hostinger

Compare documented Document management deployments on Hostinger, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/hostinger/document-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Hostinger account and VPS
- Provider group: vps-hosting
- Provider classification: The documented route uses a customer VPS and application administrator; the hosting provider operates its physical infrastructure. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-20).
- Network: Customer server networking, DNS and firewall rules
- Identity and access: Cloud account access, server root/SSH access and application administrators
- Installation guidance: Provision the documented Cloudron VPS template in your account, complete domain and administrator setup, then install and operate the reviewed application package.
- Guidance source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
- Guidance reviewed: 2026-11-13


### VPS hardening

The provider recommends SSH hardening, firewall configuration and patching for VPS hosts. A preinstalled application template does not transfer these operating responsibilities away from the customer.
Source: https://www.hostinger.com/tutorials/vps-security/ (reviewed 2026-11-14).

The listings below have evidence for Hostinger. Read each cloud evidence note for the applicable package, edition and support qualifications.

12 listings.


## Apache JSPWiki

Apache file-based wiki for documentation and knowledge content.

- Listing: https://launchinyourcloud.com/directory/apache-jspwiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: JSPWiki Java application, persistent page files and attachments.
- Operations: 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.
- Product website: https://jspwiki.apache.org/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current repository maintenance is distinct from the older GitHub release snapshot; validate the chosen Tomcat/Java and wiki version combination.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

JSPWiki Java application, persistent page files and attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Apache file-based wiki for documentation and knowledge content.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/apache-jspwiki (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/apache-jspwiki
  JSPWiki Java application, persistent page files and attachments. Current repository maintenance is distinct from the older GitHub release snapshot; validate the chosen Tomcat/Java and wiki version combination.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes juanpablo-santos, ajaquith, spyhunter99, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/apache/jspwiki/graphs/contributors

- Upstream project: https://github.com/apache/jspwiki

### Sources

- Hostinger: https://www.hostinger.com/applications/apache-jspwiki

- Apache-2.0 LICENSE: https://raw.githubusercontent.com/apache/jspwiki/master/LICENSE

- GitHub Releases: https://github.com/apache/jspwiki/releases

- Official upstream releases: https://jspwiki.apache.org/

### Licensing sources

- https://raw.githubusercontent.com/apache/jspwiki/master/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/apache-jspwiki


### Buyer diligence


Research coverage: 5/12 fields (42%); 2 documented, 3 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The upstream documentation establishes JAAS and servlet-container security integration, but this review did not establish a complete version-matched external SAML/OIDC user-login configuration for JSPWiki 3.0. Generic Java/container authentication alone is not proof of a supported federation path. Scope: Apache JSPWiki application user federation; optional login modules and external servlet/proxy integration require specific evidence. Source: https://github.com/apache/jspwiki/blob/master/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. JSPWiki documents WAR/container installation, but the current Apache index exposes a 3.0.1 distribution while the project homepage still announces 3.0.0. This review did not reconcile the current release status and exact production binary selection. Verify the announcement, package/checksums and servlet compatibility rather than assuming an archived package or provider image is current. Scope: JSPWiki upstream artifact/release-channel reconciliation; the documented self-hosted installation path remains established. Source: https://downloads.apache.org/jspwiki/ (reviewed 2026-11-20). Deployment artifact: https://downloads.apache.org/jspwiki/. Artifact reference: Mutable Apache distribution index; observed 3.0.1 directory is not used to invent a publication date. Supporting source: Project release announcements — https://jspwiki.apache.org/. Supporting source: Observed versioned binary directory — https://downloads.apache.org/jspwiki/3.0.1/binaries/. Supporting source: Application installation and runtime requirements — https://github.com/apache/jspwiki/blob/master/README.md.

- Minimum footprint / sizing: Sources checked — unresolved. The installation README specifies Java and servlet-container prerequisites but does not establish a quantitative whole-host CPU/RAM/storage minimum. Size the wiki content, attachments, search/indexing, runtime and replicas for the intended use rather than treating Java heap settings as host capacity. Scope: JSPWiki 3.0 application/container deployment; quantitative production and HA sizing remains unconfirmed. Source: https://github.com/apache/jspwiki/blob/master/README.md (reviewed 2026-11-20).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Apache JSPWiki; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/apache/jspwiki/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The official site announces JSPWiki 3.0.0 and maintained-line 2.12.5 on August 22, 2026. GitHub Releases does not list all current Apache distributions; check Java/Tomcat and plugin compatibility. Scope: Official Apache upstream application releases, not the provider image. Source: https://jspwiki.apache.org/ (reviewed 2026-11-19).







## Docassemble

Self-hosted guided interviews and automated document assembly.

- Listing: https://launchinyourcloud.com/directory/docassemble/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: Docassemble Docker application, database, persistent interviews and generated documents.
- Operations: 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.
- Product website: https://docassemble.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor explicitly recommends AWS EC2. Azure Blob integration is storage evidence only, not Azure application hosting; interview authors must validate legal content and external integrations.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Docassemble Docker application, database, persistent interviews and generated documents. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted guided interviews and automated document assembly.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/docassemble (checked 2026-11-19). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docassemble.org/docs/installation.html (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/docassemble
  Docassemble Docker application, database, persistent interviews and generated documents. The vendor explicitly recommends AWS EC2. Azure Blob integration is storage evidence only, not Azure application hosting; interview authors must validate legal content and external integrations.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Docassemble EC2 Docs (aws): https://docassemble.org/docs/installation.html
  Docassemble Docker application, database, persistent interviews and generated documents. The vendor explicitly recommends AWS EC2. Azure Blob integration is storage evidence only, not Azure application hosting; interview authors must validate legal content and external integrations.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jhpyle, jpylephilalegal, BryceStevenWilley, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/jhpyle/docassemble/graphs/contributors

- Upstream project: https://github.com/jhpyle/docassemble

### Sources

- Hostinger: https://www.hostinger.com/applications/docassemble

- Docassemble EC2 Docs: https://docassemble.org/docs/installation.html

- MIT LICENSE.txt: https://raw.githubusercontent.com/jhpyle/docassemble/master/LICENSE.txt

- GitHub Releases: https://github.com/jhpyle/docassemble/releases

### Licensing sources

- https://raw.githubusercontent.com/jhpyle/docassemble/master/LICENSE.txt

### Infrastructure sources

- https://www.hostinger.com/applications/docassemble

- https://docassemble.org/docs/installation.html


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The server documents external OAuth sign-in with providers including Auth0, Keycloak, Authentik and Azure. Configure each provider and account-linking/admin policies. The guide warns that external authentication affects its optional server-side answer-encryption model. Scope: Self-hosted server external authentication. Source: https://docassemble.org/docs/config.html#oauth (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project recommends the jhpyle/docassemble Docker distribution, including for production, with persistent configuration/data and optional external database or object storage. Select a versioned image and review production settings rather than using the minimal demonstration command unchanged. Scope: Official Docker distribution; infrastructure provisioning and HA not supplied by the one-line example. Source: https://docassemble.org/docs/installation.html (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/jhpyle/docassemble. Artifact reference: Select an explicit image tag for deployment.

- Minimum footprint / sizing: Documented. The project reports roughly 800–900 MB RAM during normal operation but recommends at least 4 GB because updates can use substantially more. This is a baseline server recommendation, not tested capacity for 100 users, 1 TB or HA. Scope: Upstream single-machine memory recommendation. Source: https://docassemble.org/docs/installation.html (reviewed 2026-11-20).

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Docassemble; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/jhpyle/docassemble/master/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Docspell

Self-hosted document ingestion, OCR, classification and search.

- Listing: https://launchinyourcloud.com/directory/docspell/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment; Docker / Compose
- Architecture: Docspell REST server and job executor sharing PostgreSQL and durable document storage.
- Operations: 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.
- Product website: https://docspell.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Railway recipe uses PostgreSQL full-text search rather than Solr. Joex and REST services must reach each other and use matching application versions.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Docspell REST server and job executor sharing PostgreSQL and durable document storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted document ingestion, OCR, classification and search.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/docspell (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/docspell-1 (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/docspell
  Docspell REST server and job executor sharing PostgreSQL and durable document storage. The Railway recipe uses PostgreSQL full-text search rather than Solr. Joex and REST services must reach each other and use matching application versions.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/docspell-1
  Docspell REST server and job executor sharing PostgreSQL and durable document storage. The Railway recipe uses PostgreSQL full-text search rather than Solr. Joex and REST services must reach each other and use matching application versions.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes eikek, scala-steward, eikek-scala-steward, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/eikek/docspell/graphs/contributors

- Upstream project: https://github.com/eikek/docspell

### Sources

- Hostinger: https://www.hostinger.com/applications/docspell

- Railway: https://railway.com/deploy/docspell-1

- AGPL-3.0 LICENSE.txt: https://raw.githubusercontent.com/eikek/docspell/master/LICENSE.txt

- GitHub Releases: https://github.com/eikek/docspell/releases

### Licensing sources

- https://raw.githubusercontent.com/eikek/docspell/master/LICENSE.txt

### Infrastructure sources

- https://www.hostinger.com/applications/docspell

- https://railway.com/deploy/docspell-1


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The upstream server supports OIDC/OAuth2 sign-in using a configured external provider; multiple providers are supported and Keycloak configuration is documented. Configure registration, collective mapping and provider settings for the selected release. Scope: Self-hosted Docspell REST server authentication. Source: https://docspell.org/docs/configure/authentication/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project maintains a Compose deployment for the REST server, job executor, PostgreSQL and full-text search. Change the documented secrets, persist data and pin compatible image versions; moving latest/nightly tags are not immutable releases. Scope: Upstream Compose deployment; single-machine default, not HA. Source: https://docspell.org/docs/install/docker/ (reviewed 2026-11-20). Deployment artifact: https://github.com/docspell/docker/tree/master/docker-compose. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. The project recommends 4 GB RAM for a small board running Joex with its database and Solr, with Joex pool size 1. Its example 1-CPU/4-GB VM is a processing illustration, not validated 100-user, 1-TB or HA capacity; OCR languages and classification affect memory. Scope: Upstream low-resource example; not production/HA workload sizing. Source: https://docspell.org/docs/install/rpi/ (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Docspell; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/eikek/docspell/master/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v0.43.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Docspell upstream application; verify compatibility with the selected package. Source: https://github.com/eikek/docspell/releases/tag/v0.43.0 (reviewed 2026-11-19).







## eLabFTW

Open-source electronic laboratory notebook for tracked experiments, procedures and attached records.

- Listing: https://launchinyourcloud.com/directory/elabftw/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: eLabFTW application containers, database and persistent uploaded records on a customer VPS.
- Operations: 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.
- Product website: https://www.elabftw.net
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Verify the actual provider image and current upstream security fixes. Laboratory record controls are not an automatic clinical-validation, GLP or regulatory-certification claim; institutional procedures and supported dependencies remain separate.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

eLabFTW application containers, database and persistent uploaded records on a customer VPS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Open-source electronic laboratory notebook for tracked experiments, procedures and attached records.

- clinical-regulatory-document-management: Open-source electronic laboratory notebook for tracked experiments, procedures and attached records.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/elabftw (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger VPS (hostinger): https://www.hostinger.com/applications/elabftw
  eLabFTW application containers, database and persistent uploaded records on a customer VPS. Verify the actual provider image and current upstream security fixes. Laboratory record controls are not an automatic clinical-validation, GLP or regulatory-certification claim; institutional procedures and supported dependencies remain separate.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes NicolasCARPi, MoustaphaCamara, MarcelBolten, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/elabftw/elabftw/graphs/contributors

- Upstream project: https://github.com/elabftw/elabftw

### Sources

- Hostinger VPS: https://www.hostinger.com/applications/elabftw

- AGPL-3.0: https://github.com/elabftw/elabftw/blob/master/LICENSE

- Releases: https://github.com/elabftw/elabftw/releases

### Licensing sources

- https://github.com/elabftw/elabftw/blob/master/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/elabftw


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The system-administrator guide documents SAML user sign-in with one or more identity providers, separately from LDAP and trusted-header external authentication. Account-creation and local-login settings control how users are admitted. Configure the chosen IdP and team mapping for the selected release. Scope: Self-hosted eLabFTW SAML login; LDAP, local login and middleware-header paths are distinct. Source: https://doc.elabftw.net/docs/install/post-install/authentication/saml (reviewed 2026-11-20). Supporting source: Authentication and account policies — https://doc.elabftw.net/sysadmin-guide.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The version-6 installation guide uses the official elabctl management script or a downloadable Docker Compose configuration, then separate configuration/TLS/start steps. The default includes MySQL; the current guide explicitly distinguishes it from MariaDB. Configure secrets, durable data, backups and matching application/database versions. Scope: eLabFTW version-6 container installation path; provision the host and production operations separately. Source: https://github.com/elabftw/elabftw/blob/release/6.0/documentation/docs/install/installation/1-elabctl.md (reviewed 2026-11-20). Deployment artifact: https://get.elabftw.net/. Artifact reference: Official elabctl/configuration download URL is unversioned; guide branch release/6.0 is moving. Supporting source: Runtime and database prerequisites — https://doc.elabftw.net/docs/install/prerequisites.

- Minimum footprint / sizing: Sources checked — unresolved. The current prerequisites identify a 64-bit Linux container host and a MySQL-backed stack, but do not establish a quantitative whole-host CPU/RAM/storage minimum for this laboratory workload. Attachments, database growth, backups, integrations and replicas require a version- and workload-specific design. Scope: eLabFTW application, database and persistent experiment data; container/package allowances are not whole-system HA sizing. Source: https://doc.elabftw.net/docs/install/prerequisites (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: eLabFTW; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/elabftw/elabftw/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 6.0.10 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: eLabFTW upstream application; verify compatibility with the selected package. Source: https://github.com/elabftw/elabftw/releases/tag/6.0.10 (reviewed 2026-11-19).







## Joplin Server

Personal-use self-hosted synchronization server for Joplin notes.

- Listing: https://launchinyourcloud.com/directory/joplin-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization.
- Licensing model: source-available
- Installation: Cloudron package; Docker / Compose
- Architecture: Joplin Server, database and persistent attachment storage.
- Operations: 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.
- Product website: https://joplinapp.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization.

Joplin Server, database and persistent attachment storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Personal-use self-hosted synchronization server for Joplin notes.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/joplin-server.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/joplin-server.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/joplin-server.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/joplin-server.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/joplin-server.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/joplin-server.html (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/joplin-server.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Cloudron Store: https://www.cloudron.io/store/joplin-server.html

- Hostinger: https://www.hostinger.com/applications/joplin-server

- Joplin Server Personal Use License: https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md

- GitHub Releases: https://github.com/laurent22/joplin/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md

### Infrastructure sources

- https://www.cloudron.io/store/joplin-server.html


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. 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. Scope: Self-hosted Joplin Server SAML; supported clients, session policy and business licensing must be checked. Source: https://joplinapp.org/help/apps/server/saml/ (reviewed 2026-11-20). Supporting source: Server Business and self-hosted licensing context — https://joplinapp.org/help/apps/joplin_server_business/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Joplin Server application plus separately provisioned production database and persistent content storage. Source: https://github.com/laurent22/joplin/blob/dev/packages/server/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/laurent22/joplin/blob/dev/docker-compose.server.yml. Artifact reference: dev (moving branch); use a compatible published server image tag.

- Minimum footprint / sizing: Documented. 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. Scope: Joplin Server Business self-hosted baseline; provider-package allocations, external content storage and redundancy are separate. Source: https://joplinapp.org/help/apps/joplin_server_business/ (reviewed 2026-11-20). Supporting source: Previously reviewed Cloudron app package allocation — https://www.cloudron.io/store/joplin-server.html.

- License pricing: Edition-dependent. Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization. Scope: Joplin Server; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Memos

Self-hosted lightweight notes, documents and knowledge timeline.

- Listing: https://launchinyourcloud.com/directory/memos/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment; Docker / Compose
- Architecture: Memos application, SQLite database and attachment storage.
- Operations: 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.
- Product website: https://usememos.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron, Hostinger and Railway packages have distinct upgrade cycles. Multi-user notes do not establish a regulated document-retention system.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Memos application, SQLite database and attachment storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted lightweight notes, documents and knowledge timeline.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/memos-3 (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/memos.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/memos-3
  Memos application, SQLite database and attachment storage. Cloudron, Hostinger and Railway packages have distinct upgrade cycles. Multi-user notes do not establish a regulated document-retention system. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes boojack, johnnyjoygh, athurg, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/usememos/memos/graphs/contributors

- Upstream project: https://github.com/usememos/memos

### Sources

- Cloudron Store: https://www.cloudron.io/store/memos.html

- Railway: https://railway.com/deploy/memos-3

- Hostinger: https://www.hostinger.com/applications/memos

- MIT LICENSE: https://raw.githubusercontent.com/usememos/memos/main/LICENSE

- GitHub Releases: https://github.com/usememos/memos/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://raw.githubusercontent.com/usememos/memos/main/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/memos.html

- https://railway.com/deploy/memos-3


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Memos documents external OAuth2/SSO providers separately from local passwords and API tokens. Providers map a stable external identity to a local user; account linking and registration policy control admission. Password login can be disabled for regular users while retaining an admin recovery path. Scope: Self-hosted Memos current authentication configuration; verify compatibility with the installed release and any provider package. Source: https://usememos.com/docs/configuration/authentication (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official deployment guide provides a Docker container with persistent application data; its README also links Compose, Kubernetes and binary options. Choose a published version and compatible database/configuration, then configure HTTPS, backups and instance authentication. Scope: Self-hosted Memos application/data deployment; not a complete HA cloud stack. Source: https://usememos.com/docs/deploy/docker (reviewed 2026-11-20). Deployment artifact: https://github.com/usememos/memos. Artifact reference: main (moving branch); 26.11.1 release snapshot is recorded separately.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/memos.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Memos; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/usememos/memos/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 26.11.1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Memos upstream application; verify compatibility with the selected package. Source: https://github.com/usememos/memos/releases/tag/26.11.1 (reviewed 2026-11-19).







## Papermerge DMS

Self-hosted scanned-document management, OCR and metadata repository.

- Listing: https://launchinyourcloud.com/directory/papermerge/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: Papermerge application, database, processing workers and persistent documents.
- Operations: 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.
- Product website: https://papermerge.dev
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

OCR and preview processing add compute and temporary storage; a base provider template is not a capacity plan for a 1 TB HA repository.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Papermerge application, database, processing workers and persistent documents. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted scanned-document management, OCR and metadata repository.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/papermerge (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/papermerge
  Papermerge application, database, processing workers and persistent documents. OCR and preview processing add compute and temporary storage; a base provider template is not a capacity plan for a 1 TB HA repository.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes ciur, dl3sm, bl1nkker, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/papermerge/papermerge-core/graphs/contributors

- Upstream project: https://github.com/papermerge/papermerge-core

### Sources

- Hostinger: https://www.hostinger.com/applications/papermerge

- Apache-2.0 LICENSE: https://raw.githubusercontent.com/papermerge/papermerge-core/master/LICENSE

- GitHub Releases: https://github.com/papermerge/papermerge-core/releases

### Licensing sources

- https://raw.githubusercontent.com/papermerge/papermerge-core/master/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/papermerge


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The 3.5 documentation describes OIDC sign-in, with Keycloak and Authentik examples, plus a separately configured remote-user option. Configure the identity provider and token/group mapping; do not trust unfiltered public headers. Scope: Papermerge DMS 3.5 self-hosted OIDC. Source: https://docs.papermerge.io/3.5/sso/oidc/overview/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes Compose YAML for PostgreSQL, persistent media and optional OCR, S3 and indexing workers. Examples pin the web image to 3.5.3; replace sample secrets and reconcile component versions before production. SQLite examples are demos. Scope: Papermerge 3.5 progressive Compose examples; not a complete HA architecture. Source: https://docs.papermerge.io/3.5/setup/docker-compose/ (reviewed 2026-11-20). Deployment artifact: https://docs.papermerge.io/3.5/setup/docker-compose/#persistent-media-storage. Artifact reference: 3.5 documentation; example web image 3.5.3.

- Minimum footprint / sizing: Documented. The vendor gives 1 GB RAM as the absolute minimum for the web application alone. Database, OCR, indexing, other workers and Kubernetes require additional resources; this is not the full application or HA footprint. Scope: Papermerge 3.5 web-only minimum; optional services and production capacity excluded. Source: https://docs.papermerge.io/3.5/setup/requirements/ (reviewed 2026-11-20).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Papermerge DMS; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/papermerge/papermerge-core/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 3.5.3 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Papermerge DMS upstream application; verify compatibility with the selected package. Source: https://github.com/papermerge/papermerge-core/releases/tag/3.5.3 (reviewed 2026-11-19).







## SilverBullet

Self-hosted Markdown note and personal knowledge workspace.

- Listing: https://launchinyourcloud.com/directory/silverbullet/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: SilverBullet server with persistent Markdown documents and local metadata.
- Operations: 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.
- Product website: https://silverbullet.md
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

A browser offline/PWA mode does not establish a disconnected production deployment. Review any installed plugs and external AI integrations.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

SilverBullet server with persistent Markdown documents and local metadata. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted Markdown note and personal knowledge workspace.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/silverbullet (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/silverbullet
  SilverBullet server with persistent Markdown documents and local metadata. A browser offline/PWA mode does not establish a disconnected production deployment. Review any installed plugs and external AI integrations.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes zefhemel, mjf, MrMugame, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/silverbulletmd/silverbullet/graphs/contributors

- Upstream project: https://github.com/silverbulletmd/silverbullet

### Sources

- Hostinger: https://www.hostinger.com/applications/silverbullet

- MIT LICENSE.md: https://raw.githubusercontent.com/silverbulletmd/silverbullet/main/LICENSE.md

- GitHub Releases: https://github.com/silverbulletmd/silverbullet/releases

### Licensing sources

- https://raw.githubusercontent.com/silverbulletmd/silverbullet/main/LICENSE.md

### Infrastructure sources

- https://www.hostinger.com/applications/silverbullet


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The published 2.12.1 documentation supports OIDC in account-managed multi-server mode. Administrators provision accounts and assign spaces; the IdP must supply a stable subject and verified email. Legacy single-space credentials and an authentication proxy are separate modes, not equivalent per-user SSO configurations. Scope: SilverBullet 2.12.1 account-managed server; provider configuration and local administrator recovery access required. Source: https://github.com/silverbulletmd/silverbullet/blob/2.12.1/docs/Single%20Sign-On.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide supplies a Compose deployment with a persistent data directory and versioned GHCR/Docker Hub images. Select a stable release rather than the moving edge/v2 channel, and configure the chosen account/authentication mode, HTTPS and backups. Scope: Self-hosted SilverBullet container and persistent server data; not a cloud/HA template. Source: https://silverbullet.md/Install/Docker (reviewed 2026-11-20). Deployment artifact: https://github.com/silverbulletmd/silverbullet/pkgs/container/silverbullet. Artifact reference: 2.12.1 published source reviewed; select its corresponding versioned image instead of latest/edge.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed Docker/configuration guides establish persistent server data and authentication modes but do not specify a quantitative whole-host CPU/RAM/storage floor. Library size, indexing, attached files, browser/runtime features and concurrent spaces must be sized for the selected release. Scope: SilverBullet server and data workload; a small binary/container is not a production or HA sizing guarantee. Source: https://silverbullet.md/Install/Docker (reviewed 2026-11-20). Supporting source: Server modes and configuration — https://silverbullet.md/Install/Configuration.

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: SilverBullet; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/silverbulletmd/silverbullet/main/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 2.12.1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: SilverBullet upstream application; verify compatibility with the selected package. Source: https://github.com/silverbulletmd/silverbullet/releases/tag/2.12.1 (reviewed 2026-11-19).







## SiYuan

Self-hosted personal knowledge base and block-based note application.

- Listing: https://launchinyourcloud.com/directory/siyuan/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: SiYuan server and persistent workspace files.
- Operations: 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.
- Product website: https://b3log.org/siyuan
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Release candidates must be separated from stable versions. Optional AI, synchronization and paid services change the external data flow; browser offline use is not air-gapped server support.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

SiYuan server and persistent workspace files. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted personal knowledge base and block-based note application.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/siyuan (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/siyuan
  SiYuan server and persistent workspace files. Release candidates must be separated from stable versions. Optional AI, synchronization and paid services change the external data flow; browser offline use is not air-gapped server support.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes 88250, Vanessa219, TCOTC, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/siyuan-note/siyuan/graphs/contributors

- Upstream project: https://github.com/siyuan-note/siyuan

### Sources

- Hostinger: https://www.hostinger.com/applications/siyuan

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/siyuan-note/siyuan/master/LICENSE

- GitHub Releases: https://github.com/siyuan-note/siyuan/releases

### Licensing sources

- https://raw.githubusercontent.com/siyuan-note/siyuan/master/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/siyuan


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. SiYuan v3.8.11 documents Docker access through OpenID Connect, with Google, Microsoft and custom OIDC providers plus a separate GitHub OAuth adapter. Accepted identities receive SiYuan administrator access to the workspace; configure claim rules rather than assuming separate per-user roles or private workspaces. Scope: SiYuan v3.8.11 server workspace access; not a general multi-tenant collaboration or SCIM claim. Source: https://github.com/siyuan-note/siyuan/blob/v3.8.11/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The published v3.8.11 README documents Docker and Kubernetes deployment with a persistent workspace and explicit access authentication. The example uses b3log/siyuan; select a compatible image version, correct host ownership, credentials and a public HTTPS/OIDC callback configuration. Scope: Self-hosted SiYuan application/workspace; container deployment is not an HA infrastructure design. Source: https://github.com/siyuan-note/siyuan/blob/v3.8.11/README.md (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/b3log/siyuan. Artifact reference: v3.8.11 source instructions; example image tag is not pinned.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed server-deployment instructions describe workspace persistence and authentication but do not establish a quantitative whole-host CPU/RAM/storage minimum for the chosen library and workload. Desktop package size or container start-up alone would not establish team/HA capacity. Scope: SiYuan server/workspace and its data, search/indexing and backups; quantitative production sizing remains unconfirmed. Source: https://github.com/siyuan-note/siyuan/blob/v3.8.11/README.md (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: SiYuan; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/siyuan-note/siyuan/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Teedy (Sismics Docs)

Self-hosted document repository with OCR, search and access controls.

- Listing: https://launchinyourcloud.com/directory/teedy/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: Teedy application, database and durable document storage.
- Operations: 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.
- Product website: https://teedy.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The published 1.11 release date and recent source activity are separate facts; do not present a source commit as a new stable release or support commitment. Verify that the installed Teedy image contains the reviewed source fixes, or obtain a fixed build; do not assume the old stable tag includes later commits.

GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Teedy application, database and durable document storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted document repository with OCR, search and access controls.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/teedy (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/teedy
  Teedy application, database and durable document storage. The published 1.11 release date and recent source activity are separate facts; do not present a source commit as a new stable release or support commitment.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jendib, naku, vmario89, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/sismics/docs/graphs/contributors

- Upstream project: https://github.com/sismics/docs

### Sources

- Hostinger: https://www.hostinger.com/applications/teedy

- GPL-2.0 COPYING: https://raw.githubusercontent.com/sismics/docs/master/COPYING

- GitHub Commits: https://github.com/sismics/docs/commits/master

- Teedy source-branch authorization and input fixes: https://github.com/sismics/docs/commit/c188971e72d2595b5d0cc1fcab980bca0b42ea89

### Licensing sources

- https://raw.githubusercontent.com/sismics/docs/master/COPYING

### Infrastructure sources

- https://www.hostinger.com/applications/teedy


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The upstream feature list documents LDAP and two-factor authentication, but the reviewed installation/configuration reference does not establish a supported SAML or OIDC sign-on workflow. LDAP login alone is not evidence of federated SSO. Scope: Self-hosted upstream edition; federation protocol and support scope unresolved. Source: https://raw.githubusercontent.com/sismics/docs/master/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream README includes a Docker Compose application/PostgreSQL stack and persistent volumes. It pins the example application to v1.11; reconcile it with the chosen maintained release and replace example credentials before production. Embedded H2 is evaluation-only. Scope: Upstream Compose example, not a hardened or HA template. Source: https://raw.githubusercontent.com/sismics/docs/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/sismics/docs/blob/master/README.md#examples. Artifact reference: master (moving branch; example image v1.11).

- Minimum footprint / sizing: Sources checked — unresolved. The upstream recipe identifies the application, OCR/conversion tools, PostgreSQL and persistent storage, but does not specify a CPU/RAM minimum or validated workload sizing. Obtain a workload-specific recommendation before choosing production capacity. Scope: Upstream production components; numeric sizing unresolved. Source: https://raw.githubusercontent.com/sismics/docs/master/README.md (reviewed 2026-11-20).

- License pricing: Documented. GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Teedy (Sismics Docs); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/sismics/docs/master/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v1.11 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Teedy (Sismics Docs) upstream application; verify compatibility with the selected package. Source: https://github.com/sismics/docs/releases/tag/v1.11 (reviewed 2026-11-19).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Teedy source-branch authorization and input fixes (security-advisory): Recent upstream source commits correct LDAP filter escaping, active-content rendering and file write-permission checks. Scope: Reviewed main-branch fixes in October–November 2026; the older v1.11 GitHub release does not establish a release containing them. Conditions: LDAP configuration, uploaded active content and file operations have separate conditions; check the installed image’s actual commits. Action: Verify that the installed Teedy image contains the reviewed source fixes, or obtain a fixed build; do not assume the old stable tag includes later commits. Source: https://github.com/sismics/docs/commit/c188971e72d2595b5d0cc1fcab980bca0b42ea89; reviewed 2026-11-19. Supporting source: LDAP escaping correction — https://github.com/sismics/docs/commit/b928f5d376479db5c7b3750fb84c25ba0b69f09d. Supporting source: Active-content rendering correction — https://github.com/sismics/docs/commit/2337d43d8d34b596cff3b0deb0c4bbd0caea2584.




## TriliumNext Notes

Self-hosted hierarchical personal notes and document knowledge base.

- Listing: https://launchinyourcloud.com/directory/triliumnext-notes/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package
- Architecture: TriliumNext server with persistent database and attachments.
- Operations: 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.
- Product website: https://triliumnotes.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The server is primarily a single-user knowledge base; published notes and sharing do not establish a multi-user enterprise collaboration suite.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

TriliumNext server with persistent database and attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted hierarchical personal notes and document knowledge base.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/triliumnext-notes.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/triliumnext-notes.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/triliumnext-notes.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/triliumnext-notes.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/triliumnext-notes.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/triliumnext-notes.html (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/triliumnext-notes.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes eliandoran, zadam, adoriandoran, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/TriliumNext/Trilium/graphs/contributors

- Upstream project: https://github.com/TriliumNext/Trilium

### Sources

- Cloudron Store: https://www.cloudron.io/store/triliumnext-notes.html

- AGPL-3.0 LICENSE: https://github.com/TriliumNext/Trilium/blob/main/LICENSE

- Releases v0.107.0: https://github.com/TriliumNext/Trilium/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/TriliumNext/Trilium/blob/main/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/triliumnext-notes.html


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. TriliumNext documents external OpenID Connect login and links the integration from its published v0.107.0 README. OIDC replaces the local web password login and delegates MFA to the provider. Configure the identity accepted by this personal-notes instance; this does not make it a multi-tenant team repository. Scope: TriliumNext v0.107.0 server authentication; verify the packaged server version and provider algorithm/settings. Source: https://github.com/TriliumNext/Trilium/blob/v0.107.0/README.md (reviewed 2026-11-20). Supporting source: OpenID Connect configuration — https://docs.triliumnotes.org/user-guide/setup/server/openid-connect.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project publishes Docker images and Compose instructions with a persistent Trilium data directory. Select a version matching the desktop/sync clients rather than automatically following latest; configure proxy/authentication, ownership, backups and upgrades for the installed server. Scope: TriliumNext self-hosted server; upstream and Cloudron package versions/allocations are separate. Source: https://docs.triliumnotes.org/user-guide/setup/server/installation/docker (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/triliumnext/trilium. Artifact reference: v0.107.0 upstream source reviewed; choose its matching published image tag, not an unpinned latest upgrade.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/triliumnext-notes.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: TriliumNext Notes; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/TriliumNext/Trilium/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v0.107.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: TriliumNext Notes upstream application; verify compatibility with the selected package. Source: https://github.com/TriliumNext/Trilium/releases/tag/v0.107.0 (reviewed 2026-11-19).







## XWiki

Self-hosted enterprise wiki and structured knowledge application platform.

- Listing: https://launchinyourcloud.com/directory/xwiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU LGPL-2.1 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment; Docker / Compose
- Architecture: XWiki application, PostgreSQL, persistent files and search components.
- Operations: 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.
- Product website: https://www.hostinger.com/applications/xwiki
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Railway recipe pins XWiki 18.9.0; upstream 17.10 LTS maintenance releases have a separate release line. Run the Distribution Wizard and validate extensions when upgrading.

GNU LGPL-2.1 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

XWiki application, PostgreSQL, persistent files and search components. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted enterprise wiki and structured knowledge application platform.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/xwiki (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/xwiki-1 (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/xwiki
  XWiki application, PostgreSQL, persistent files and search components. The Railway recipe pins XWiki 18.9.0; upstream 17.10 LTS maintenance releases have a separate release line. Run the Distribution Wizard and validate extensions when upgrading.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/xwiki-1
  XWiki application, PostgreSQL, persistent files and search components. The Railway recipe pins XWiki 18.9.0; upstream 17.10 LTS maintenance releases have a separate release line. Run the Distribution Wizard and validate extensions when upgrading.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes tmortagne, vmassol, mflorea, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/xwiki/xwiki-platform/graphs/contributors

- Upstream project: https://github.com/xwiki/xwiki-platform

### Sources

- Hostinger: https://www.hostinger.com/applications/xwiki

- Railway: https://railway.com/deploy/xwiki-1

- LGPL-2.1 LICENSE: https://raw.githubusercontent.com/xwiki/xwiki-platform/master/LICENSE

- GitHub Releases: https://github.com/xwiki/xwiki-platform/releases

### Licensing sources

- https://raw.githubusercontent.com/xwiki/xwiki-platform/master/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/xwiki

- https://railway.com/deploy/xwiki-1


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The OpenID Connect Authenticator extension provides OIDC sign-in and synchronization. It is installed through Extension Manager, is LGPL-2.1 licensed, and requires XWiki 14.10.2 or later; commercial support is separate. Scope: XWiki with separately installed OIDC Authenticator extension. Source: https://extensions.xwiki.org/xwiki/bin/view/Extension/OpenID%20Connect/OpenID%20Connect%20Authenticator/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Official installation options include a production-capable Docker image, Debian packages or a WAR distribution. Production requires a supported database, persistent application data and compatible Java/container versions; the standalone HSQLDB demo is not the production baseline. Scope: Official XWiki distribution options. Source: https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/ (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/_/xwiki. Artifact reference: Select an explicit compatible image tag; no artifact is installed by this review.

- Minimum footprint / sizing: Documented. The Tiny guideline is 2 CPU cores, 2 GB RAM and 5 GB disk for up to 25 active users; Small is 2 cores, 4 GB and 20 GB for up to 250. These single-machine application/database profiles depend on document and request volume and do not establish HA or 1-TB capacity. Scope: Upstream single-machine sizing profiles; workload dimensions must all be checked. Source: https://www.xwiki.org/xwiki/bin/view/documentation/xs/admin/installation/xwiki-instance-sizing/ (reviewed 2026-11-20).

- License pricing: Documented. GNU LGPL-2.1 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: XWiki; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/xwiki/xwiki-platform/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream xwiki-platform-17.10.15 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: XWiki upstream application; verify compatibility with the selected package. Source: https://github.com/xwiki/xwiki-platform/releases/tag/xwiki-platform-17.10.15 (reviewed 2026-11-19).






