Why Arcline exists

The gap is between twenty and two hundred people.

I'm Blake. I have spent eight years running production infrastructure: Kubernetes on Azure and AWS, SLOs and on-call, Terraform and GitOps, and the networking underneath all of it. Much of that has been in regulated places — crypto custody serving a million API requests a day, insurance, banking — where an outage is expensive and a control that exists only in a document is worse than useless.

There is a size of company that falls through the gap. Past about twenty engineers, the platform is too important to run on habit, but not yet large enough to justify a full-time site reliability engineer. So the cloud bill grows, on-call is whoever answered, and the audit is survived rather than passed.

Arcline exists for that company. The audit finds what the platform costs and what it risks. The retainer keeps it honest month to month. The platform work turns compliance controls into code, so the evidence exists before the auditor asks.

Blake Ridgway, Founder

Who you work with

One engineer, start to finish.

Blake Ridgway

Founder, Site Reliability Engineer

Scopes and delivers every engagement, from the first conversation to the handoff. Eight years of production Kubernetes, Terraform, and on-call in regulated environments.

What that means

There is no account manager, no delivery team, and nobody else to escalate to. The person who scopes the work is the person who does it, and the person you call when it is going wrong.

It also means a deliberately small number of engagements at once. If Arcline cannot do the work well, it says so rather than taking it.

Values

What we stand for.

You own it

The systems, the credentials, and the documentation belong to you. We earn the next engagement instead of locking you into this one.

Evidence over assertion

A control that only exists in a policy document is not a control. We build the thing that produces the evidence.

Fixed price

Every engagement is quoted before work begins. No hourly billing, and no change order because the work was harder than expected.

Plain English

Findings are written for the person who has to decide, not for the person who wrote the tool. Technical detail is available when wanted.

Honest claims

We do not promise 24/7 staffing, and we do not promise a smaller cloud bill. We promise what we can prove and say so when we cannot.

Handover, not lock-in

The goal is a team that no longer needs us. Every engagement ends with runbooks, documentation, and a handoff session.

Want a second opinion on your platform?

Tell us what you're dealing with. We'll work out what you need and give you a fixed-price quote. Scoping conversations are free, and we reply within 24 hours.