# Multi Network Segmentation

{% embed url="<https://media.netmaker.io/features/Multi-Network-Management.mp4>" %}

Netmaker enables you to design and operate multiple independent overlay networks within a single control plane.\
Each network functions as its own isolated security domain with dedicated policies, access controls, and routing behaviour.

This architecture allows enterprises to enforce strict segmentation across environments, tenants, business units, or compliance zones — without deploying separate physical infrastructure.

***

### Create Multiple Isolated Networks by Design

Unlike traditional segmentation models that divide a single network into subzones, Netmaker allows you to create entirely separate overlay networks, each with:

* Independent peer membership<br>
* Dedicated access control policies<br>
* Separate DNS configuration<br>
* Custom routing and egress rules<br>
* Distinct security boundaries<br>

Each overlay network is logically isolated and cryptographically independent, ensuring clear operational separation across environments.

***

### Environment Separation Without Infrastructure Duplication

Design dedicated networks for:

* Production<br>
* Staging<br>
* Development<br>
* QA<br>
* Customer environments<br>
* Partner access<br>
* Compliance-regulated workloads<br>

All networks remain centrally managed while maintaining strict isolation.

This enables:

* Reduced lateral movement risk<br>
* Clear blast-radius containment<br>
* Simplified governance<br>
* Predictable security enforcement

***

### Multi-Tenant & MSP-Ready Architecture

For enterprises, OEMs, and managed service providers, multi-network capability is critical.

Netmaker supports:

* Customer-isolated overlay networks<br>
* Per-tenant policy enforcement<br>
* Role-based access is scoped per network<br>
* Centralised observability across all networks<br>

This allows organisations to operate multiple secure domains from a unified platform while preserving tenant isolation.

***

### Zero Trust Segmentation Within and Across Networks

Segmentation operates at two levels:

1. Between networks — full logical isolation<br>
2. Within networks — granular peer-to-peer policy enforcement<br>

This layered model strengthens Zero Trust architecture by ensuring:

* No implicit trust based on location<br>
* Explicit authorization for all connectivity<br>
* Default-deny policy support<br>
* Conditional and Just-In-Time access controls<br>

***

### Hybrid & Multi-Region Consistency

Each overlay network can span:

* Cloud providers (AWS, Azure, GCP)<br>
* On-prem data centres<br>
* Edge deployments<br>
* Global regions<br>

Segmentation policies apply consistently across environments without relying on physical topology.

***

### Observability Across Multiple Networks

Manage and monitor all overlay networks from a centralised control plane.

Gain visibility into:

* Network-level traffic flows<br>
* Cross-segment communication<br>
* Policy enforcement events<br>
* Administrative actions<br>

Operate multiple secure domains without sacrificing clarity or governance.

***

### Why Multiple Networks Matter

Modern infrastructure is not a single flat network.

Enterprises require:

* Separation of duties<br>
* Regulatory boundaries<br>
* Tenant isolation<br>
* Environment partitioning<br>
* Independent security domains<br>

Netmaker’s multi-overlay architecture provides these capabilities natively, without introducing routing complexity or centralised bottlenecks.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.netmaker.io/features/multi-network-segmentation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
