Reach customer systems without opening every network.
Give authorized support engineers access to specific customer networks using Reefspan Access, device-bound activation and routing groups.

Your support work happens inside customer environments.
Technology vendors often need network access to deployed equipment and applications at customer sites. Reefspan provides a way to connect those sites and grant engineers access to the networks relevant to their support work.
Access to specific networks
Use routing groups to grant support engineers access to the customer networks required for their work.
Connect customer locations
Customer sites can connect to Reefspan over IPsec IKEv2 using compatible UniFi, Fortinet, pfSense, Meraki and SonicWall firewalls.
Review administrative changes
The platform maintains an audit log of every administrative action, providing a record of changes made through the console.
Define the access before the support session.
Identify the customer networks
Agree which networks the support team needs and how access will be managed.
Connect the customer site
Configure a compatible firewall with a Reefspan IPsec IKEv2 tunnel.
Grant and adjust permissions
Assign authorized engineers to routing groups and change those grants as support requirements change.
Identity and network access under clear control.
Reefspan supports sign-in and MFA through an organization's OIDC identity provider, including Entra ID, Okta and Google. Routing group changes apply to connected users within a minute. The identity and organization model for each vendor-customer deployment should be agreed before rollout.

Let's discuss how you support customer sites.
Tell us how many environments your engineers access, which firewalls customers use and what network permissions support work requires.

