A local point of visibility for the network David helps you manage.

Oblyx Edge is a small physical device placed inside an independently managed business network. It helps establish which devices are present, retain useful identity and history, run appropriate health checks and connect that local evidence to Oblyx Hub.

Remote dashboards rarely explain the complete local environment.

Cloud portals can show a phone system, Microsoft 365 tenant or backup job while leaving the switches, printers, local servers, UPS devices and unknown equipment between them undocumented. A support provider can therefore know each product without holding a reliable site picture.

Edge gives David an appropriate local vantage point. It supports evidence and continuity of understanding; it does not make every discovered device safe, owned or correctly configured.

What Edge is designed to see—and what it is not

Physical Edge device

A small managed appliance placed on the customer network with a defined purpose, site record and controlled lifecycle.

Network boundary

One Edge normally represents one independently managed network boundary; separate sites or isolated networks may need their own device.

Device discovery

Addresses, identity clues, reachable services and permitted local information used to establish what is present.

Identity and history

A continuing record that helps distinguish a known device moving address from an unfamiliar device appearing for the first time.

Health monitoring

Selected reachability, service, resource and dependency signals appropriate to the systems and permissions available.

Phones and provisioning

Selected provisioning, registration and local phone visibility as Oblyx Voice and supported device integrations mature.

Network documentation

Evidence that supports an inventory, topology, ownership record and useful change history in Hub.

Clear boundaries

Edge is not sold as a firewall replacement, general router, compliance certificate, autonomous administrator or magical AI appliance.

From installation to a maintained working picture

Edge is introduced as part of a managed service with an explicit network scope.

  1. Define the boundaryAgree the site, network segments, management ownership and permitted discovery approach.
  2. Install safelyConnect the device with outbound management access and no assumption that it should replace existing gateway services.
  3. Establish identityDiscover visible devices and reconcile evidence with business and supplier knowledge.
  4. Build the Hub recordConnect devices, roles, history, suppliers and outstanding questions to the wider customer picture.
  5. Monitor proportionatelyEnable only relevant checks and review changes rather than generating alerts without ownership.
  6. Maintain and improveUse the evidence during reviews, faults, supplier conversations and planned change.

Example: the same switch fault appears as three separate problems

Users report slow access, several phones unregister and a wireless access point disappears. Separate portals show symptoms but not the shared local dependency. Edge can support the local history and reachability evidence that helps David trace the events to one switch or uplink, then coordinate the responsible provider.

How Edge is managed and connected

The management approach is outbound-only where deployed as designed: Edge initiates its secure management connection rather than requiring a general inbound management port exposed from the internet. Exact access and data handling are documented for each implementation.

Hub holds the customer-facing inventory, relationships, actions and history. David interprets the evidence, confirms uncertain findings and decides what should be investigated. Several independently managed sites normally mean several Edge devices connected to the same Hub picture.

For networks that deserve a maintained local record

  • Businesses relying on local networks, phones, servers or managed equipment
  • Multi-site firms that need consistent visibility without pretending every site is one network
  • Customers whose systems are divided between several specialist suppliers
  • Organisations beginning with a Health Review and moving towards ongoing management
Available now and developing

The physical Edge platform, controlled local connectivity, selected provisioning and operational checks exist within the Oblyx staging and managed-service direction. Broader device classification, topology, dependency inference, phone visibility and resilient local services remain developing capabilities and will be introduced only when ready.

Discuss Oblyx Edge

A short message is enough to begin. David will reply personally and can work alongside the providers already involved.

Arrange a conversation