Module Suite Runtime introduces a new place to build and run applications with Module Suite. It is a standalone, containerized platform that runs Content Scripts independently – without requiring an OpenText Content Management installation or sharing its upgrade cycle.
The language, API style and skills remain the same. Applications can run entirely on the Runtime or connect to OpenText Content Management when enterprise content services are needed.
Standalone by design
Unlike classic Module Suite, which operates within OpenText Content Management, the Runtime has its own web server, database, storage, security model and administration console.
This opens Module Suite to applications that do not require an enterprise repository, including public forms, portals, webhook receivers, scheduled integrations and AI agent tools. It also allows organizations to introduce new capabilities without modifying their Content Management environment, while preserving the option to connect applications to it later.
Deploy it your way
Module Suite Runtime ships as a container and can run on a laptop, virtual machine or Kubernetes. It supports single-node environments for evaluation, scalable multi-node deployments and offline delivery for air-gapped or regulated environments.
Organizations can use the bundled PostgreSQL, Redis and object storage services or provide their own infrastructure.
A composable platform
The Runtime core provides the Content Script engine, security, storage, scheduling, auditing, REST APIs and management console. Additional capabilities are installed as independent modules, including:
- Forms and public experiences
- End-user portals
- Content Script Editor
- MCP Server
- Docusign Integration
Administrators can install and activate only the modules they need. Each module runs in isolation and can evolve independently, while a documented template will allow partners and customers to create their own extensions.
Connecting enterprise systems to AI
Module Suite Runtime can also operate as an MCP server, enabling AI assistants to call tools written as Content Scripts.
Anything a Content Script can access – from an enterprise repository or database to a web service – can therefore be made available to an AI agent under the organization’s governance. Multiple MCP servers can be hosted, each with its own purpose-built set of tools and OAuth-secured access.
Planned for Module Suite 4.1, the AI Gateway will provide a centrally governed entry point for both Module Suite and third-party MCP servers. It will support role- and user-based entitlement, curated toolsets, auditing and server health monitoring.
Standalone when possible, connected when needed
Application Builder, AI Form Builder and Content Script Editor can all run within the Runtime, with Aether powering their generative capabilities. The same toolchain can be used to create standalone forms, portals, integrations and agent tools – or applications that work with enterprise content.
When connected to OpenText Content Management, Runtime applications can search the repository, inspect nodes and perform document operations through supported service interfaces. Support for OpenText Core Content and additional repositories is part of the roadmap.
Module Suite Runtime extends what can be built around enterprise content platform – providing a flexible starting point for standalone applications and a controlled path to enterprise content, integrations and AI.
