Adobe Experience Manager 6.5 Forms (Correspondence Management)

Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Package / binary installer

  2. 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
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    AEM 6.5 Tech Reqs ↗ · Source checked 2026-11-19

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    AEM 6.5 Tech Reqs ↗ · 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 methodPackage / binary installer
InfrastructureServers / containers
Customer-operated AEM author/publish application VMs with supported Java, persistence and Forms components. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelCommercial Only
Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
LicenseCommercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

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%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

AEM 6.5 provides a SAML 2.0 Web SSO handler with signed/encrypted assertions, user creation and group synchronization. It is disabled until configured with provider/entity information and trust material. This establishes the AEM/OSGi web-login path, not automatic SSO for every Forms JEE or desktop component.

AEM 6.5 platform web authentication used by the Forms deployment; choose the applicable runtime and repository paths · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

Adobe documents installing AEM 6.5 Quickstart and a compatible Forms add-on package through its package-management workflow. Downloads require entitled Adobe access. Select the matching Forms runtime/service pack and deployment topology; this is licensed application installation, not a public Terraform or complete cloud template.

AEM 6.5 Forms on OSGi installation path; Forms JEE and Correspondence Management components require their applicable guides · Source ↗ · Deployment artifact ↗ (AEM 6.5 Quickstart plus compatible Forms add-on/service pack; entitled download selection required) · Base AEM installation ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

Adobe lists base AEM installation requirements and separate Forms temporary-space/topology requirements, but these do not establish a complete Correspondence Management production sizing profile. Author/publish roles, document services, storage and redundant instances must be sized for the selected Forms runtime and workload.

AEM 6.5 Forms/Correspondence Management; generic AEM minima and installer temporary space are not a validated whole-system HA floor · Source ↗ · General AEM technical requirements ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Adobe Experience Manager 6.5 Forms (Correspondence Management); software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

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

AEM 6.5 Forms is separate from AEM as a Cloud Service and Adobe Managed Services. Production Forms capabilities require their own licence. Adobe's VM support remains subject to its technical requirements and reproducibility rules; supported S3 or Blob datastores do not make every cloud-native service supported.

Category fit

Correspondence management
Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.
Document management
Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.

Compare within Correspondence management

  • FormKiQ Correspondence Management Directory PublisherManage formal correspondence from intake and assignment to approved replies, response deadlines, dispatch evidence, follow-up, and closure in FormKiQ.
    • AWS
    Customer-operated · Commercial Only
  • Hyland OnBase On-PremiseCustomer-hosted enterprise content and case platform for document-heavy business processes.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Hyperscience HypercellCommercial document-intake and extraction platform installed into customer Kubernetes infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • OpenKM ProfessionalCustomer-hosted document management for configured correspondence registration and response workflows.
    • AWS
    Customer-operated · Commercial Only
  • Quadient Inspire Flex via ORDACommercial customer-communications software packaged as a bring-your-own-licence AWS image by ORDA.
    • AWS
    Customer-operated · Commercial Only

These products address related workflows; read their category-fit notes before comparing scope. See all of Correspondence management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • AEM 6.5 Tech Reqs ↗ · AWS, Azure

      Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Customer-operated AEM author/publish application VMs with supported Java, persistence and Forms components. AEM 6.5 Forms is separate from AEM as a Cloud Service and Adobe Managed Services. Production Forms capabilities require their own licence. Adobe's VM support remains subject to its technical requirements and reproducibility rules; supported S3 or Blob datastores do not make every cloud-native service supported.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory