Part A — Administrator guide (Admin Panel)
Part B — Team guide (User Panel)
1. Key concepts
Resource | What it is | Who creates it | Billable |
|---|---|---|---|
Public VLAN | An external VLAN carrying a pool of public IPs. Backs Elastic IPs. | Administrator | No |
Elastic IP | A dedicated public IP for per workload. | Allocated automatically when an instance is created with Elastic IP selected | Yes — rate per Elastic IP, hourly by default (see §9, §17) |
Private Overlay | Software-defined subnet for pod-to-pod communication within your team. No physical VLAN needed. | Team (self-service) | Yes — rate per attached Private Overlay, hourly by default (see §9, §17) |
Private VLAN | Layer-2 attachment onto a customer VLAN. Gives a pod interface directly on VLAN. | Team requests; administrator fulfils | Yes — rate per attached Private VLAN, hourly by default (see §9, §17) |
Floating IP | An IP address that is not permanently assigned to one server or device and can be reassigned or moved to another server when needed, usually for high availability or failover. | — | — |
Part A- Administrator guide (Admin Panel)
2. Prerequisites
The region is active, with at least one controller node initialised.
Each node has a provider interface, chosen when the node is added (see Section 7).
Upstream gateways exist and are reachable for each Public VLAN subnet.
3. Networking Overview
Go to Infrastructure → Nodes → Accelerator → Networking.
4. Managing Public VLANs
4.1 Create a Public VLAN
Go to Networking → Public VLANs and click Create Public VLAN. The wizard has three steps.
Step 1 .
Fill the fields -
Field |
|---|
VLAN ID |
Network Prefix |
Name |
IP Range |
Gateway IP |
Step 2: Underlay Binding. Choosing an interface binds the VLAN to that node and previews the sub-interface it will create.
Step 3- Review. Once confirmed, Click Create.
The VLAN appears immediately as Provisioning and changes to Ready when setup completes.
4.2 Edit a Public VLAN
Each row's ⚙ menu offers Edit and Delete. Edit reopens the wizard pre-filled.
Only Name and IP Range are editable. VLAN ID, Gateway, and Network Prefix cannot be changed after creation.
4.3 Delete a Public VLAN
Delete removes the VLAN from every bound node.
⚠️ Warning: Delete of public VLANs is not allowed as long as there are user workloads consuming the elastic ips backed by this public VLAN.
5. Managing Private VLANs
A Private VLAN exists only as the result of fulfilling a team request. Pending requests appear inside the Private VLANs tab.
5.1 The request-and-fulfil flow
# | Step | Where | What happens |
|---|---|---|---|
1 | Team submits | User Panel → Team → Networking → Private VLANs → Request a New Private VLAN | Region, name, IPAM mode, IP range, optional gateway / prefix / notes. |
3 | Full Administrator reviews | Admin Panel → Networking → Private VLANs | The Pending VLAN Requests panel shows the team, requester email, and every requested field. |
4 | Full Administrator fulfils or rejects | Same tab | Fulfill provisions it; Reject declines it with a reason. Either way the team is notified. |
5 | Team sees the result | User Panel → Private VLANs | A card showing the VLAN ID, CIDR, and Ready. |
5.2 Fulfil a request
1. Go to Networking → Private VLANs.
2. Click Fulfil. The form opens pre-filled from the request.
VLAN ID is assigned here
3. Confirm. The VLAN appears in the list as Ready once provisioned, and the team sees it in their Private VLANs list.
5.3 Edit or delete a Private VLAN
Each row's ⚙ menu offers Edit and Delete.
Editable: Name, IP range (must stay inside the existing subnet), DNS, and DHCP server IP.
Fixed once provisioned: VLAN ID, IPAM mode, and CIDR.
6. Elastic IPs and Floating IPs
6.1 Elastic IPs
Elastic IPs are drawn from a Public VLAN and allocated automatically when a team creates an instance with Elastic IP selected. Administrators do not hand them out individually.
The Elastic IPs tab lists each address with its owning team, backing Public VLAN, attached instance, and status.
The row's ⚙ menu has Edit Elastic IP
With 2 editable fields: Name and DNS Name. The IP address, Public VLAN, and owning team are read-only.
Note: Setting a DNS name records the mapping against the Elastic IP only. Publishing the record in DNS is a separate, external step.
6.2 Floating IPs
Floating IPs are temporary public addresses that follow the instance and are released when it is deleted.
7. Node provider interfaces and VLAN bindings
7.1 Add Node- Provider interface
On Basic details, the platform shows an SSH key to copy onto the node. Once IP, SSH port, and username are filled in.
Check available interfaces connects over SSH and lists the details. There are three states:
7.2 Add Node- VLAN Binding step
The Add Node wizard has three steps: Basic details, Node details, and VLAN Binding.
The VLAN Binding step lists every existing VLAN- Public and Private, choose which provider interface the new node uses for each.
7.3 Node Details- VLAN Bindings
The Node Info card ends with a VLAN Bindings section listing every VLAN the node trunks.
-----------------------------------------------------------------------------------------------
Part B- Team guide (User Panel)
8. Network Policies
Network Policies and Pricing are configured by the platform administrator (Super Admin) in the User Panel, not in the Admin Panel. Team members cannot change them.
Network Policy It governs how much networking a team may consume, separately from what it costs.
Find it under User Panel → Policies → Network policies.
A policy grants entitlements per team, per region across three categories: Elastic IPs, Private VLANs, and Private Overlays. Each region in the policy has an Access setting — No access, Unlimited, or Restricted. Only Restricted reveals the three category rows; each row then carries its own Max <resource> per team setting:
Max <resource> per team | Capacity |
|---|---|
Unlimited (default) | ∞ (read-only) |
Limited | Numeric per-team cap, entered by the administrator |
Restricted | N/A (read-only) |
8.1 Create a Network Policy
Creating a policy is a four-step wizard:
1. Basic policy info.
2. Configure networks. Click Add Region, select the region and choose its Access: No access, Unlimited, or Restricted. The three category rows appear only when a region is selected and Access is Restricted; set each row to Unlimited, Limited (enter the cap), or Restricted.
3. Assign Teams.
4. Review & Create.
9. Pricing networking resources
Pricing is under User Panel → Policies → Pricing. Networking is billable and kept separate from compute:
Networking resources are added through the Add Network Resource button
Billable types: Private VLAN, Elastic IP, and Private Overlay.
For each type you set a Pricing amount and its billing period (hourly by default), plus an optional inclusive amount.
These rates appear in the team's per-instance Resources usage breakdown under a Networking category.
10. How limits and pricing are configured
Your team doesn't configure these, they are set by your platform administrator.
11. Networking Overview
From your team's page, open the Networking tab.
It has four sub-tabs: Overview, Private Overlays, Private VLANs, and Elastic IPs.
Overview:
Option to view Private Overlays, Private VLANs, Elastic IPs each showing how many your team has.
An IP Entitlements card showing, per region, how many Elastic IPs are allocated and how many remain against your team's maximum.
If your team has any, an Available Private VLANs list showing each VLAN's ID, CIDR, and status.
12. Private Overlays
12.1 Create a Private Overlay
Go to Networking → Private Overlays.
Click Create Subnet.
Fill in the fields
Click Create Subnet.
12.2 Delete a Private Overlay
Use the row's Delete action. The confirmation names the subnet if running instances are still using it.
13. Private VLANs
Active connections are shown here
13.1 Request a Private VLAN
Go to Networking → Private VLANs.
Click + Request a New Private VLAN.
In the Request a Connection form fill in required fields
Click Submit request. It stays disabled until Region, Name, IPAM mode, and IP range are filled in.
13.2 After you submit
The request is sent to the Platform admin.
The request appears under View Requests → Your Requests with status Pending.
While it's Pending, you can click Cancel to withdraw it.
Once approved, it appears as an active Ready card in your Private VLANs list.
If declined, the status changes.
13.3 Delete a Private VLAN
Use the card's Delete action. This removes an established connection.
14. Elastic IPs
An Elastic IP is a dedicated public IP address, allotted per instance when you choose Elastic IP as the instance's public IP mode. Every access path for the instance SSH and exposed services switches to that address (see Section 16.2).
The Elastic IPs sub-tab lists the Elastic IPs currently allotted to your team's instances. Click the copy icon to copy an address.
Lifecycle: An Elastic IP is tied to the instance it was allotted to. Deprovisioning that instance releases the IP, and its row disappears from the list.
15. Creating an instance- networking step
The create-instance wizard has a networking step:
Public IP mode: Shared IP (included) or Elastic IP.
Private VLANs and Private Overlays- if your team has them, select which to attach from searchable multi-select lists.
Note: If your team's Elastic IP limit is exhausted, creating an instance with Elastic IP fails.
15.1 Public IP mode in the Instances list
The Public IP(s) column shows a chip for each instance:
Elastic IP- the instance has a dedicated public IP.
Shared- the instance shares a common platform IP. If other instances share it.
16. Instance details- networking
16.1 Overview tab → Networking card
Open an instance, then its Overview tab. The Networking card shows:
Elastic IP- the instance's dedicated public IP address.
Private Overlay- the attached overlay. If there is more than one, it shows name +N more; hover to see each one's name and IP address.
Private VLAN- the same pattern, for attached Private VLANs.
Below the card, an Attached Interfaces table lists each attached Private Overlay or Private VLAN with its IP address and its interface name inside the pod.
This table only appears when the instance has at least one Private Overlay or Private VLAN attached.
16.2 Access tab → SSH and Service Exposure
Once an instance has an Elastic IP, its SSH connection details (IP Address field).
17. Billing- networking
Open your team's Billing tab. Network resources are billed on a consumption basis: you're charged for exactly how long each instance has been provisioned with them, at the rate your administrator sets in the Pricing policy (hourly by default — see §9).
Each Elastic IP, Private VLAN, and Private Overlay attached to an instance accrues cost for as long as the instance stays provisioned. Billing stops only once the instance is de-provisioned.