Skip to content
afterbuild.dev
$ ssh you@yourserver 'systemctl status yourapp'

We don’t experiment on your server.

That is a different promise from “we never touch it”, and the difference matters. If we never touched your server you would be left to deploy the fix yourself, which is the part you asked for help with. What we mean is narrower and more useful: every attempt, every wrong turn and every restart happens on our hardware. Yours sees the result once, and you are watching when it does.

The four stages

  1. STAGE 01

    We look from the outside

    You send the address of a page that breaks and a sentence about what happens. We open it, reproduce what you described, and write back with the cause.

    Access
    No access to anything.
    Cost
    Free.
  2. STAGE 02

    We work on our own machine

    If you go ahead, we take a copy of the code and run it in a container here. Every attempt, every wrong turn and every restart happens on our hardware.

    Access
    Read access to the repository, or a zip.
    Cost
    Quoted before it starts.
  3. STAGE 03

    You see it before it moves

    A preview on our own server, with test data and empty keys — never your production database and never your real secrets. It shows the shape of the fix. It is not the acceptance.

    Access
    Nothing further.
    Cost
    Included.
  4. STAGE 04

    It goes onto your infrastructure, with you watching

    One command, run against your server. Then we check the routes, refresh an inner page, and restart the machine to prove it comes back on its own.

    Access
    Temporary, asked for in writing, revoked afterwards — or you run the command yourself while we watch.
    Cost
    Included.

Why the preview is not the proof

The one place where our own logic would trap us if we let it.

Everything on this site argues one thing: that an app working in a preview tells you nothing about your own domain. A demo on our server is another preview. It would prove the fix works on our machine, which is not what you are buying.
So the preview at stage three is a courtesy, not an acceptance. The work is accepted at stage four, on your infrastructure, with your certificate, after your machine has been restarted.

What we never do

What you are left holding

Not an app running somewhere we control. The changes as a pull request in your own repository, the deployment configuration committed next to them, and the command that produced the result — so that if you change host next year, the procedure moves with you. Plus a written list of the things we noticed and deliberately did not touch.

Send us the app