Product availability
| Product | 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 release scope |
| Public IPs | Available · assisted setup | Device or gateway delivery, address family, location and traffic policy |
| Routed Subnets · Public IPs | Separate invitation-led managed service, outside the app MVP | Separate IPv4 or IPv6 allocation; IPv6 /48 through /64; IPv4 stock and gateway requirements |
| Outbound | Available · assisted setup | Full-tunnel profile, exit location, stable-source allocation and endpoint support |
Managed-service availability and native-app release scope are separate. An agreed Routed Subnets deployment does not establish a released subnet provisioning API, self-service workflow or floating-prefix orchestration.
Check four things together
The connection you need
Confirm the capability, traffic behaviour, address family and any optional features. A published product explanation is not a promise that every configuration is provisionable.
Where it runs
Confirm the supported OS and package version, including gateway prerequisites and mobile restrictions. Unverified combinations need assessment before use.
Where it is delivered
Customer eligibility and service location are different facts. Confirm your country, assigned infrastructure location, capacity and applicable terms.
04 / Account admission: 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.
Global intent, confirmed delivery locations
Fibmesh is an Indian company building for customers in multiple countries. A country availability list and service-location map have not been published. Treat a requested region as a preference until the actual serving location and allocation are confirmed.
For a provider allowlist, also check whether the provider accepts the assigned source address, address family and location. An IP-geolocation result alone is not a service delivery guarantee.
What needs separate confirmation?
- Private IPv6: within Networks product scope; automatic assignment must be checked against the deployed release.
- Direct P2P: planned; current private connections use Fibmesh nodes.
- Public IP traffic: inbound, selected outbound and full-tunnel configurations need the appropriate route, source address and firewall setup.
- Outbound: current profiles use full tunnel and one active organisation profile; do not assume per-app or selected-destination routing.
- Publish: available with assisted setup; custom domains and additional access controls have separate scope.
- Hardware and failover: edge appliances remain development/pilot options. Available Routed Subnets does not imply automated floating-prefix failover.