---
schema_version: "1"
id: aeffde3f65f87070d2a91eafc15c5a349eab8d2fe2dd030d841f8252706c5f4c
title: Requirements and Limitations for Hybrid Standalone Instances
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/hybrid-standalone/hybrid-standalone-requirements-limitations.md
canonical_url: https://docs.mulesoft.com/hybrid-standalone/hybrid-standalone-requirements-limitations
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 03f5469d40c3ea4d12c9506fe8d3f73abcbbe7dcbd2d8c2b2724dd6893430834
description: MuleSoft Documentation Site
latest: true
---
---
product: Hybrid Standalone Runtimes
---

# Requirements and Limitations for Hybrid Standalone Instances

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Plan and configure your hybrid standalone infrastructure by understanding the licensing
requirements, infrastructure specifications, and operational limitations that govern hybrid
standalone deployments.

## MuleSoft License Compliance

You are responsible for ensuring compliance with your MuleSoft licensing for hybrid standalone
deployments.

Licensing is based on the maximum allocated cores consumed by your Mule runtime instances:

- Core calculation is based on logical or allocated cores available to the Mule instance or server.

- Allocated cores are configured through OS, VM, container, or Mule configuration settings.

- Core count is determined by the number of cores visible to the Java Virtual Machine running Mule.

- Physical cores are not considered in licensing; only logical or virtual cores as reported by the
  OS are counted.

- Each VM or container instance is metered separately, even if multiple instances run on the same
  physical host.

- Fractional cores are always rounded up to the nearest integer value.

If cores are not explicitly allocated to Mule, the number of logical or virtual cores available on
the physical or virtual machine or container as informed by the OS determines the core count.

## Requirements

Ensure your infrastructure meets the minimum specifications and configuration requirements for
successful hybrid standalone deployment and operation.

### Hardware Requirements

Minimum hardware specifications for Mule runtime engine on hybrid standalone instances:

- 2 GHz CPU or 1 virtual CPU in virtualized environments, 2+ cores recommended for production
  workloads.

- 1 GB RAM minimum (Mule runtime), 4GB RAM minimum recommended for hybrid deployments, 8GB+
  recommended for production environments.

- 4 GB minimum (Mule runtime), 10GB+ available disk space recommended for applications and logs.

- x86 and x64 architectures supported.

- Reliable internet connectivity for Anypoint Platform communication.

> [!NOTE] Adjust RAM allocation to match your latency requirements and the size and number of
> simultaneous messages that applications process.

### Software Requirements

Verify that you use a supported version of Java before installing Mule runtime engine:

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><div><div><p>JDK</p></div></div></td><td><div><div><p>JDK 17</p></div></div></td></tr></tbody></table>

> [!NOTE] Though you can run a different JDK of choice, MuleSoft doesn’t support or take action to
> fix issues if they are traced back to the JDK.

### Supported Operating Systems

Mule is supported on any operating system that runs a Java Runtime Environment (JRE) from a
supported JDK.

Mule runtime engine passed functional testing against these software and operating systems:

- MacOS 10.15

- HP-UX 11i V3

- AIX 7.2

- Windows Server 2019

- Windows 10

- Solaris 11.3

- Red Hat Enterprise Linux 9.4

- Ubuntu Server 20.04

- Adoptium OpenJDK distribution

> [!NOTE] Anypoint Monitoring agent has known compatibility limitations on all of the operating
> systems listed previously. Advanced monitoring features provided by Anypoint Monitoring may not be
> available on these platforms. Basic monitoring capabilities through Runtime Manager remain
> available.

### Network Requirements

Network configuration needs:

- Outbound HTTPS connectivity to Anypoint Platform

- Firewall configuration for Runtime Manager agent

- Optional VPN for secure communication

- Load balancer configuration (for clustered deployments)

### Security Considerations

Important security aspects:

- SSL/TLS encryption for all communications

- Certificate management and rotation

- Access control and authentication

- Network segmentation and firewall rules

- Audit logging and monitoring

## Limitations

Be aware of the constraints and limitations that affect hybrid standalone deployments to plan your
infrastructure accordingly.

A target represents any deployment destination for Mule applications, including individual servers,
server groups, or clusters. For example, a server group with eight servers is a single target for
deployment purposes.

### Infrastructure Scaling Limits

Design your server infrastructure within these hard limits to ensure scalable and manageable hybrid
standalone deployments.

<table><colgroup><col> <col></colgroup><thead><tr><th>Component</th><th>Hard Limit</th></tr></thead><tbody><tr><td><p>Maximum number of servers (not Runtime Fabric)</p></td><td><p>500</p></td></tr><tr><td><p>Maximum number of servers per server group</p></td><td><p>20</p></td></tr><tr><td><p>Maximum number of servers per cluster</p></td><td><p>8</p></td></tr></tbody></table>

### Network Configuration Requirements

Proper network configuration is essential for Runtime Manager agent connectivity and secure
communication with Anypoint Platform services. Network allowlists, firewall rules, and port
configurations must be properly configured to ensure reliable hybrid standalone operations.

For comprehensive network configuration guidance, refer to
[Adding Ports, IPs, and Hostnames for Runtime Manager Agent](https://docs.mulesoft.com/hybrid-standalone/configure-ports-ips).

### Deployment Limits

Plan your application deployment strategy within these tested and recommended limits to make sure
reliable performance and avoid platform constraints.

<table><colgroup><col> <col></colgroup><thead><tr><th>Component</th><th>Tested Recommended Limit</th></tr></thead><tbody><tr><td><p>Maximum number of deployments per environment</p></td><td><p>1000</p></td></tr><tr><td><p>Maximum number of deployments per hybrid target</p></td><td><p>200</p></td></tr><tr><td><p>Maximum number of properties per application</p></td><td><p>300</p></td></tr><tr><td><p>Maximum deployment size for CloudHub and standalone</p></td><td><p>200 MB</p></td></tr><tr><td><p>Maximum deployment size for CloudHub 2.0 and Runtime Fabric</p></td><td><p>350 MB</p></td></tr></tbody></table>

## See Also

- [Hybrid Standalone Runtimes Overview](https://docs.mulesoft.com/hybrid-standalone/)