
# AI tools & infrastructure on DigitalOcean

Compare documented AI tools & infrastructure deployments on DigitalOcean, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/digitalocean/ai-tools/
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.

4 listings.


## LibreChat Self-Hosted

Self-hosted multi-model AI chat, agent and retrieval platform with documented Railway and DigitalOcean deployments.

- Listing: https://launchinyourcloud.com/directory/librechat/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT
- Licensing model: open-source
- Installation: Official Railway one-click template or Docker on a DigitalOcean Ubuntu Droplet
- Architecture: Containerized web and API services with application databases, retrieval services and customer-configured model endpoints
- Operations: Customer manages the Railway project or DigitalOcean Droplet, application secrets, model credentials, data services, backups, scaling and upgrades. Railway operates its platform; Droplet users also maintain the operating system and Docker runtime.
- Product website: https://www.librechat.ai/
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

The Railway path runs in the customer's project on platform-managed infrastructure; the DigitalOcean path uses a customer-operated Droplet. External model, embedding, search and tool providers receive data according to customer configuration. Review generated secrets, public networking, persistent data services and image updates before production use.

LibreChat is MIT-licensed. The licenses and commercial terms of configured model providers, tools and external services are separate.

LibreChat runs persistent application, database and retrieval containers in a Railway project or on a DigitalOcean Droplet.


### Category fit

- ai-applications-rag: Provides self-hosted multi-model chat, agents, file-backed retrieval and tool use over customer-selected model and data services.

- ai-tools: Provides a self-hosted interface and orchestration layer for model endpoints, agents, MCP tools, authentication and administrative controls.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://www.librechat.ai/docs/remote/railway (checked 2026-11-15). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.librechat.ai/docs/remote/digitalocean (checked 2026-11-15). 


### Cloud deployment evidence

- LibreChat one-click deployment on Railway (railway): https://www.librechat.ai/docs/remote/railway
  LibreChat documents creating a Railway account, reviewing the template's three containers and environment variables, deploying the services and accessing the resulting LibreChat URL in the customer's Railway project.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- LibreChat deployment on DigitalOcean (digitalocean): https://www.librechat.ai/docs/remote/digitalocean
  The upstream guide creates an Ubuntu Droplet in the customer DigitalOcean project, configures a user and firewall, then links to the Docker installation steps. The example is for a small personal deployment, not a production sizing guarantee.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Community and maintenance

LibreChat documents a community of hundreds of contributors and maintains its implementation in a public upstream repository. Contributor history establishes active project participation; it does not establish support for a specific Railway template release.

Reviewed 2026-11-15.

- LibreChat project and community: https://www.librechat.ai/about

- LibreChat contributor history: https://github.com/LibreChat-AI/LibreChat/graphs/contributors

### Sources

- LibreChat Railway deployment: https://www.librechat.ai/docs/remote/railway

- LibreChat project, self-hosting and MIT license: https://www.librechat.ai/about

- LibreChat upstream repository: https://github.com/LibreChat-AI/LibreChat

- LibreChat contributor history: https://github.com/LibreChat-AI/LibreChat/graphs/contributors

- LibreChat deployment on DigitalOcean: https://www.librechat.ai/docs/remote/digitalocean

### Licensing sources

- https://www.librechat.ai/about

### Infrastructure sources

- https://www.librechat.ai/docs/remote/railway

- https://www.librechat.ai/docs/remote/digitalocean


### 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 official self-hosted authentication guide documents OAuth2/OpenID Connect and SAML, with separately configured LDAP and local accounts. Configure the selected provider, registration policy, account linking and administrator recovery; external model credentials are a separate authentication surface. Scope: Self-hosted LibreChat user authentication. Source: https://www.librechat.ai/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 Railway guide describes its repository deploy button, three-container configuration and required environment variables. Review persistence and optional integrations before production; the one-click recipe does not establish a minimum production footprint. Scope: LibreChat Railway deployment guide; moving template and configured features. Source: https://www.librechat.ai/docs/remote/railway (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. The Docker guide lists 1 vCPU and 1 GiB RAM minimum for LibreChat containers, recommending at least 2 GB allocated to Docker with the default backing services. MongoDB, search, RAG/pgvector, storage and HA need sizing; locally hosted models require additional compute and often GPUs. Scope: Official Docker starting profile; model inference and production HA excluded. Source: https://www.librechat.ai/docs/local/docker (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is MIT licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/danny-avila/LibreChat/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## n8n Self-Hosted

