
# Document management on DigitalOcean

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

Canonical page: https://launchinyourcloud.com/clouds/digitalocean/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: DigitalOcean team/account and project
- Provider group: cloud-infrastructure
- Provider classification: Droplets and managed Kubernetes use the customer infrastructure account. App Platform is a separate platform-workspace path and is identified per listing. Source: https://docs.digitalocean.com/products/droplets/how-to/create/ (checked 2026-11-20).
- Network: VPC and Cloud Firewalls; review public endpoints
- Identity and access: Team roles, scoped API tokens and SSH keys
- Installation guidance: Provision Droplets or Kubernetes in your account; review the application image, storage, updates and firewall rules.
- Guidance source: https://docs.digitalocean.com/products/droplets/how-to/create/
- Guidance reviewed: 2026-11-12


### Private networking

DigitalOcean VPCs isolate resource traffic from the public internet; VPC peering can connect VPCs. Confirm the selected service can join the intended VPC and configure application access controls.
Source: https://docs.digitalocean.com/products/networking/vpc/ (reviewed 2026-11-14).

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

5 listings.


## 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.







## LiquidFiles (Self-Hosted Virtual Appliance)

Commercial self-hosted appliance for controlled external file delivery and shared files.

- Listing: https://launchinyourcloud.com/directory/liquidfiles/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: VM image
- Architecture: LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image.
- 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://docs.liquidfiles.com/install/ec2.html
- 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 documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial self-hosted appliance for controlled external file delivery and shared files.

- data-rooms-ma-document-management: Commercial self-hosted appliance for controlled external file delivery and shared files.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.liquidfiles.com/install/ec2.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.liquidfiles.com/install/azure.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.liquidfiles.com/install/digital_ocean.html (checked 2026-11-19). 


### Cloud deployment evidence

- EC2 Guide (aws): https://docs.liquidfiles.com/install/ec2.html
  LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. The vendor documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://docs.liquidfiles.com/install/azure.html
  LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. The vendor documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- DigitalOcean Guide (digitalocean): https://docs.liquidfiles.com/install/digital_ocean.html
  LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. The vendor documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- EC2 Guide: https://docs.liquidfiles.com/install/ec2.html

- Azure Guide: https://docs.liquidfiles.com/install/azure.html

- DigitalOcean Guide: https://docs.liquidfiles.com/install/digital_ocean.html

- License Overview: https://docs.liquidfiles.com/license/overview.html

- v4.3.x Release Notes: https://docs.liquidfiles.com/release_notes/version_4-3-x.html

### Licensing sources

- https://docs.liquidfiles.com/license/overview.html

### Infrastructure sources

- https://docs.liquidfiles.com/install/ec2.html

- https://docs.liquidfiles.com/install/azure.html

- https://docs.liquidfiles.com/install/digital_ocean.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 appliance supports SAML sign-on, metadata exchange, email NameID and group assignment, with optional per-group enforcement. The vendor documents a safeguard local-login path and warns against forcing every external user into the internal IdP. Scope: Self-hosted LiquidFiles SAML authentication. Source: https://docs.liquidfiles.com/authentication/sso_using_saml.html (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 documents deployment from its EC2 appliance AMI, with cloud-instance, storage and network configuration steps. The appliance contains its own OS; this is a vendor appliance installation path, not an upstream Terraform or CloudFormation template. Select the current regional image and licence. Scope: Official AWS appliance deployment; infrastructure provisioning remains customer work. Source: https://docs.liquidfiles.com/install/ec2.html (reviewed 2026-11-20). Deployment artifact: https://docs.liquidfiles.com/install/ec2.html. Artifact reference: Regional AMI selection described in vendor guide.

- Minimum footprint / sizing: Documented. The vendor recommends 1–2 CPUs, 2 GB RAM and 10 GB disk plus transfer storage. One GB RAM is for testing and can swap. File volume, disk/network throughput, backup and HA must be sized separately; the appliance OS is included. Scope: Vendor appliance baseline; transfer storage and HA excluded. Source: https://docs.liquidfiles.com/install/system_requirements.html (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: LiquidFiles (Self-Hosted Virtual Appliance); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.liquidfiles.com/license/overview.html (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).







## NirvaShare

Commercial self-hosted gateway for controlled sharing of customer object storage.

- Listing: https://launchinyourcloud.com/directory/nirvashare/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: CloudFormation; VM image
- Architecture: NirvaShare application services on a customer VM with configured object-storage and identity-provider access.
- 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://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

NirvaShare application services on a customer VM with configured object-storage and identity-provider access. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial self-hosted gateway for controlled sharing of customer object storage.

- data-rooms-ma-document-management: Commercial self-hosted gateway for controlled sharing of customer object storage.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/nirvashare (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://nirvashare.com/docs/deployment/cloud-platforms/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace CFT (aws): https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs
  NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/nirvashare
  NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Cloud Platforms (vultr): https://nirvashare.com/docs/deployment/cloud-platforms/
  NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Marketplace CFT: https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs

- DO Marketplace: https://marketplace.digitalocean.com/apps/nirvashare

- Cloud Platforms: https://nirvashare.com/docs/deployment/cloud-platforms/

- AWS CFT Docs: https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/

- Pricing: https://nirvashare.com/pricing/

- Release Notes: https://nirvashare.com/release-notes/

### Licensing sources

- https://nirvashare.com/pricing/

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs

- https://marketplace.digitalocean.com/apps/nirvashare

- https://nirvashare.com/docs/deployment/cloud-platforms/


### 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: Documented. The reviewed AWS offer delivers CloudFormation Template (CFT) from Nirvato Software Pvt Ltd. Its package version is 6.4.1; verify the contained application and required entitlements separately. Scope: NirvaShare selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs (reviewed 2026-11-19). Offer prodview-k6zpjoiopyrzs: Nirvato Software Pvt Ltd; CloudFormation Template (CFT); package 6.4.1; https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. SAML 2.0 identity providers can protect shares using external-SSO login profiles. The vendor documents metadata exchange with Entra ID and separate admin-console SSO configuration; review entitlement, claim mapping and enforcement for each surface. Scope: Self-hosted share access; admin console configured separately. Source: https://nirvashare.com/docs/tutorials/share-files-from-smb-storage-with-entra-id-active-directory-users-using-sso/ (reviewed 2026-11-20). Supporting source: Admin-console SSO configuration properties — https://nirvashare.com/docs/deployment/nirvashare-config-properties/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes inline CloudFormation YAML that creates EC2, security rules and an installation bootstrap. Its 2025 example uses a fixed AMI, t2.medium and 40-GB disk, below the current 100-GB requirement, and exposes SSH/application ports publicly. Update region/image, storage, ingress and bootstrap pinning before use; it is not a hardened production template. Scope: Legacy vendor CloudFormation example; conflicts with current sizing and requires review. Source: https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/ (reviewed 2026-11-20). Deployment artifact: https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/. Artifact reference: Documentation updated 2025-01-10; not executed. Supporting source: Current minimum disk requirement — https://nirvashare.com/docs/deployment/system-requirements-for-nirvashare/.

- Minimum footprint / sizing: Documented. The vendor specifies at least 2 CPU cores, 4 GB RAM and 100 GB disk, recommending 8 GB RAM or more on a supported Linux distribution. Object/file storage, optional services and HA are additional; this is a baseline, not validated 100-user capacity. Scope: Vendor Linux server baseline; workload and HA sizing excluded. Source: https://nirvashare.com/docs/deployment/system-requirements-for-nirvashare/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: NirvaShare; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://nirvashare.com/pricing/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## 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).






