Sign-in helpTalk to Fibmesh
MenuClose

Business pilots

A good pilot has one question to answer.

Choose one connection problem. Agree what success looks like, and how access will be removed.

A small evaluation should settle a real question in your intended environment. A private build tool, client preview or provider allowlist is a better first scope than every device and route in the organisation.

See the illustrative demo ↗

Write the brief first

The pass condition comes before the first enrollment.

Question
Can an approved engineer reach the private build dashboard?
Scope
One supported laptop · one owned server · one access group
Pass
Permitted access works; an unapproved identity has no grant
Exit
Temporary membership is removed and observed state is checked
Illustrative pilot brief. This does not submit an application or establish availability.

Run a useful evaluation

Baseline, enable,
verify, remove.

  1. Baseline

    Know the starting point.

    Record the existing application, listener, platform and ordinary network behaviour. Choose a non-critical first resource.

  2. Enable

    Authorise the smallest path.

    Confirm product, platform and market readiness, then authorise only the path needed to answer the question.

  3. Verify

    Check both sides of the boundary.

    Observe the permitted connection and a relevant negative test. Record the resource’s local apply state alongside the application result.

  4. Remove

    Restore, record and hand over.

    Withdraw temporary access or publication, inspect removal and restoration, and leave the operating owner a clear record.

Plan an evaluation

Agree on the setup,
the owner and the outcome.

A pilot should establish whether a specific connection works safely in the intended environment. Keep it small enough that the outcome and removal can be observed clearly.

Define the pilot question

Write the resource, owner and intended connection in one sentence. An approved engineer may need one private build host, or an integration worker may need a provider-observed outgoing identity.

A portfolio-wide demonstration is not a substitute for that question.

Explore Networks ↗Review deployment options ↗

Prepare the assessment brief

Bring the decisions that define the change and the evidence you will need to close it.

Six decisions to bring to the pilot assessment
DecisionInformation to bring
OwnershipWorkspace administrator and resource/network owner
OutcomeProduct, audience, direction, protocol and traffic scope
EnvironmentPlatform/version, local network and existing constraints
EligibilityIntended market and assessed product/release support
SuccessAllowed and unapproved paths, application result and observations
ClosureRemoval authority, restoration and allocation disposition

Keep production assumptions out of the first test

Choose a non-critical target and a controlled change window. Do not assume HA, a response SLA, global infrastructure or future product support.

Customer and service terms, data practices and actual release readiness require separate review.

Observe both connection and removal

Test the permitted result and the boundary that should remain closed. Inspect local apply state rather than treating a requested policy as success.

Withdraw the relevant grant or rule and verify removal and restoration before deciding to expand.

From brief to conversation

Bring one question.
We’ll discuss the scope.

Contact Fibmesh to discuss the scope, timing and requirements of a pilot. Use the resource plans and availability to prepare your brief.

Discuss a pilot ↗

A conversation does not reserve capacity or confirm acceptance.