Browsertrix
Open-source browser-based web archiving and collection-management application.
3 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Kubernetes manifests
Runs in
Documented customer environment
Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook.
- DigitalOcean: Customer cloud account
- DigitalOcean
Servers / containers
Operated by
Your team
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.
Deployment boundaries by provider
- DigitalOcean: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Browsertrix DigitalOcean Docs ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Kubernetes manifests |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Open Source / Open Core GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
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.
Self-hosted Browsertrix v1.26.6 platform-user identity; captured-site credentials are excluded · Source ↗ · Deployment customization ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Self-hosted Browsertrix v1.26.6 Helm artifact; production configuration and experimental Ansible scope · Source ↗ · Deployment artifact ↗ (v1.26.6) · Chart configuration ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
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.
Browsertrix v1.26.6 chart component resource requests; not complete workload/HA sizing · Source ↗ · Backend resource template ↗ · MongoDB resource template ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Browsertrix; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
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.
Browsertrix upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
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.
Community & 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.
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.
Compare within Legacy system archive & access
- ArchiveBoxOpen-source web archiving application for retained, searchable copies of web content.
- Railway
- Hostinger
- FormKiQ Legacy System Archive and Access Directory PublisherArchive documents from legacy business systems — searchable, governed, and stored in your own AWS account without new vendor lock-in.
- AWS
- OpenText Information ArchiveArchive legacy application data and content while retaining searchable access and lifecycle controls.
- AWS
- PBS ContentLink (Azure)SAP archive-content software operated by itesys in the customer’s Azure tenant.
- Azure
- Rocket Content Services - MobiusCommercial content-services and archive platform delivered to customer AWS through a negotiated offer.
- AWS
- Solix Application Retirement — Customer-ManagedArchive retired applications while retaining searchable access to historical business information.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- IBM Cloud
- StorageMAP by DatadobiCommercial unstructured-data inventory, search and governance software for customer cloud infrastructure.
- AWS
These products address related workflows; read their category-fit notes before comparing scope. See all of Legacy system archive & access →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Browsertrix DigitalOcean Docs ↗docs.browsertrix.com
- AGPL-3.0 LICENSE ↗raw.githubusercontent.com
- GitHub Releases ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Browsertrix DigitalOcean Docs ↗ · DigitalOcean
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Browsertrix DigitalOcean Docs ↗ · DigitalOcean
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com