Automation & Platform Engineering · United States

Everything fails at the joint.

An astragal is the small, precisely cut piece that closes a joint: the ring where a column meets its capital, the strip that seals two doors into one. That is the work. AI automation and platform engineering at the seams where your systems, your teams and your processes actually meet, so you ship faster and sleep through the night.

Tell us where it breaks Read the thesis

01 · The name

astragal/ˈas-trə-gəl/ n.

From the Greek astrágalos, "knucklebone." The small convex moulding that rings a column where the shaft meets its capital, carved with bead and reel. In joinery, the strip that closes the gap between a pair of doors, so that two leaves shut as one.

Systems do not fail in the middle. The database does not break mid-query and the service does not break mid-function. Things break at the handoff: the integration that assumed a field would always be there, the deploy step only one person understands, the Friday routine where a spreadsheet becomes an email becomes a ticket.

None of that appears on an architecture diagram. All of it decides whether the architecture survives contact with production.

Most consultancies will sell you another component. We are interested in the seams between the ones you already have, because that is where your outages live, and that is where six hours a week are quietly going.

Speed and reliability are not a trade-off. They are the same property, observed from two directions.

Teams that deploy often deploy small. Small changes fail rarely, and when they do, they fail legibly. The organisations shipping fastest are the same ones sleeping best, not despite the pace, but because of it.

02 · Two seams we close

I

AI Process
Automation

The six-hour job that becomes a nine-second job.

Document and workflow pipelines: intake, extraction, routing, and the exception handling that everyone forgets
Agents wired into the systems you already run, not a parallel universe your team has to maintain
Evaluation harnesses, so you find out a model regressed before your customers do
Human-in-the-loop checkpoints placed exactly where being wrong is expensive
Retrieval over your own knowledge, built to be corrected rather than merely queried
An honest read on which processes should not be automated yet

II

DevOps &
Platform Engineering

The deploy that stops being an event.

CI/CD fast enough to actually use and boring enough to actually trust
Infrastructure as code: environments that rebuild from nothing, on purpose, regularly
Kubernetes and container platforms, or a frank conversation about talking you out of them
Observability that answers questions: traces, SLOs, and alerts a human should be woken for
Incident response, on-call rotations designed for humans, and the postmortem habit
Cost engineering, treating the cloud bill as an engineering artefact, because it is one

03 · How the joint gets cut

Joinery has an order of operations, and so does this. Each step produces something you keep, whether or not you continue with us.

01

Survey

Two weeks · fixed fee

We read the code, watch a real deploy end to end, and sit in on an incident if one obliges. We interview the people who get paged. You receive a written assessment naming the three things costing you the most, with evidence, not adjectives.

02

Seam map

Included in the survey

We map every handoff: where a system passes work to another system, where a person passes work to a machine, where one team passes work to the next. Outages and wasted hours cluster at these points, and most teams are surprised by at least one of them.

03

Fit the piece

Eight to twelve weeks

We build, embedded with your engineers, in your repositories, reviewed by your team. No parallel track that gets thrown over a wall at the end. Work ships to production continuously throughout. The engagement is not the deliverable, the running system is.

04

Hand over

The last two weeks

Runbooks, architecture decision records, and a working session with the people who now own it. We consider the engagement successful when you stop needing us. Consultancies that engineer their own indispensability are a failure mode, not a business model.

04 · What we move

Four numbers describe delivery performance. We agree on where yours sit before we start, and we publish them as we go. If a consultancy cannot tell you which of these they are moving, they are redecorating.

Deployment frequency Elite: on demand

How often you can safely release. Frequency is a proxy for batch size, and batch size is a proxy for risk.

Lead time for changes Elite: under 1 hour

Commit to production. This is the honest measure of how much friction sits between an idea and a customer.

Change failure rate Elite: 5–10%

The share of releases that degrade service. Driven down by test design and progressive delivery, not by deploying less.

Time to restore Elite: under 1 hour

Everything fails eventually. What separates teams is how quickly they notice, and how quickly they can put it back.

These are the four DORA metrics, and the benchmarks shown are the published elite-performer bands from the DORA research programme. They are industry reference points, not claims about our own client results. Astragal is a new firm; we would rather show you the standard we hold ourselves to than a wall of logos we have not earned yet.

05 · Ways to work together

Start here

The Survey

2 weeks · fixed fee

A written assessment of your delivery pipeline and automation opportunities, with a prioritised seam map and cost estimates. Yours to keep and act on with any team you like, including your own.

Embedded Build

8–12 weeks

We join your engineering team and ship. Automation pipelines, platform work, or both. Your repositories, your review process, your production environment from week one.

Retained Platform

Ongoing · monthly

For teams without a dedicated platform group. We hold the pager alongside you, keep the foundations current, and stay close enough to catch drift before it becomes an incident.

Begin

Tell us where it breaks.

Not a discovery call. Send us the thing that is actually annoying you: the deploy that takes forty minutes, the process three people do by hand every Friday, the alert everyone has learned to ignore. We will tell you honestly whether it is worth fixing and roughly what it would take.

Email hello@astragal.org

Survey enquiries survey@astragal.org

Based United States · remote-first

Write to us