Engineering · integration
Built to connect,
built to be run.
We build the tools your team is missing and connect the platforms you already run: ServiceNow, your SIEM and SOAR, Azure, Elastic, Tenable and the systems in your plants. Each job is priced from a plan of the work, at one price that holds, and carried from architecture through deployment and operation.
What we build
Four kinds of job, often in one project. Each ends with the result running in your systems.
Table 1 The work, by kind.
-
01 / tooling
The tool your team is missing
What people now do by hand across several consoles: an access review, an asset list drawn from three sources, the monthly evidence for an audit.
-
02 / integration
Platforms that work together
SIEM alerts that open and close ServiceNow tickets, Tenable findings that reach the change process, Azure and Elastic feeding one record.
-
03 / automation
The first steps, the same every time
SOAR playbooks and scripts that gather the facts and take the first safe steps of a response, with a person deciding the rest.
-
04 / OT
Plant systems, on the plant’s terms
Integrations that read from controllers and plant networks without disturbing them, with any change made inside the plant’s maintenance windows.
Built for the day a part fails
APIs change, tokens expire and platforms go down for maintenance. The design starts from that day.
Nothing lost while a link is down. Events wait in a queue and go through once the platform is back.
A quiet link raises an alert. A feed that stops is noticed by a person before the gap matters.
A written way to work without it. Each integration comes with a short runbook: what it does, what to do while it is down, how to bring it back.
Limits stated honestly. Every delivery says what it does, what it leaves out and where its guarantees end.
Four questions every system should answer
NIS2 asks you about your suppliers and the systems they run for you. These are the answers it asks for.
Where
Where it runs
The country, the provider and the account each part runs in, and where its data and backups are kept.
Who
Who can reach it
Every person and service with access, how they sign in, and how that access is reviewed and removed.
What
What it depends on
Every platform, licence and outside service it needs, and what happens when one of them stops.
How
How it could be replaced
What it takes to move it, run it yourselves or change a supplier, written down while the work is fresh.
Each job’s written record answers all four. For our own site, the answers are in our privacy notice.
One price, then run under a plan
Engineering is priced the way every job here is: from a plan of the work.
A plan, then one price. We write down who does what, on which days and for how long, and price the job from that plan. Once agreed, the price holds. How a fixed price is worked out.
Handed over with the record. You keep the runbook, the configuration and the record of what was built and checked.
Run afterwards, if you want. One of our plans can watch it, keep it updated and answer when it breaks. Your own team can run it from the runbook just as well.
Tell us what to build or connect
Name the platforms and what should happen between them. A person reads it and answers within one working day with the questions that decide the plan.
- FirstA first answer. We read what you sent and reply with the questions that decide the plan.
- ThenA plan and one price. Who does what and on which days, for one price that holds.
- LastBuilt, checked, handed over. Running in your systems, with the runbook and the record.