A guided platform tour

See how a connection becomes permitted.

Choose a scenario and inspect how identity, policy and delivery define the intended outcome.

Explore products ↗

Fictional resources · No account required

Three ways into the platform

How to use this tour

Start with the idea, inspect the workspace, then follow a connection.

  1. Watch the 53-second film

    See the platform idea.

  2. Open the illustrative console tabs

    Inspect enrolled resources, private access, Publish, Public IPs and traffic choices.

  3. Use the connection explorer

    Follow a request. Switch to Control path to see how policy is applied; change the permission or replay the finite animation.

The tour uses fictional resources. It does not connect to your account, enrol your device or change networking.

Publish is available with assisted setup. Public IPs includes incoming and outgoing routing options. Routed Subnets is a separate, invitation-led managed service, with setup arranged through the Fibmesh team. The explorer’s Public IP scene illustrates inbound access.

01 / Watch the idea

53-second silent film

The fabric, in motion

The internet connects the world. Make it your network.

People. Apps. Places. See how a shared identity and policy foundation brings them together.53 seconds · Silent film · Illustrative

Film transcript

The internet connects people, applications and places. Fibmesh brings them into a network defined by identity and policy: approved private access, deliberate application publication, and a chosen exit for eligible internet traffic. Backend policy defines who can connect, what they can reach and how traffic leaves. Our vision is to make secure connectivity a utility for teams, applications, locations and infrastructure.

Illustrative connection models. Confirm supported endpoints and service locations for your deployment.

02 / Inspect the workspace

Five illustrative views

These views explain how resources and capabilities fit together. They use sample data and do not operate a live account.

On smaller screens, scroll a table sideways to read every column. With a keyboard, Tab to the table and use the arrow keys.

Designed around your resources

A platform you can
find your way around.

Explore the workspace model. Devices, access groups, publication and routing each have a clear place.

fibmeshIllustrative workspace
Workspace / Devices & servers

Start with a resource.

Give supported endpoints a workspace identity. Inspect resources first, then choose the capabilities they need.

LaptopIdentityWorkspace
Sample devices & servers in an illustrative workspace
ResourceRoleIllustrative state
Developer laptopNative endpointEnrolled
Studio serverPrivate application hostEnrolled
Office gatewayInfrastructure boundaryRoute review

Endpoint private keys stay local by default.

Explore Networks

Interactive product walkthrough, based on Fibmesh’s app architecture. Sample resources only; no live account actions or customer data.

03 / Follow a request

Traffic, control and permission

Follow the connection

See the path.
Understand the permission.

Switch between traffic and control. Change a policy decision. See what the connection means.

Data plane / illustrative

A private path between approved resources.

  1. 01Enrolled deviceWorkspace identity
  2. 02WireGuard tunnelExisting internet carries it
  3. 03Fibmesh nodeCurrent node-routed path
  4. 04Private resourceEnrolled target or approved site route

Policy governs the connection and is shown separately in the Control path view.

Illustrative path permitted

Networks permits the private connection under workspace policy. Replies use the established private path. Unrelated internet traffic keeps its existing route. Direct P2P is planned.

A working explanation of the product model. No account, device or network is connected by this demo. Release availability must be verified.

From illustration to your setup

Read the connection.
Then plan the real one.

While exploring, ask these four questions. They turn a diagram into a useful deployment plan.

  1. Who starts the request?

  2. What carries it?

  3. Which rules permit it?

  4. How does the reply get back?