Alfresco Content Services + Governance Services
Customer-operated content and records management with retention and record-declaration workflows.
8 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
Distribution ZIP/module installation; underlying platform container/Helm options
Runs in
Documented customer environment
Customer-operated content repository, search and database
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer operates repository, search, database, backups and upgrades. Enterprise container access requires vendor credentials.
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.
Alfresco Content Services deployment on Amazon EKS ↗ · Source checked 2026-11-12
Alfresco Governance Services 7.4 add-on installation ↗ · 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 | Distribution ZIP/module installation; underlying platform container/Helm options |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Open Source / Open Core This broad combined Content Services/Governance listing spans LGPL-3.0 Community software and commercially licensed Enterprise software with additional enterprise extensions. Community-only deployments and Enterprise deployments have different rights/features. |
| License | Community and commercial editions; capabilities and support differ |
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 official Identity Service source describes SAML federation for Alfresco Content Services, the parent platform. It does not establish the current Governance Services/ACS/Identity Service supported-version combination or commercial entitlement. Confirm that matrix for the selected governance installation.
Parent-platform federation documented; current Governance Services combination unresolved · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The archived 7.2 Docker Compose instructions are explicitly for development and test. Enterprise images require Quay credentials through Alfresco Support; do not treat this recipe as a supported production architecture.
Alfresco Governance Services 7.2 Enterprise container recipe; historical, not current-release certification · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The version-7.2 Compose source cites a 16-GB required memory setting while describing lower troubleshooting allocations. It explicitly limits Compose to development/test. This does not establish a current production or HA footprint for ACS plus Governance Services and supporting search/database components.
Legacy development/test container recipe; current production sizing unresolved · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
Not confirmedEvidence and scope for License pricing
The reviewed installation source requires customer-issued Quay credentials for Enterprise Governance images. Community source licensing does not establish those commercial entitlements, supported ACS/AGS combinations or pricing. Obtain a current subscription and module quote for the selected deployment.
Enterprise distribution access; current licence/pricing terms unresolved · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · 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
Governance Services adds records management to Alfresco Content Services. Select the exact edition and supported production installation. Storage connectors do not establish provider-specific deployment support, and the documented development Docker Compose configuration is not a recommended production topology. Hyland’s current supported-platform documentation lists Governance Services 26.2. The retained 25.2 installation page is version-specific, so verify the selected Content Services and Governance Services versions against the current compatibility matrix.
Category fit
- Records management
- Records lifecycle management with file plans, retention schedules, declaration and auditing. Community and commercial editions differ. Docker Compose examples are for development/testing; review a supported production topology.
- Document management
- Content Services provides the content repository and document management; Governance Services adds records lifecycle capabilities.
Compare within Records management
- FormKiQ Records Management Directory PublisherImplement retention, legal hold, defensible disposition, and compliant lifecycle policies for governed records.
- AWS
- Hyland OnBase On-PremiseCustomer-hosted enterprise content and case platform for document-heavy business processes.
- AWS
- Azure
- Google Cloud
- iTernity Compliant Archive Software (iCAS)Licensed immutable-archive software provisioned in a customer STACKIT deployment.
- STACKIT
- Laserfiche Self-HostedSelf-hosted document and records platform with forms and configurable business process automation.
- AWS
- Azure
- M-Files On-PremisesCustomer-operated document vault and information-governance platform with metadata-driven workflows.
- AWS
- Azure
- Google Cloud
- Mail-ArchiverOpen-source email archiving, search and export service with a community Railway deployment.
- Railway
- MailStore Service Provider Edition (SPE)Commercial multitenant email archive operated by service providers in their own cloud accounts.
- AWS
- Azure
- Open ArchiverOpen-source email archive with provider-packaged VPS deployment and retention-oriented workflows.
- Hostinger
Showing 8 of 12 other listings in Records management. These products address related workflows; read their category-fit notes before comparing scope. See all of Records management →
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 Alfresco documentation ↗docs.hyland.com
- Governance Services 25.2 installation options ↗support.hyland.com
- Official container installation source and limitations ↗github.com
- Licensing and edition terms ↗github.com
- Licensing and edition terms ↗docs.alfresco.com
- Licensing and edition terms ↗pages.alfresco.com
- Licensing and edition terms ↗connect.hyland.com
- Current Alfresco supported platforms and Governance Services releases ↗docs.hyland.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.
- Alfresco Content Services deployment on Amazon EKS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents customer-operated ACS Enterprise and Community deployments on EKS, including persistent storage and customized repository/Share images. Evidence covers the ACS platform on which Governance Services is installed. Add the compatible Governance Services images or modules, required entitlements and production configuration; the separate development-only Compose example is not a production recommendation.
- Alfresco Governance Services 7.4 add-on installation ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12 · Version: Governance Services 7.4; confirm compatible ACS release. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor versioned 7.4 manual documents Governance Services distribution ZIP/AMP installation on the compatible ACS platform and a development/test-only Compose option. Pair the add-on documentation with the ACS EKS deployment evidence and confirm the supported ACS/Governance release combination and commercial entitlements. This is not a claim that the development Compose file is a production topology.
- Alfresco Content Services deployment on Amazon EKS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked