ROC3
Systems engineering for digital sovereignty

Deep expertise.
Practical control.

We build custom software, connect enterprise platforms and engineer the operations that keep them dependable, across IT and OT, with security, maintainability and sovereignty designed in from the start.

Rigour · Orchestration · Control

WORK

Engineering the whole system

apps · services · automation

Software shaped around the work

Applications, services and automation built for how the organisation actually works, carried from architecture through deployment and operation.

platforms · data · workflows

Integration with operational depth

Enterprise platforms, security tools, identities, data and workflows brought into one coherent system, designed for the day a component fails.

deploy · observe · recover

Operations with clear responsibility

Deployment, observability, access, maintenance and recovery treated as engineering from day one, so systems can be understood, supported and evolved.

METHOD

How we work

Rigour

Understand the foundations. Make the decisions explicit.

We investigate the problem, validate the behaviour we rely on and state limits honestly. Documentation and testable controls are part of the work.

Orchestration

Make the whole system work.

Software, infrastructure, identities, data and people, connected through clear interfaces and purposeful automation, and proven against how production really behaves.

Control

Keep the ability to decide, and to act.

Systems that are observable, governable, recoverable and changeable, with their dependencies visible to the people who run them and answer for them.

SOVEREIGNTY

Engineering for digital sovereignty

Where a system runs, who can reach it, what it depends on and how it can be replaced are design decisions. Our European perspective puts them into the architecture, so each system comes with guarantees its users can understand and boundaries its operators can explain.

Where it runs

Regions, providers and data flows chosen and written down, not inherited.

Who can reach it

Identities, permissions and audit trails designed in, not bolted on.

What it depends on

Every dependency visible, with its failure mode and its alternative.

How it changes

A credible path to maintain, move or replace each part.

ESTATE

Across the enterprise, from IT to OT

Cloud & datacentres EU based in the European Union
  • Microsoft Azure
  • Google Cloud
  • AWS
  • Hetzner
  • OVHcloud
  • Scaleway
  • IONOS
  • STACKIT
  • Open Telekom Cloud
  • UpCloud
  • Proxmox VE
  • VMware vSphere
Enterprise Linux · server & desktop
  • Red Hat Enterprise Linux
  • SUSE Linux Enterprise
  • Ubuntu
  • Debian
  • AlmaLinux
  • Rocky Linux
  • Fedora
  • GNOME
  • KDE Plasma
  • FreeIPA
  • systemd
  • SELinux
ITSM & business
  • ServiceNow
  • SAP
  • Atlassian
  • Opsgenie
  • PagerDuty
SIEM & data pipelines
  • Google SecOps
  • Cortex XSIAM
  • Exabeam
  • Elastic
  • Cribl
SOAR & automation
  • Swimlane Turbine
  • Cortex XSOAR
  • AWX / Ansible
  • n8n
Endpoint & identity
  • Microsoft Defender
  • Microsoft Entra ID
  • Microsoft Intune
  • CrowdStrike Falcon
  • Carbon Black
  • Keycloak
Vulnerability & threat intel
  • Tenable
  • Archer
  • MISP
  • VirusTotal
Network security
  • Palo Alto Networks
  • Fortinet
  • Cloudflare
  • Entuity
OT / ICS
  • Claroty
  • Nozomi Networks
  • Dispel
Platform & observability
  • Docker / Podman
  • Terraform
  • GitLab
  • Grafana
  • Prometheus
  • Thanos