Software built
around the system.
Embedded firmware, infrastructure applications and connected platforms. Orelink combines software development with the hardware and systems context around it.
From device behaviour
to system visibility.
Software is a defined part of Orelink’s engineering activity, alongside hardware design, testing, quality control and support.
Our software focus includes firmware and embedded software, network and equipment management, IoT platforms and cloud software, and security software. These disciplines connect the behaviour of a device with the applications and infrastructure around it.
We develop our own technology and undertake custom development. The software scope is established for the specific product or engagement, including interfaces, target environment and delivery responsibilities.
Explore the software layers.
Firmware & embedded software
Software close to electronic hardware, including device behaviour and integration boundaries.
Infrastructure management
Applications for understanding and managing networks, equipment and IT infrastructure.
IoT platforms & cloud software
Software foundations connecting devices, data interfaces and application needs.
Security software
Security-focused software with a clearly defined system boundary and validation scope.
A clear delivery model.
- Software licensing
- Software supplied under a licence appropriate to the agreed use and distribution scope.
- Custom development
- Development scoped to a customer’s product, system requirements and integration environment.
- Software with equipment
- Firmware and related software delivered as part of a hardware-based product or system.
The contracting entity, rights of use and delivery responsibilities are established for each engagement. Product-specific terms, publisher identity and support arrangements should be taken from the applicable agreement and delivery documentation.
Define the integration
before the release.
When an engagement includes operating-system integration, the target environment, device interfaces and software responsibilities are defined in the technical scope. This makes the relationship between firmware, device-side behaviour and host applications explicit.
For release planning, the relevant specifications include the software identity, intended environment, version information, integration requirements and the evidence needed to evaluate the result. Requirements for a particular driver or operating system are confirmed for that engagement.
Business and technical enquiries