Automate integrations and business processes with a customer-hosted workflow editor and runtime.

- Listing: https://launchinyourcloud.com/directory/n8n/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components
- Licensing model: source-available
- Installation: Docker Compose with persistent data; database and worker topology selected for workload
- Architecture: Customer-operated workflow runtime, credentials store and persistent execution data
- Operations: Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
- Product website: https://n8n.io/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry excludes n8n Cloud. The Sustainable Use License has use restrictions and should not be described as unrestricted open-source licensing. Enterprise components require the appropriate commercial license. External integrations, AI providers and optional assistant services require separate data-flow review. n8n@2.48.6 and the maintained n8n@1.123.99 line move official images to patched Node runtimes carrying a V8 process-abort fix. The 1.x image also moves to Node 24.22.3, while 2.x pins a patched Node 26.13.0. Update the selected line and verify custom images use the fixed runtime.

The core is under the Sustainable Use License with use restrictions, not an OSI open-source license. Enterprise-marked code requires a separate commercial Enterprise license. A free self-hosted option does not change the core license model.

Reviewed topology runs long-lived containers and persistent workflow/credential storage. Event triggers do not make the self-hosted control/runtime stack function-based serverless.


### Category fit

- workflow-automation: Visual integration/workflow automation with custom code and connectors; connected systems and AI providers may receive workflow data.

- ai-tools: Orchestrates AI providers, agents, tools and memory as workflows. Model inference and external service dependencies are configured separately.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-aws (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-google-cloud-run (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner (checked 2026-11-12). 


### Cloud deployment evidence

- n8n deployment on AWS (aws): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-aws
  Project instructions deploy n8n and PostgreSQL on customer-operated EKS. Review persistence, ingress and production scaling requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n deployment on Azure (azure): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-azure
  Project instructions deploy n8n with PostgreSQL on Azure Kubernetes Service in the customer subscription.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n deployment on Google Cloud Run (gcp): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-google-cloud-run
  The project documents Cloud Run deployment. Its easy mode is not the production configuration; follow the durable-mode guidance for production and review execution and persistence constraints.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on DigitalOcean (digitalocean): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on Heroku (heroku): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on Hetzner (hetzner): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Current self-hosted Docker Compose guide: https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose

- Official license boundaries: https://github.com/n8n-io/n8n/blob/master/LICENSE.md

- Workflow automation project: https://github.com/n8n-io/n8n

- AI workflow components and integrations: https://docs.n8n.io/build/integrate-ai.md

- n8n self-hosted deployment on DigitalOcean: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean

- n8n self-hosted deployment on Heroku: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku

- n8n self-hosted deployment on Hetzner: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner

- n8n@2.48.6 release: https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6

- n8n@1.123.99 release: https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99

- Patched V8 runtime integration: https://github.com/n8n-io/n8n/pull/43703

### Licensing sources

- https://github.com/n8n-io/n8n/blob/master/LICENSE.md

### Infrastructure sources

- https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose


### 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: Edition-dependent. SAML or OIDC SSO is documented for self-hosted Business and Enterprise. Instance-owner or administrator privileges are required to configure it. Scope: Self-hosted Business and Enterprise; not the unlicensed Community edition. Source: https://docs.n8n.io/deploy/host-n8n/configure-n8n/security/configure-sso.md (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor documents Linux Compose installation and links n8n-hosting configurations for different architectures. Configure persistent data, database, encryption key, domain and TLS; choose the production topology rather than treating the minimal single-server recipe as HA. Scope: Official self-hosted Compose deployment. Source: https://docs.n8n.io/hosting/installation/server-setups/docker-compose/ (reviewed 2026-11-20). Deployment artifact: https://github.com/n8n-io/n8n-hosting. Artifact reference: Select and pin a compatible versioned application image.

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosted memory guide ties RAM usage to execution concurrency, JSON/binary payload size and workflow behavior. It does not establish one safe server minimum. Size main processes, workers/task runners, PostgreSQL, queue-mode Redis, binary storage and HA after measuring representative workflows. Scope: Self-hosted workflow-dependent sizing; complete production footprint unresolved. Source: https://docs.n8n.io/hosting/scaling/memory-errors/ (reviewed 2026-11-20). Supporting source: Production topology and dependencies — https://docs.n8n.io/deploy/host-n8n/install-options/production-requirements.md.

- License pricing: Documented. The Sustainable Use License permits internal business or non-commercial/personal use under its conditions. Enterprise files are separately licensed, and other branches have specific restrictions. Commercial redistribution or embedded use must be checked against vendor terms; self-hosting does not grant every Enterprise feature. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/n8n-io/n8n/master/LICENSE.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. n8n n8n@2.48.6 was published November 19, 2026. Official 2.x images use a patched Node 26.13.0 runtime carrying a V8 process-abort fix. Maintained 1.x users should use n8n@1.123.99 or later, which moves to Node 24.22.3. Scope: Upstream n8n 2.x release; the 1.x maintenance line has a separate fixed build. Source: https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/n8n-io/n8n/releases/tag/n8n%402.47.7. Supporting source: Maintained 1.x runtime fix — https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99. Supporting source: Patched V8 runtime integration — https://github.com/n8n-io/n8n/pull/43703.







## Onyx Self-Hosted

Self-hosted enterprise search and AI assistant platform with connectors and retrieval infrastructure.

- Listing: https://launchinyourcloud.com/directory/onyx/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Community Edition; Business and Enterprise features use separate commercial terms.
- Licensing model: open-source
- Installation: Docker Compose on a VM or official Kubernetes and Terraform deployment
- Architecture: Customer-operated web/API services, background workers, PostgreSQL, Redis, search and object storage
- Operations: Customer manages application services, databases, search, object storage, connectors, model credentials, backups, scaling and upgrades.
- Product website: https://www.onyx.app/
- Source review: 2026-11-14; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers self-hosted Onyx, not a vendor-hosted environment. External LLM, embedding and connector services receive data according to the customer's configuration. Business and Enterprise features and support require separate commercial entitlements.

Onyx Community Edition is MIT-licensed. Business and Enterprise features, images and support have separate commercial terms.

Onyx runs web services, workers and persistent database, cache, search and object-storage dependencies on VMs or Kubernetes.


### Category fit

- ai-applications-rag: Provides enterprise search, connectors and retrieval-augmented AI assistants over customer-selected knowledge sources.

- ai-tools: Provides self-hosted indexing, retrieval, model integration and agent services for building internal AI experiences.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/aws/ec2 (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/azure (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/gcp (checked 2026-11-14). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/digital_ocean (checked 2026-11-14). 


### Cloud deployment evidence

- Onyx on AWS (aws): https://docs.onyx.app/deployment/cloud/aws/ec2
  Onyx documents self-hosting on a customer EC2 instance and links a production EKS architecture using AWS managed dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Onyx on Azure (azure): https://docs.onyx.app/deployment/cloud/azure
  Onyx documents self-hosting on an Azure VM and an AKS Terraform path using customer Azure managed services.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Onyx on Google Cloud (gcp): https://docs.onyx.app/deployment/cloud/gcp
  Onyx documents Compute Engine and production GKE deployment paths in the customer's Google Cloud project.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Onyx on DigitalOcean (digitalocean): https://docs.onyx.app/deployment/cloud/digital_ocean
  Onyx documents installing its self-hosted stack on a customer DigitalOcean Droplet.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Community and maintenance

Onyx has sustained, substantive code participation from multiple contributors. Release 5.1.2 on November 12, 2026 records continuing maintenance, including permission-handling and retrieval fixes. Contributor and release histories establish maintained project participation; they do not establish that paid Business or Enterprise features are included in the MIT Community Edition.

Reviewed 2026-11-14.

- Reviewed maintenance release v5.1.2: https://github.com/onyx-dot-app/onyx/releases/tag/v5.1.2

- Upstream contributor history: https://github.com/onyx-dot-app/onyx/graphs/contributors

### Sources

- AWS EC2 deployment: https://docs.onyx.app/deployment/cloud/aws/ec2

- Azure deployment: https://docs.onyx.app/deployment/cloud/azure

- Google Cloud deployment: https://docs.onyx.app/deployment/cloud/gcp

- DigitalOcean deployment: https://docs.onyx.app/deployment/cloud/digital_ocean

- Community license: https://github.com/onyx-dot-app/onyx/blob/main/LICENSE

- Reviewed maintenance release v5.1.2: https://github.com/onyx-dot-app/onyx/releases/tag/v5.1.2

- Upstream contributor history: https://github.com/onyx-dot-app/onyx/graphs/contributors

- Current Business and Enterprise edition boundaries: https://docs.onyx.app/deployment/enterprise_edition.md

### Licensing sources

- https://github.com/onyx-dot-app/onyx/blob/main/LICENSE

- https://docs.onyx.app/deployment/enterprise_edition.md

### Infrastructure sources

- https://docs.onyx.app/deployment/cloud/aws/ec2

- https://docs.onyx.app/deployment/cloud/gcp


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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 Enterprise section advertises Google OAuth, OIDC and SAML sign-in. The README does not establish every Community-versus-Enterprise protocol entitlement; confirm the selected self-hosted edition and identity configuration. Scope: Enterprise feature statement; exact protocol entitlement not fully established. Source: https://github.com/onyx-dot-app/onyx (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. The upstream Enterprise section describes group synchronization and SCIM user provisioning. Confirm the licensed self-hosted implementation and supported lifecycle operations rather than assuming Community includes them. Scope: Onyx Enterprise feature statement. Source: https://github.com/onyx-dot-app/onyx (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide uses the upstream deployment/docker_compose directory and an environment template. The default image tag moves; replace example storage credentials and configure the selected inference/storage services. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.onyx.app/deployment/local/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/onyx-dot-app/onyx/tree/main/deployment/docker_compose. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The vendor gives Lite minimum 2 vCPUs/2 GB RAM/10 GB disk and Standard minimum 4 vCPUs/10 GB RAM/32 GB plus roughly 2.5 times indexed data. Its Standard per-container example totals about 12 CPUs/24 GB. These describe different profiles; connector/index volume, model services and HA require additional sizing. Scope: Vendor Lite/Standard profiles; per-container and single-instance recommendations differ. Source: https://docs.onyx.app/deployment/getting_started/resourcing.md (reviewed 2026-11-20).

- License pricing: Documented. Core code is MIT licensed; ee directories are under the Onyx Enterprise License. Enterprise features need their own entitlement and quote. The MIT core licence does not establish all-edition feature access, support or model/hosting prices. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/onyx-dot-app/onyx/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v5.1.2, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream onyx-dot-app/onyx release record; commercial editions and deployment packages may differ. Source: https://github.com/onyx-dot-app/onyx/releases/tag/v5.1.2 (reviewed 2026-11-14).







## OpenLIT

OpenTelemetry-based AI tracing and evaluation platform for model and agent operations.

- Listing: https://launchinyourcloud.com/directory/openlit/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream OpenLIT. Models and external integrations have separate terms.
- Licensing model: open-source
- Installation: Run the official Docker Compose platform or documented Kubernetes deployment with its persistent telemetry services.
- Architecture: Customer-operated UI, telemetry receiver and analytical storage with application-side instrumentation
- Operations: Customer manages telemetry collection, analytical storage, capture policies, access controls, retention and upgrades.
- Product website: https://openlit.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Configure instrumentation to send telemetry to the self-hosted receiver. Optional LLM-based evaluations and integrations can call external services; hosting the observability platform does not host every model being observed.

Apache License 2.0 for upstream OpenLIT. Models and external integrations have separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated UI, telemetry receiver and analytical storage with application-side instrumentation. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-observability: OpenTelemetry-native tracing, evaluations and cost/GPU monitoring for AI applications and agents.

- ai-tools: AI instrumentation, evaluation and operational feedback tooling with a self-hosted platform.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.digitalocean.com/products/marketplace/catalog/openlit/ (checked 2026-11-12). 


### Cloud deployment evidence

- OpenLIT deployment on DigitalOcean Kubernetes (digitalocean): https://docs.digitalocean.com/products/marketplace/catalog/openlit/
  DigitalOcean documents the OpenLIT Kubernetes add-on, Helm installation verification and access to the application in the customer cluster. Review the included application and ClickHouse versions, persistent storage and access controls; this is the observability platform, not just its instrumentation SDK.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The upstream release history recognizes multiple named contributors and first-time contributions across releases, providing evidence of sustained participation beyond repository stars.

Reviewed 2026-11-10.

- Maintenance and named release contributors: https://github.com/openlit/openlit/releases

- Public platform and contribution process: https://github.com/openlit/openlit

### Sources

- Official installation and runtime: https://raw.githubusercontent.com/openlit/openlit/main/README.md

- Upstream project and capabilities: https://github.com/openlit/openlit

- Current upstream license: https://raw.githubusercontent.com/openlit/openlit/main/LICENSE

### Licensing sources

- https://raw.githubusercontent.com/openlit/openlit/main/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/openlit/openlit/main/README.md


### Buyer diligence


Research coverage: 6/12 fields (50%); 5 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: Documented. The DigitalOcean Kubernetes 1-Click catalog packages OpenLIT 1.15.0. Its example cluster command is not a minimum footprint or evidence that the package matches the current upstream release. Scope: OpenLIT-published Kubernetes package; 1.15.0 package scope. Source: https://docs.digitalocean.com/products/marketplace/catalog/openlit/ (reviewed 2026-11-14). Offer openlit: OpenLIT; Kubernetes 1-Click; package 1.15.0; https://marketplace.digitalocean.com/apps/openlit.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The official OAuth guide documents Google, GitHub, Microsoft and Okta sign-in, including an Okta OIDC application and provider callbacks. Configure credentials and verified-email account linking. Enterprise UI configuration helpers are separate from the environment-based provider setup; verify the chosen release/edition. Scope: Self-hosted OpenLIT OAuth/OIDC provider setup. Source: https://docs.openlit.io/latest/openlit/oauth.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 OpenLIT repository provides platform deployment instructions separate from its instrumentation SDK. Configure the platform telemetry services, persistent data and network exposure for the selected deployment. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/openlit/openlit (reviewed 2026-11-14). Deployment artifact: https://github.com/openlit/openlit. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The current self-hosting guide identifies the OpenLIT dashboard/API/OTLP receiver, ClickHouse storage and NATS JetStream for threshold alerts. It does not establish a workload-independent CPU/RAM floor. Size ingestion rate, trace retention, indexing and HA for these components together. Scope: Current OpenLIT multi-component topology; numeric production sizing unresolved. Source: https://docs.openlit.io/latest/openlit/installation.md (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/openlit/openlit/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was openlit-2.1.1, published 2026-10-26. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream openlit/openlit release record; commercial editions and deployment packages may differ. Source: https://github.com/openlit/openlit/releases/tag/openlit-2.1.1 (reviewed 2026-11-14).






