What is written down, and who can read it.

PUBLIC

What you can read now.

The published set

Privacy, terms, processing, security and accessibility, at /documents

What we would deploy

The catalogue names the systems and lists a selection of their licences

How the work runs

The four long pages, area by area, and what each one does not cover

What it costs

Prices in the /consulting panels, and machine sizes on /sizes

How to leave

/leaving: what is handed over, in what shape, and what we destroy

Write-ups

The blog, which is about our own estate rather than a customer's

That is a great deal of writing about how the work is done and none at all about how to operate a system yourself. The difference is deliberate: the second is the upstream projects' own documentation and it is better than anything we would write about their software.

YOURS, WITH A DEPLOYMENT

The writing that comes with the work.

A deployment is handed over with the documents that make it maintainable by somebody who is not us. They are written during the work rather than at the end of it, which is what makes them true, and they are yours under clause 11 for as long as you want them, including after the contract has ended.

• A runbook per component, written for whoever is on duty at two in the morning rather than for whoever built it
• The configuration repository that builds and maintains the deployment, versioned and readable, with every setting that differs from the default and the reason beside it
• The restore procedure, and what it was measured to take where a restore has actually been run
• A named owner for every component, so that replacing us is a decision rather than an excavation

Project runbooks are supplied privately to the organisation.

Support

Support questions can be sent to hello@ave17.com.