Physical Edge device
A small managed appliance placed on the customer network with a defined purpose, site record and controlled lifecycle.
Oblyx Edge
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.
The business problem
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 Oblyx covers
A small managed appliance placed on the customer network with a defined purpose, site record and controlled lifecycle.
One Edge normally represents one independently managed network boundary; separate sites or isolated networks may need their own device.
Addresses, identity clues, reachable services and permitted local information used to establish what is present.
A continuing record that helps distinguish a known device moving address from an unfamiliar device appearing for the first time.
Selected reachability, service, resource and dependency signals appropriate to the systems and permissions available.
Selected provisioning, registration and local phone visibility as Oblyx Voice and supported device integrations mature.
Evidence that supports an inventory, topology, ownership record and useful change history in Hub.
Edge is not sold as a firewall replacement, general router, compliance certificate, autonomous administrator or magical AI appliance.
A practical workflow
Edge is introduced as part of a managed service with an explicit network scope.
A realistic example
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.
Hub, Edge and the human service
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.
Who it is for
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.
Speak directly with David
A short message is enough to begin. David will reply personally and can work alongside the providers already involved.