MathType integrations deployment models

MathType integrations support several deployment models that differ in how services are hosted and managed. Choosing the right deployment model depends on your organization's infrastructure, security requirements, and operational preferences.

Why deployment models matter

MathType integrations consist of multiple components that can be hosted either by WIRIS or within your own infrastructure. Different deployment models provide different levels of:

• Operational complexity.
• Infrastructure control.
• Security isolation.
• Configuration flexibility.

Most deployments use WIRIS-hosted services and require little or no additional infrastructure.

Default cloud deployment

In the default deployment model, all services are hosted by WIRIS.

Integration frontend
        ↓
WIRIS-hosted services

This is the recommended option for most organizations because it:

• Requires no backend deployment.
• Minimizes maintenance.
• Provides access to all standard MathType functionality.

Typical use cases

• Schools and universities.
• SaaS applications.
• Organizations without self-hosting requirements.

Self-hosted Integration Services

In this model, Integration Services are hosted on your infrastructure while MathType editor services remain hosted by WIRIS.

Integration frontend
        ↓
Customer Integration Services
        ↓
WIRIS-hosted editor services

This model provides additional control over:

• Formula storage.
• Cache location.
• Rendering configuration.
• Proxy settings.
• Network routing.

Typical use cases

• Organizations with backend customization requirements.
• Customers with proxy or networking restrictions.
• Institutions that need control over stored content.

Fully self-hosted deployment

In a fully self-hosted deployment, both Integration Services and MathType editor services are hosted on your infrastructure.

Integration frontend
        ↓
Customer Integration Services
        ↓
Customer editor services

This model provides the highest level of control but also requires additional infrastructure and licensing.

Typical use cases

• Air-gapped environments.
• Government organizations.
• High-security deployments.
• Environments where external SaaS dependencies are not permitted.

MathType editor services

MathType editor services provide the core functionality used by MathType integrations. Depending on your deployment, these services may include:

• MathType Editor services.
• MathType Hand services.

These services are hosted by WIRIS by default but can be deployed on-premises with the appropriate license.

Choosing a deployment model

For most deployments, the default cloud deployment is sufficient.

• Consider self-hosting Integration Services when you need control over backend behavior or infrastructure configuration.
• Consider a fully self-hosted deployment only when organizational requirements prevent the use of WIRIS-hosted services.

Related articles

• MathType integrations architecture.
• Deploy Integration Services with PHP.
• Deploy Integration Services with Java.
• Deploy MathType Services on-premises with Docker.