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 Services

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

• MathType Editor services.
• MathType Hand services.

Although most deployments access MathType Services through Integration Services, applications can also communicate with these services directly when only formula editing, handwriting recognition, or rendering capabilities are required.

When should you self-host MathType Services?

For most deployments, WIRIS-hosted services provide the simplest and recommended solution. Self-hosting MathType Services may be appropriate when your organization requires:

• Network isolation or air-gapped environments.
• Compliance with internal security policies.
• Control over where requests are processed.
• Reduced dependency on external services.
• Direct integration with MathType Services from custom applications.

Self-hosting requires additional infrastructure, operational maintenance, and a valid MathType server license.

Performance considerations

Resource consumption depends on the services you deploy and the workload they process. The following figures are intended as general sizing guidance for self-hosted deployments and should not be considered guaranteed performance metrics.

Editor Services

When deploying only MathType Editor Services, historical sizing guidance indicates:

A server with 1 CPU core and 1.5 GB RAM is considered the recommended minimum specification. These figures refer to formulas being edited. Rendering formulas that have already been generated is typically less demanding, as images may be served from the Integration Services cache.

Estimated concurrent users

Assuming each user edits, on average, one formula every three minutes, a deployment with 2 CPU cores and 1.5 GB RAM can support approximately:

These figures are indicative and assume a relatively even distribution of editing activity rather than simultaneous editing peaks.

Editor Services + Hand Services

Deployments that include both MathType Editor Services and Hand Services require additional processing capacity. Historical sizing guidance indicates:

A server with 1 CPU core and 1.5 GB RAM is considered the recommended minimum specification. As with Editor Services alone, these figures refer to formulas being edited rather than rendered from cache.

Estimated concurrent users

Assuming each user edits, on average, one formula every three minutes, a deployment with 2 CPU cores and 1.5 GB RAM can support approximately:

These figures are indicative and may vary depending on hardware, workload, deployment architecture, and MathType version.

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.
• Deploy MathType Services with Java.
• Deploy MathType Services with .NET.