Dorsa CloudCloud infrastructure
Sign inGet started
Private network

Connect your servers through an isolated internal network

Private networking connects servers in a project without routing through the internet. Internal communication stays separate from public traffic.

Get startedPricing calculator
  • Pay by the hour for the time you use
  • Estimate costs before provisioning
  • Tehran data centers
ExamplePrivate network diagram
Private networkapp-net10.0.1.0/24

Compute web-1 connects over its internal address to app-1 and db-1 without the internet. The connection succeeds only if the destination server's firewall allows it.

Why private networking?

Let your servers communicate without the internet

When application components run on several servers, keep internal communication on an internal network and expose only the parts that must be public.

  • Separate from public traffic

    Project servers communicate over a separate internal network rather than the public internet. Each network belongs to one project.

  • Direct server communication

    Your application connects to database servers and other components using internal addresses, just like a conventional local network.

  • Choose your address range

    Choose an address range when creating a network and optionally specify an internal IP when creating a server. Networks in one project must not overlap.

Startup

Create a network in 3 steps

Values below are examples only. Choose your own range and name.

  1. Create the network

    Choose a Latin-character name and an address range. A common internal address range is shown below as an example.

    app-net 10.0.1.0/24

  2. Create a server in the network

    Select the network when creating a server. You can optionally assign its internal IP yourself.

    web-1 10.0.1.10

  3. Connect a router if required

    Connect the network to a virtual router and configure the gateway address for external connectivity.

    gateway 10.0.1.1
Example architecture

Web, application and data, each in its own network

A common pattern exposes only the web tier externally. Each subsequent tier accepts connections only from the preceding one. This is an example, not a mandatory template.

Example

  • Web tier

    The application users see

    10.0.1.0/24web-1
    Only external web traffic

  • Application tier

    Processing and business logic

    10.0.2.0/24app-1
    Only from the web network

  • Data tier

    Database

    10.0.3.0/24db-1
    Only from the application network

Restrict each tier's inbound access with firewall rules. For example, open the database port only to the application network range.

Companion services

Combine Private Networking with firewalls and load balancing

Features

What is included

The main capabilities of Private network at a glance.

  • Project network

    Create and manage the network within your project.

  • Connect servers

    Attach your chosen servers to this network.

  • View members

    Review connected servers and network status in the panel.

Use cases

Who it is for

  • Application back-end servers
  • Segmented networks
  • Service isolation
User guide forPrivate network
Recommended

Related services

Services commonly used alongside Private network.

Frequently asked questions

Before you start

What problem does Private network solve?

If servers communicate over the internet, internal connections become harder to control and sensitive components are unnecessarily exposed.

What is Private network suitable for?

Private network supports use cases such as Application back-end servers, Segmented networks, Service isolation. The right choice depends on your project's technical and operational requirements.

How do I get started with Private network?

Read the product guide and estimate costs in the calculator, then create the service in your chosen project in the client panel.

Get started with Private network

Register, estimate costs before provisioning and pay hourly for the time you use the service.

Get startedPricing calculator