OpenText Information Archive
Archive legacy application data and content while retaining searchable access and lifecycle controls.
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
Arrange the documented on-premises deployment and implementation with OpenText.
Runs in
Documented customer environment
Enterprise archival platform; exact current on-premises topology requires vendor sizing and design.
- AWS: Customer cloud account
- AWS
Not specified
Operated by
Your team
Plan extraction, information packages, validation, storage, retention, access, backups and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Customer-deployed OpenText InfoArchive architecture on AWS ↗ · Source checked 2026-11-12
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 | Arrange the documented on-premises deployment and implementation with OpenText. |
|---|---|
| Infrastructure | Not specified The current product page establishes on-premises deployment but does not specify a complete current runtime topology; infrastructure is left unspecified. |
| Licensing model | Commercial Only The listed OpenText archive is licensed commercial software. The vendor license-model schedule explicitly includes OT InfoArchive; current metrics, bundles and terms must be confirmed for the renamed product. |
| License | Commercial software licensing; confirm the current archive edition, metrics and deployment contract. |
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.
4 of 12 fields researched (33%) · 1 documented · 3 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The accessible developer overview and REST material do not establish a version-matched user-facing SAML/OIDC integration for customer-managed Information Archive. API bearer/JWT access and a generic OpenText identity service do not by themselves prove the archive UI login path and entitlement.
Customer-managed Information Archive user federation remains unconfirmed · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
Not confirmedEvidence and scope for Deployment artifact / IaC
The product page confirms on-premises and hybrid deployment options but does not identify an installable package or current IaC artifact. A deployment model is not enough to establish the installer, version compatibility or entitlement; obtain the licensed installation documentation.
Current customer-operated product; installer/artifact remains unconfirmed · Source ↗ · Reviewed 2026-11-16
Sources checked — unresolved · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The accessible product/developer overview does not supply quantitative current production CPU/RAM/storage or HA sizing. A lightweight test-installation statement cannot size archive ingestion, indexes, retention, retrieval or database/storage replicas.
Customer-managed Information Archive production sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The published ECD software schedule (effective 2021) identifies InfoArchive as application-specific licensed software and defines order-selected usage metrics and restrictions. This documents a commercial licensing framework, not the metric or price of a current customer order; confirm current product/DR/non-production entitlements.
Historical public ECD licence framework naming InfoArchive; current transaction documents control · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
Show all fields (8 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.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
Formerly InfoArchive. The current product explicitly supports on-premises deployment. Named cloud availability alone does not establish deployment in your account.
Category fit
- Legacy system archive & access
- Dedicated structured/unstructured data archiving and legacy application decommissioning while preserving governed historical access.
Compare within Legacy system archive & access
- ArchiveBoxOpen-source web archiving application for retained, searchable copies of web content.
- Railway
- Hostinger
- BrowsertrixOpen-source browser-based web archiving and collection-management application.
- DigitalOcean
- 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
- 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
- Current product, legacy retirement and on-premises deployment ↗www.opentext.com
- InfoArchive license model schedule ↗www.opentext.com
- Vendor implementation and on-premises upgrade responsibilities ↗careers.opentext.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.
- Customer-deployed OpenText InfoArchive architecture on AWS ↗ · AWS
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
AWS and OpenText explicitly distinguish customer-deployed InfoArchive from the managed offering. Their reference architecture places the web application, directory service and InfoArchive server on EKS in private subnets, with S3, EFS and RDS. Confirm the current product release, licensing, sizing and operating agreement before implementation.
- Customer-deployed OpenText InfoArchive architecture on AWS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked