Availability
Start with the connection.
Confirm the setup.
Product availability is the first check. Your devices, delivery location and access path need to fit too.
Use this page to prepare a deployment conversation and see which details need separate confirmation.
01 / Network locations
Find your place
in the network.
Explore live and available provisioning locations, and see which products are confirmed for each city.
Explore network locations →- Locations
- 35
- Countries
- 20
- Live locations
- 4
Live in Bengaluru, Mumbai, Delhi NCR, and Jammu. View confirmed products by location.
02 / Product availability
A starting point for
your deployment.
The access state describes how to begin. Confirm the exact configuration before planning around it.
On a narrow screen, scroll the table horizontally. Keyboard users can focus the table area and use the arrow keys.
| Product / service | Access today | Confirm for your deployment |
|---|---|---|
| Networks | Available · assisted setup | Supported devices, private addressing and site routes. |
| Publish | Available · assisted setup | Supported app targets, domains and the scope of the deployed release. |
| Public IPs | Available · assisted setup | Device or gateway delivery, address family, serving location and traffic policy. |
| Routed SubnetsA separate Public IPs managed service | Invitation-led · outside the app MVP | Separate IPv4 or IPv6 allocations; IPv6 /48 through /64. Review requirements, IPv4 stock and the gateway before agreeing delivery. |
| Outbound | Available · assisted setup | Full-tunnel profile, exit location, stable-source allocation and endpoint support. |
Managed service and app release are separate.
An agreed Routed Subnets deployment does not establish a released subnet provisioning API, a self-service workflow or floating-prefix orchestration.
Explore Routed Subnets and delivery requirements ↗03 / Check four things together
Four independent checks.
One agreed setup.
A supported product, a supported package, an eligible deployment and an admitted account answer different questions.
Product
Does it support your connection?
Confirm the capability, traffic behaviour, address family and optional features. A published product explanation does not establish that every configuration can be provisioned.
Bring the resource, audience and traffic scope.
Platform
Can it run in your environment?
Confirm the supported operating system and package version, gateway prerequisites and mobile restrictions. Unverified combinations need assessment before use.
Bring device roles, OS versions and network constraints.
Market & location
Where can it be delivered?
Customer eligibility and service location are different facts. Confirm your country, assigned infrastructure location, available capacity and applicable terms.
Bring the customer country and preferred serving location.
Account admission
How do you enter the service?
An invitation or future signup permits an account to enter the service. It does not enable every platform, market or optional feature; admission remains separate from product support.
Confirm the admission path for the agreed setup.
04 / What needs separate confirmation?
Keep these details
in the brief.
These boundaries remain relevant even when the product is available and the account has access.
- Private IPv6
- Part of Networks product scope. Check automatic private IPv6 assignment against the deployed release before depending on it.
- Direct P2P
- Direct peer-to-peer connections are planned. Current private connections use Fibmesh nodes.
- Public IP traffic
- Inbound, selected outbound and full-tunnel configurations each need the appropriate route, source address and firewall setup.
- Outbound routing
- Current profiles use full tunnel, with one active organisation profile. Per-app and selected-destination routing are not established by availability.
- Publish domains & access
- Custom domains and additional access controls have separate scope. Confirm them alongside the app target and the deployed release.
- Hardware & failover
- Edge appliances remain development/pilot deployment options. An available Routed Subnets service does not imply automated floating-prefix failover.
Prepare the next step
Bring the environment.
Agree the delivery.
Start with the product, device and OS versions, customer country, preferred location and any optional requirements. Use the invitation guidance to understand the access path, and check package publication separately.