02 / First-release focus
Audit intelligence
Keep source-native events distinct from changes Zenda observes and actions Zenda generates. Show coverage gaps instead of implying a complete history.
Information with integrity
Your content.
A clearer truth.
Keep your existing systems. Make your enterprise information intelligent, traceable and continuously governed.
Zenda Overlay is being shaped as an independent integrity layer for OpenText Content Management, including Extended ECM and Content Server.
Initial integration target: OpenText Content Management.No customer environment is connected or verified.
Zenda Overlay
Information integrity model
Existing system
Your content stays at its source
Intended Zenda layer
Review information with context
Metadata quality
Event provenance
Version context
Concept only. This illustration contains no live repository data and does not represent a connected OpenText environment.
Same systemsA higher layer for what matters
First-release design intent
01Read-only source retrieval
02Identity and provenance preserved
03Unknowns stay visible
01 / The integrity layer
Govern. Verify. Trace.
The first release is planned around three questions: is the metadata consistent, what evidence exists about change, and which native version can be traced?
Metadata governance01
Find the exception.
Keep the evidence.
The planned rule engine focuses on mandatory fields, formats, controlled vocabularies and cross-field consistency. Source values stay distinct from Zenda's interpretation.
Proposed review sequence · illustrative
01Observe authorised source values
02Evaluate against an agreed rule
03Attach evidence to an exception
04Record the review decision
03 / First-release focus
Version intelligence
Preserve native version identifiers and source references when an authorised, verified API exposes them. Missing history stays an explicit gap.
These are product objectives, not claims of live functionality. Audit, version and metadata access must be verified against an authorised target environment.
02 / Commercial scope
Start focused. Measure honestly.
Agree repository scope, document types and success measures before committing. Confirm commercial terms for your deployment.
Illustrative storefront template plans below; these are not a confirmed Zenda offer or pricing.
Free
For individuals getting started
$0/month
- 1 workspace
- Up to 3 team members
- Basic analytics
- Community support
A subscription does not establish OpenText compatibility. Deployment-specific verification is a separate prerequisite.
03 / Clear boundaries
Evidence before assumptions.
04 / A higher layer for what matters
Make information easier to trust.
Begin with a defined information problem, a confirmed source environment and evidence you can measure.