Consulting.
Advice from people who run a cloud.
Architecture, Kubernetes, compliance and sovereignty. Our engineers review your setup, write down what they find and help you decide what to do next.
Scoped per engagement, fixed price after the first call.
What we help with.
Four kinds of questions.
Architecture reviews
Where your setup is fragile, slow or expensive, and what to change first.
- Reliability and failure modes
- Performance bottlenecks
- Cost and right-sizing
Kubernetes strategy
Whether Kubernetes fits, and how to run it well when it does.
- Cluster and tenant design
- GitOps and release flow
- Upgrades, scaling and observability
Compliance preparation
The infrastructure side of NIS2, DORA and GDPR, ready for your auditors and legal team.
- Gap analysis against the requirements
- Documentation of operations and access
- Supplier and data-location questions
Sovereignty strategy
How dependent you are on US clouds, and a realistic plan to reduce it.
- Inventory of US services and data flows
- Exit plan with priorities and costs
- Jurisdiction and vendor risk
How we work together.
Three formats.
Review
A fixed-scope look at one setup or one question, ending in a written report.
Readiness assessment
Your infrastructure measured against NIS2, DORA or a customer audit, with the gaps and the evidence you still need.
Advisory
A standing contact for architecture decisions, design reviews and second opinions, billed monthly.
How an engagement runs.
Five phases, each with a result.
- 01
Scoping
What we do- A call with your technical lead
- Agree on the question, constraints and stakeholders
- NDA and access rules, if needed
What you getA written scope with timeline and fixed price
- 02
Discovery
What we do- Interviews with engineering, operations and security
- Read-only access to accounts, clusters and repositories
- Existing docs, incident history and invoices
What you getAn inventory of systems, data flows and dependencies
- 03
Analysis
What we do- Failure modes, bottlenecks and single points of failure
- Cost breakdown by service and team
- Access, secrets and network exposure
- Mapping against NIS2 Art. 21 or DORA, where relevant
- Dependencies on US providers and where data flows
What you getFindings with evidence, each rated by risk
- 04
Recommendations
What we do- A target architecture that fits your team
- Actions ranked by impact and effort
- Phased roadmap with cost estimates
What you getThe report, diagrams and a readout for engineering and leadership
- 05
Follow-through
What we do- Answer questions while your team implements
- Review changes before they reach production
- Or hand over to Migration or DevOps as a Service
What you getA follow-up review once the changes are in
What the report contains.
Written for both audiences.
- 01Executive summaryThe answer, the risks and the cost, on two pages for leadership.
- 02Current stateDiagrams of systems, data flows and dependencies as they are today.
- 03FindingsEach finding with evidence and a rating: critical, high, medium or low.
- 04Target stateThe recommended architecture and why it fits your team.
- 05RoadmapPhases with effort, cost and the order that keeps risk low.
- 06AppendixRequirement mapping for NIS2, DORA or GDPR, and the raw data behind the findings.
When you want more than advice.
We can also do the work.
Questions.
About consulting.
What does consulting cost?
Every engagement is scoped individually. After the first call you get a fixed price for the agreed scope.
Do we have to move to enum?
No. You get the findings either way. If enum fits your needs, we tell you how; if something else fits better, we tell you that too.
Are you lawyers or auditors?
No. We cover the infrastructure side of NIS2, DORA and GDPR and work alongside your legal, compliance and audit teams.
How long does an engagement take?
Most reviews take days to a few weeks, depending on the size of the setup and the question.
Have a question about your setup?
Talk to an engineer.
A short call to understand the question. Then a scope and a fixed price.