
# Data & analytics on DigitalOcean

Compare documented Data & analytics deployments on DigitalOcean, including operating responsibility, licensing and deployment evidence.

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

2 listings.


## Airbyte Self-Managed

Self-managed data movement and ELT platform with customer-operated connectors and job execution.

- Listing: https://launchinyourcloud.com/directory/airbyte/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Elastic License 2.0 for the Airbyte platform; connector and component licenses vary. Enterprise and Cloud offerings use separate commercial terms.
- Licensing model: source-available
- Installation: Official Helm chart for current Kubernetes deployments; cloud VMs are also documented. DigitalOcean separately lists a legacy 1-Click Droplet image.
- Architecture: Customer-operated platform services, connector jobs, metadata database and object storage
- Operations: Customer manages Kubernetes or VM capacity, the metadata database, object storage, secrets, connector images, network access, backups and upgrades.
- Product website: https://airbyte.com/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

This entry covers Airbyte Self-Managed, not Airbyte Cloud or the hybrid offering. Connector jobs communicate with configured external sources and destinations. Elastic License 2.0 permits internal self-hosting but restricts offering the software as a managed service and bypassing license-key functionality. DigitalOcean lists a separate legacy v0.30.25 Marketplace image on Ubuntu 20.04. That evidence does not establish current Helm-release compatibility or current vendor support; verify image availability, upgrade paths and support for the selected release.

The Airbyte platform uses Elastic License 2.0, which permits self-hosting and source modification but restricts managed-service use and protected license functionality. Connectors and development tooling can carry different licenses; inspect the selected component and release. Commercial Enterprise and Cloud terms are separate.

The documented deployment uses long-lived Kubernetes platform services and connector job pods, with a metadata database and object storage. Managed cloud databases or object stores do not make the application runtime serverless.


### Category fit

