Warranty

What it covers

Everything in the repository. Not a list of covered components with the interesting ones missing from it: if it is in there and we put it there, it is covered for 12 months.

In practice that means two kinds of work. Every finding Aegis escalates to us is fixed at no charge, including the less urgent ones that normally carry a bill on Core. And our own mistakes: if something we wrote doesn’t do what the scope said it would, we fix it and don’t bill you for our own defect.

Graduate builds carry the warranty too, on the same terms. It’s a free build with a 1-year warranty, which we realise sounds like a catch and isn’t one.

Who it actually changes anything for

Worth being straight about: critical fixes are already free on every tier, warranty or not, and the less urgent ones are already inside the fee on Plus and Priority. So for those two tiers the warranty changes nothing, and we are not going to pretend otherwise.

Where it matters is Core. On Core a less urgent fix is normally quoted at £35/hr; during the warranty it is not quoted at all. If you take the cheapest hosting tier with a new build, your first year carries no Aegis bills of any kind.

When it starts, and when it stops

It runs from the day your build is finished and handed over, not from the day you first spoke to us and not from the day hosting starts. 12 months later it lapses, and the normal tier rules apply again with no change to your bill and no renewal to decline.

What it depends on

Two conditions, and no others.

One: the site still lives in the repositoryRepositoryA safe online folder holding your website’s code, with a full history of every change. Yours lives in your own account, like a deed in your name.more in the glossary we built it in. Copy it elsewhere and carry on from there and the warranty stays with the original, because that is the code we can actually vouch for.

Two: nobody but us has changed the code in it. Once a commit lands from an author who isn’t us, the warranty ends. There is no clause about misuse, no list of forbidden actions, and nothing that depends on our opinion of what you did.

Both conditions come from the same place: the warranty is a promise about code we wrote, sitting where we left it. Once that stops being true we can no longer tell you with a straight face that the thing we are guaranteeing is still the thing we built. We’d rather say that plainly than write a warranty full of escape hatches and lean on them later.

To be clear about what this is not: it is not a restriction. The repository is yours, and you can hand it to any developer you like, whenever you like. That is the entire point of how we work and the warranty doesn’t buy us a veto over it. You just lose the guarantee at the same moment, because it stopped being only our work.

Editing your own content through Pantheon does not void anything. Pantheon commits as us, so everything you do through it, every page, every image, every price you change, counts as our authorship. Use your own website as much as you like.

And because the repository is in your name, you can check this yourself. The commit history lists every author. Nobody has to take our word for whether the warranty still stands, including us.

What it isn’t

It is not a support contract and it is not insurance. New pages, new features and changes you ask for are build work, and they come out of your quarterly build hours or are quoted, the same as always. It is not a second chance to change the scope either: what the build was agreed to be is what it was agreed to be, in writing, before it started.

If you sell the business

The warranty goes with the website, because it is attached to the repository rather than to you. Hand over the repo and the new owner gets whatever is left of the 12 months, on the same two conditions. Nobody has to tell us, and there is nothing to re-apply for.

Anything here you want in writing for a specific situation, ask: hello@page-flow.co.uk