
# Legacy system archive & access on DigitalOcean

Compare documented Legacy system archive & access deployments on DigitalOcean, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/digitalocean/legacy-system-archive-access/
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.

1 listing.


## Browsertrix

Open-source browser-based web archiving and collection-management application.

- Listing: https://launchinyourcloud.com/directory/browsertrix/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- 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: Kubernetes manifests
- Architecture: Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook.
- 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://webrecorder.net/browsertrix
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The documented playbook provisions the application rather than only a crawler SDK. Customer operators manage crawl capacity, storage, credentials, retention and upgrades; the hosted Browsertrix service is a separate option.

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

Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- legacy-system-archive-access: Open-source browser-based web archiving and collection-management application.

- archives-collections-management: Open-source browser-based web archiving and collection-management application.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.browsertrix.com/deploy/ansible/digitalocean/ (checked 2026-11-19). 


### Cloud deployment evidence

- Browsertrix DigitalOcean Docs (digitalocean): https://docs.browsertrix.com/deploy/ansible/digitalocean/
  Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook. The documented playbook provisions the application rather than only a crawler SDK. Customer operators manage crawl capacity, storage, credentials, retention and upgrades; the hosted Browsertrix service is a separate option.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes SuaYoo, ikreymer, tw4l, 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/webrecorder/browsertrix/graphs/contributors

- Upstream project: https://github.com/webrecorder/browsertrix

### Sources

- Browsertrix DigitalOcean Docs: https://docs.browsertrix.com/deploy/ansible/digitalocean/

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/webrecorder/browsertrix/main/LICENSE

- GitHub Releases: https://github.com/webrecorder/browsertrix/releases

### Licensing sources

- https://raw.githubusercontent.com/webrecorder/browsertrix/main/LICENSE

### Infrastructure sources

- https://docs.browsertrix.com/deploy/ansible/digitalocean/


### 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: Sources checked — unresolved. Browsertrix v1.26.6 implements application-issued JWTs and password-based login. The reviewed deployment/authentication material does not establish an external SAML/OIDC login path for platform users. Browser profiles used to authenticate to websites being crawled are a separate feature and do not prove Browsertrix account SSO. Scope: Self-hosted Browsertrix v1.26.6 platform-user identity; captured-site credentials are excluded. Source: https://github.com/webrecorder/browsertrix/blob/v1.26.6/backend/btrixcloud/auth.py (reviewed 2026-11-21). Supporting source: Deployment customization — https://docs.browsertrix.com/deploy/customization/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Browsertrix provides an upstream Helm chart and remote-deployment instructions for Kubernetes, including single-machine MicroK8s/k3s configuration, domains/TLS and optional external MongoDB/S3-compatible storage. Ansible cloud playbooks are described as experimental. Pin the chart/application release and configure secrets, persistent storage, backups and exposure; these recipes do not establish HA. Scope: Self-hosted Browsertrix v1.26.6 Helm artifact; production configuration and experimental Ansible scope. Source: https://docs.browsertrix.com/deploy/remote/ (reviewed 2026-11-21). Deployment artifact: https://github.com/webrecorder/browsertrix/tree/v1.26.6/chart. Artifact reference: v1.26.6. Supporting source: Chart configuration — https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/README.md.

- Minimum footprint / sizing: Documented. The v1.26.6 chart defaults request 100 millicores/350 MiB for an API container and 12 millicores/512 MiB with a 2 GiB volume for bundled MongoDB; the deployment templates apply those values. These are per-component scheduling defaults, not a total host minimum or archive capacity. Include Redis, frontend, crawler/browser workers, replicas, captured data and backups when sizing production. Scope: Browsertrix v1.26.6 chart component resource requests; not complete workload/HA sizing. Source: https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/values.yaml (reviewed 2026-11-21). Supporting source: Backend resource template — https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/templates/backend.yaml. Supporting source: MongoDB resource template — https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/templates/mongo.yaml.

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

- Operating cost estimate: Not researched.

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