- data-analytics: Moves data between APIs, databases, files, warehouses and lakes using customer-operated connectors and synchronization jobs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.airbyte.com/platform/deploying-airbyte (checked 2026-11-13). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.airbyte.com/platform/deploying-airbyte (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.airbyte.com/platform/deploying-airbyte (checked 2026-11-13). 

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


### Cloud deployment evidence

- Airbyte self-managed deployment on named cloud providers (aws, azure, gcp): https://docs.airbyte.com/platform/deploying-airbyte
  Airbyte documents its Helm deployment for Kubernetes and explicitly names AWS, Google Cloud and Azure, including EC2/EKS and GCE/GKE examples. This is the self-managed application path; configure provider policies, external storage, secrets and production ingress separately.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Airbyte-published v0.30.25 DigitalOcean Droplet image (digitalocean): https://marketplace.digitalocean.com/apps/airbyte
  DigitalOcean lists an Airbyte-published 1-Click Droplet image, version 0.30.25 on Ubuntu 20.04, and provides creation instructions for the customer account. This is legacy, version-specific application deployment evidence, not verification of the current Helm-based release or current vendor support. Confirm image availability, compatibility, upgrade paths and support before selecting this route.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.


### Sources

- Airbyte platform and self-managed plans: https://docs.airbyte.com/platform

- Self-managed Kubernetes and cloud deployment: https://docs.airbyte.com/platform/deploying-airbyte

- Elastic License 2.0 FAQ: https://github.com/airbytehq/airbyte/blob/master/docs/community/licenses/license-faq.md

- Airbyte platform Elastic License 2.0: https://github.com/airbytehq/airbyte/blob/master/LICENSE

- Legacy Airbyte v0.30.25 DigitalOcean Marketplace image: https://marketplace.digitalocean.com/apps/airbyte

### Licensing sources

- https://github.com/airbytehq/airbyte/blob/master/LICENSE

- https://github.com/airbytehq/airbyte/blob/master/docs/community/licenses/license-faq.md

### Infrastructure sources

- https://docs.airbyte.com/platform/deploying-airbyte

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


### 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: Documented. The DigitalOcean 1-Click page still identifies Airbyte 0.30.25 on Ubuntu 20.04. This is legacy package evidence, not confirmation of a current release, current support or suitability for a new production deployment. Scope: Legacy DigitalOcean image; current upstream deployment requires separate validation. Source: https://marketplace.digitalocean.com/apps/airbyte (reviewed 2026-11-14). Offer airbyte: Airbyte; Droplet 1-Click; package 0.30.25; https://marketplace.digitalocean.com/apps/airbyte.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The vendor documents OIDC login for self-managed instances, but the current plan comparison emphasizes Cloud/Enterprise Flex while Core quickstart uses local credentials. The reviewed pages do not unambiguously establish federation entitlement for the selected Core distribution; obtain edition/version confirmation. Scope: Self-managed OIDC workflow; Core edition entitlement unresolved. Source: https://docs.airbyte.com/platform/access-management/sso (reviewed 2026-11-20). Supporting source: Current self-managed and hybrid plan scope — https://docs.airbyte.com/platform. Supporting source: Core quickstart authentication — https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Airbyte publishes abctl to install a local Kubernetes-based Core instance and a Helm deployment path for customer infrastructure. Local abctl creates its own cluster using Docker; production requires separately configured ingress, storage, secrets and chart/application compatibility. Scope: Official Core installation tooling; local cluster is not an HA architecture. Source: https://docs.airbyte.com/platform/deploying-airbyte/abctl (reviewed 2026-11-20). Deployment artifact: https://github.com/airbytehq/abctl. Artifact reference: Choose an abctl release and compatible chart version.

- Minimum footprint / sizing: Documented. The Core quickstart recommends at least 4 CPUs and 8 GB RAM; low-resource mode can run with 2 CPUs and 8 GB but disables Connector Builder. This is a local deployment profile. Connector concurrency, storage and production/HA components require separate sizing. Scope: Airbyte Core local installation; production HA excluded. Source: https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart (reviewed 2026-11-20).

- License pricing: Documented. The platform is under Elastic License 2.0, including restrictions on offering a substantial hosted/managed service and bypassing licence keys. Connector licences vary. Enterprise features, support and alternative commercial rights require separate terms; this does not price infrastructure. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/airbytehq/airbyte/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Metabase Self-Hosted

Business intelligence and dashboards on your infrastructure.

- Listing: https://launchinyourcloud.com/directory/metabase/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source and commercial options
- Licensing model: open-source
- Installation: Docker image or Java JAR
- Architecture: Customer-operated application and database
- Operations: Your team manages hosting, upgrades and the application database.
- Product website: https://www.metabase.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Metabase documents self-hosting on AWS, Google Cloud, Azure and DigitalOcean. This entry covers self-hosting rather than Metabase Cloud. Infrastructure sizing, the application database and feature entitlements depend on the selected edition. Metabase's critical security advisory affects 0.64.0 through 0.64.3.3 and corresponding Enterprise versions. Self-hosted operators should use Open Source 0.64.3.4 or later, or Enterprise 1.64.3.4 or later. The hardening release strengthens API validation and permission checks, limits metadata exposure, improves deactivated-user session handling, removes database secrets from serialization exports, and adds optional session-signing and encryption keys.

The self-hosted platform offers an AGPL Open Source Edition alongside commercial capabilities and licensing. The classification covers the platform family described in this entry.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- data-analytics: Business intelligence and dashboards on your infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 


### Cloud deployment evidence

- Metabase production hosting compatibility (aws, azure, gcp, digitalocean): https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale
  The vendor names AWS Elastic Beanstalk and Docker, and explicitly identifies Google Cloud, Azure and DigitalOcean as alternative hosts for the Metabase application. Pair this compatibility statement with the current installation guide and a production application database; this is self-hosting, separate from Metabase Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Installing Metabase: https://www.metabase.com/docs/latest/installation-and-operation/installing-metabase

- Production hosting options: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale

- Licensing and edition terms: https://www.metabase.com/license

- Metabase 64 critical security update: https://github.com/metabase/metabase/security/advisories/GHSA-v44v-x8x4-mvcw

### Licensing sources

- https://www.metabase.com/license

### Infrastructure sources

- https://www.metabase.com/docs/latest/installation-and-operation/installing-metabase

- https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale


### 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: Edition-dependent. SAML authentication is available on Pro and Enterprise for self-hosted deployments. This does not establish SAML for the free/open-source edition. Scope: Self-hosted Pro and Enterprise. Source: https://www.metabase.com/docs/latest/people-and-groups/authenticating-with-saml (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. Pro and Enterprise support SCIM. The documentation names Okta and Microsoft Entra ID; Okta supports user/group provisioning while Entra supports user provisioning only. Scope: Self-hosted Pro and Enterprise; identity-provider behavior differs. Source: https://www.metabase.com/docs/latest/people-and-groups/user-provisioning (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor supplies separate Open Source and Enterprise images and publishes Compose examples. Production needs an external supported application database; embedded H2 is evaluation-only. Pin the selected image, configure persistence, TLS and backup, and do not assume an officially supported Helm chart. Scope: Official self-hosted Docker/Compose distributions. Source: https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker (reviewed 2026-11-20). Deployment artifact: https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker#example-docker-compose-yaml-file. Artifact reference: v65 documentation; select a compatible image tag.

- Minimum footprint / sizing: Documented. The vendor gives an application baseline of 1 core/1 GB, plus 1 core/2 GB per 20 concurrent users. The application database starts at 1 core/2 GB and needs additional capacity. Query databases, HA replicas, storage and background jobs are extra; total registered users alone is insufficient for sizing. Scope: Post-v52 production sizing guidance by concurrent users, not registered accounts. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-in-production (reviewed 2026-11-20).

- License pricing: Documented. The repository separates AGPL core code from the commercial enterprise directory and enterprise binaries. Self-hosted Pro/Enterprise features require commercial terms; the core licence does not establish paid-edition prices, support or hosting cost. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/metabase/metabase/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- Metabase 64 critical security update (security-advisory): The advisory records API, permission, metadata, session and serialization hardening in the 64 release line. Scope: Open Source 0.64.0 to before 0.64.3.4 and corresponding Pro/Enterprise 1.64 versions. Conditions: Self-hosted edition, configured integrations and exposed endpoints determine which fixes apply; optional key settings need explicit configuration. Action: Upgrade Open Source to at least 0.64.3.4 or Pro/Enterprise to at least 1.64.3.4 and follow the vendor security checklist. Source: https://github.com/metabase/metabase/security/advisories/GHSA-v44v-x8x4-mvcw; reviewed 2026-11-17.



