Services — three ways in

We do the unglamorousparts properly.

Most of our work starts with one of the products and turns into a longer conversation about how a team builds, ships and proves what it shipped. Here's what that usually looks like.

Talk to an engineer

Platform engineering

An internal platform your engineers choose to use: one place to host code, run pipelines and ship, with the paved road paved properly.

Forge rollout and migration from GitHub, GitLab or Bitbucket, history included
CI/CD templates that teams adopt rather than fork
Kubernetes foundations, sized for the team you have
Golden paths for new services, from repo to production
Runner fleets that scale down at night
Hand-over docs written for the people who stay

Typical length

6 – 12 weeks

Who you get

Two senior engineers

You end with

A platform and a team that owns it

Security & compliance

NIS2 and ISO 27001 as engineering problems: controls wired into the tools you already use, evidence collected as a side effect.

NIS2 gap analysis against Article 21 measures
ISO 27001 readiness, Annex A mapped to real systems
Identity clean-up: SSO, MFA and offboarding on Auth
Scan in every pipeline, triaged by reachability
Supplier and supply-chain inventory
An auditor walkthrough we sit in on

Typical length

4 – 10 weeks

Who you get

Security engineer + compliance lead

You end with

Evidence in Comply, not a binder

Run & operate

We run the stack for you, day and night, in EU data centres, and we tell you exactly what happened whenever something does.

Managed Forge, Auth, Gateway, Scan and Comply
24/7 on-call with a named escalation path
Upgrades on a published calendar, never a surprise
Backups we restore from monthly, on purpose
Plain-language incident write-ups within five days
A quarterly review with numbers, not adjectives

Commitment

Monthly, 12-month SLA

Uptime

99.95% per product

Where

EU only, two regions

How an engagement goes

Four steps, no surprises.

Week 1

Listen

A few calls with the people who do the work. We read your pipelines before we read your org chart.

Week 2

Map

A short written plan: what we'd change, in what order, and what we'd deliberately leave alone.

Weeks 3 – 10

Build

Small, reviewed changes in your repos. Demo every Friday, even when the demo is a diff.

After

Hand over, or run

Your team takes the wheel, or we keep running it on a Run plan. Both are fine endings.