Skip to content
The anchorage of a suspension bridge, steel cable strands fanning out into a massive concrete block.

Service 02 · From vibe to viable

You shipped in weeks. We make it last years.

For vibe-coded and AI-generated products. You built a working product with AI in weeks, on your own, and the part only you could do is done. We turn it into software that holds up in production.

Book a readiness review
  • You proved the idea with a thing that runs
  • What is left is known work at a known price
  • One read of your repository shows what it takes
  • You choose what gets fixed first

Example record

What your first read shows

So you see what breaks first, in the order it pays to fix.

Yours comes back with a price against each line.

hardening · first read of your repositorySample log

  • Secrets committed to the repository

    keys in history, still valid

    Fix first

  • Tests on the payment path

    none found

    Fix

  • Load on your busiest day

    not measured yet

    Measure

  • Dependency licences

    one with unclear terms

    Check

  • Deploys from a clean checkout

    reproducible

    Holds
A half-finished concrete building wrapped in scaffolding at dusk, the lower floors glazed and lit.

Where you stand

It stands. Now it has to last

Your product works. What it needs now is the work that keeps it standing as you grow.

Client concept poster
A concept poster titled THE AI POLICE. An officer with a clipboard asks a small robot for licence, tests and documentation. The robot, sitting in a car taped together from browser windows, answers that it works on its laptop. A road sign points to production.

Not an Oxagile service mark

Somebody drew the problem before we wrote the page

A client sent this over after working with us. It is a joke, and the most accurate brief this engagement has had.

  • 01Licence, tests and documentation, please
  • 02But it works on my laptop
  • 03Production, that way

What you already got right

Most software dies before it works. Yours works, so you start ahead.

  • Your validated idea is the spec we start from

  • The code you wrote is characterised, not replaced

  • The feedback you already get sets the fix order

  • The parts that matter most are hardened first

Speed was the easy win

A demo is cheap now. What turns yours into a business is the work left to do.

A building frame in scaffolding at dusk, the lower floors clad and lit, the upper floors still bare steel.
  1. A

    A prototype proves the idea. A system earns the revenue

  2. B

    A fix now costs a fraction of a rewrite later

  3. C

    You keep the same speed, once it is safe to go fast

Capabilities

What we harden for you

Your 5 fixes, in the order they pay off.

01Secrets where they belongYour keys out of the repository, into a managed storeLeast privilege on each service accountHistory cleaned where a key already travelled
02Tests that let you move fasterYou change code knowing what it did beforeCharacterisation tests first, recording what it does todayRun by the pipeline on each commit
03Scale that holds on your best dayA cost per user you can put in a planThe query that dies at 10,000 rows, found firstYour headroom measured and written down
04Licences you can take to a buyerOne fewer question in your due diligence roomEach dependency licence named and checkedA written position on what your output is
05A system your team can runYour team deploys from a clean machineDecisions written down and keptA named owner, and a handover to your team

Then you keep the speed

The hardening pass is where you start. What you build after it is the point.

  • Agent speed, with a named person signing each release

  • Your team learns to build with the agents

  • The same process we run on our own work

Model

What we fix, and what you decide

What we fix

  1. F1A written assessment before code changes start
  2. F2Security closed as committed checks
  3. F3Characterisation tests before a rewrite starts
  4. F4Licence and IP position, in writing
  5. F5A deploy that runs from a clean machine

What you decide

  1. C1Harden what exists, or rebuild one part of it
  2. C2Your team keeps the code, or we run it
  3. C3How far you push with agents afterwards

Related

Where to go next

Next step

Send us the repository.

What you get: what breaks first, a price against each fix, and where we would start.

Book a readiness review →