Shared exchange infrastructure
Peer discovery, names, messages and data publication are treated as connected parts of one layer. Teams can focus on application workflows while using a shared interaction model.
GeoOverlay — a network layer for distributed applications
Connect users, devices and services through a shared network over the internet. GeoOverlay brings together peer discovery, addressing, messaging and data distribution — a foundation for building your own products.
GeoNet is GeoOverlay’s infrastructure layer. Applications use its network capabilities and add their own logic, interfaces and access rules.
Packaged software under your own brand
GeoOverlay is a packaged software solution for a fast business launch. OEM delivery lets you launch the product under your own brand, with agreed branding, domain and capabilities.
The package, licence, hosting, integrations and support are defined in the delivery scope.
See how GeoNet connects applications and peers
Explore the project website for its architecture and an explanation of the network layer. A step-by-step GeoOverlay video with application examples will appear here.
Video overview coming soon
This space will show the network layer, a message’s journey and application scenarios built on GeoNet.
A networking foundation that can evolve with your product
GeoOverlay is useful when exchange between participants becomes an engineering task of its own: finding recipients, delivering data and handling network changes.
Less dependence on a single centre
A distributed architecture enables the design of alternative delivery paths and data placement across several participants. We define and test the failures your service needs to handle during the pilot.
Identity separate from an address
Keys and signed records allow network identity to be associated with a participant rather than only its current IP address. Permissions and trusted parties follow the application’s requirements.
Events and asynchronous tasks
Messaging, presence and result exchange provide a foundation for services and agents to interact. Acknowledgement, storage and redelivery rules are selected for the particular workflow.
Which teams can use GeoOverlay
The starting point is your product’s task and the participants that need to exchange data.
Distributed application developers
A networking foundation for products with multiple interacting participants. Messaging, publication and synchronisation can be designed around your own user journey.
Enterprise communications and integration teams
File exchange, service notifications and interaction between locations. A pilot helps assess how a distributed layer fits the company’s existing infrastructure.
IoT and edge teams
Interaction between devices, gateways and services across different networks. Peer inventory, channel constraints and reconnection behaviour become part of the design.
AI-agent platforms
Task and result delivery between autonomous participants. The network layer can provide a foundation for addressing and exchange, while task execution remains your platform’s logic.
Teams building their own network infrastructure
An opportunity to define the trust model, delivery rules and peer placement for your project. Suitable for exploring the architecture and testing a dedicated network deployment.
How interaction works over GeoNet
The ordinary internet provides connectivity, while GeoOverlay adds its own layer for peer discovery, routing and exchange.
1. Connect the peers
Identify the network participants: servers, computers, gateways or services. For the pilot, we select the configuration, identities and conditions of their interaction.
2. Establish connectivity
Peers discover one another and form delivery paths. The architecture provides for QUIC, fallback TCP transport and intermediary peers for different connection conditions.
3. Exchange messages and data
The application uses names, signed records, messages or file bundles. Data-copy and delivery-acknowledgement requirements follow the scenario.
4. Build an application service
Interfaces and business logic are developed over the network: for example, communication, publication or task exchange. Network capabilities become part of a specific product.
What we define for your implementation
We turn an architectural idea into a testable workflow with clear participants, constraints and outcomes.
Scenario and criteria
Who exchanges data, what is transmitted and how the system should behave during normal operation and failures.
Peers and trust model
Participant roles, key management, access rights and network component placement.
Data and integrations
Message formats, storage, acknowledgements, redelivery and connections to your application.
Operations and handover
Environment configuration, observability, documentation and an agreed support process.
From a task to a GeoOverlay pilot
We start with a limited deployment where the value of the selected approach can be tested.
Select a scenario
Explore the product, participants and reasons for needing distributed exchange.
Prepare the deployment
Specify the build, peer inventory, data and required connections to your systems.
Test behaviour
Walk through working operations, reconnections and agreed failure scenarios.
Plan development
Use the pilot results to agree the implementation scope, further checks and support.
Questions before a pilot
What is GeoNet within GeoOverlay?
It is an infrastructure network layer over the existing internet. It connects peers and provides an exchange foundation that applications use alongside their own logic.
Is this a ready-made messenger or marketplace?
GeoOverlay is a foundation for developing such products. Interfaces, business processes, application data and access rules are designed for the particular service.
What stage is the solution at?
The GeoNet page presents the network layer as beta. Before implementation, we specify the build, available capabilities and pilot criteria, then test them against your project’s task.
Is internet access required?
Yes, GeoNet runs over ordinary network connectivity. Connection methods, fallback paths and behaviour during disruptions are tested under your infrastructure’s conditions.
How do we start and estimate the cost?
Describe the application, participants, data and network conditions. We use this to prepare a pilot scenario, acceptance criteria, scope of work and cost estimate.
Let’s discuss your application’s networking foundation
Tell us who needs to exchange data and where the current architecture limits your product. We will select a useful scenario and prepare a GeoOverlay pilot with a testable outcome.