What would you like to know?

Fibmesh connects people, applications and infrastructure over existing internet connections. Use it to reach private resources, make a selected service public or choose how internet traffic leaves a device or network.

Networks connects private resources. Publish shares selected web applications through public hostnames. Public IPs provides routed public addresses. Outbound sends eligible internet traffic through a selected exit. They share identity and access policy, but you can choose them independently.

Fibmesh’s public products work over an existing internet connection. Keep your broadband, mobile or cloud provider; Fibmesh adds the selected private connections, public reachability or outgoing route. It does not replace the underlying connection.

Networks is designed to connect supported devices and resources across homes, offices and cloud environments. Join devices individually, or use a supported gateway to reach approved resources at a site. Network access still follows your policy.

A supported gateway can provide routed access to approved LAN addresses, including servers, storage and IP-accessible equipment. Applications and protocols must work over a routed network. Local broadcast discovery and every printer or scanner feature are not automatically carried across sites.

Keep the application’s own authentication and permissions. Being able to reach a server does not give someone permission to sign in or read its data.

No. Publish, Public IPs and Outbound can be selected independently. A workspace, an enrolled target where required and the relevant access permissions still apply.

Public IPs gives a supported device, gateway or subnet a public address and supports incoming or outgoing uses according to its configuration. Outbound chooses an exit for eligible outgoing internet traffic. Both may help with address allowlisting; choose based on whether you need a routed public address, an internet exit or both.

A routed subnet delivers a block of public addresses to a supported deployment through a tunnel. IPv4 and IPv6 subnets are separate allocations; the IPv6 offering covers /48 through /64. Availability is invitation-led and depends on allocation and deployment requirements.

Where supported, Public IPs can provide inbound access while unrelated outgoing traffic uses your existing route, send selected outbound traffic through Fibmesh, or use a full-tunnel configuration. Replies to incoming Fibmesh connections must return through Fibmesh. Routing and inbound firewall choices are separate.

Yes. Separate public hostnames map to selected applications and ports, even on the same machine. A request reaches a Fibmesh gateway, then travels through a WireGuard tunnel to the target application. Contact Fibmesh to arrange the supported setup.

Publish uses Fibmesh subdomains and gateway-managed HTTPS. Custom domains remain a planned extension. The Publish guide explains where HTTPS terminates and how to protect the final application hop.

Supported private workspace DNS belongs within Networks. It helps members find private resources by name through the configured resolver. The resource still needs a working route, access permission and its own application authentication.

Use the supported Fibmesh software and enrolment flow for the platform, or a supported gateway for resources behind it. Manual WireGuard profiles are Compatibility Mode. A gateway connects approved LAN routes; it does not enrol every device behind it as an independent Fibmesh device.

An enrolled device has a Fibmesh device ID and private addressing for the network. The approved design includes a private IPv4 address from shared address space and private IPv6. Addressing, assignment and platform support must match the actual deployment; an IP address is not a substitute for authentication.

Current network paths use Fibmesh nodes. Direct peer-to-peer connectivity is planned. Do not assume a direct path, automatic relay fallback or latency benefit before those capabilities are released.

WireGuard is the available tunnel protocol. Supported native software handles the platform-specific connection. A manual WireGuard profile is Compatibility Mode and does not provide the full managed device experience.

There is CLI and API coverage for selected operations; it differs by product. Networks and Public IPs document their supported commands. Outbound currently exposes egress list in the CLI; this is not CLI provisioning. Publish CLI commands remain proposed examples; the available service uses assisted setup.

Edge hardware remains in development and pilot use. It is a deployment option for connecting resources at a site, not a generally released hardware range. Confirm the supported device, software, installation and support arrangement before planning a rollout.

Full tunnel sends eligible traffic through the configured exit. Local routes, platform-controlled traffic and defined exceptions can remain outside it. IPv6-only deployments also need an explicit policy for IPv4. Check the platform and failure behaviour; do not assume a universal kill switch.

Networks, Publish, Public IPs and Outbound are available with assisted setup. Contact Fibmesh with the resource, platform and locations you need to connect so we can confirm the supported deployment and next steps.

Setup is currently assisted. A future self-service route would need its own release and eligibility details; product availability does not mean every platform, country or optional capability is supported.

Fibmesh is an Indian company building for customers across countries. Eligibility depends on the product, service location and supported platform. Confirm the proposed deployment rather than assuming worldwide availability.

Public packages, fees and allowances are being finalised. The pricing page explains the factors behind an offer, including addresses, deployment scope, traffic and support. Planning figures are not purchase offers.

Note the product, device platform and version, what you expected and what happened. Use your agreed support contact for an existing deployment. Remove passwords, tokens and private keys before sharing diagnostics.

The status page is not connected to live monitoring yet. A status-unavailable message is neither a healthy-service confirmation nor a confirmed outage.

Vikram Gupta leads Fibmesh as Founder & CEO. Shivali Bakshi and Sonali Wankhede serve on the board. The company’s work grew out of broadband infrastructure and now focuses on programmable connectivity.

Integrators, service providers and equipment vendors can explore collaboration around a specific customer deployment. Start with the customer’s need and agree installation, operation, support and access responsibilities.