How it's delivered - Your deployment, in three milestones

Your deployment is broken into three milestones, and you approve each one before we move to the next. Nothing goes live until you have signed off on it yourself.

01

Review and written plan

I review your app, confirm I have the access I need, and work out exactly how it will be put online. You get a written plan in plain language: what will be built, what it will cost to run, how long it will take, and anything that needs fixing first.

What you get
A written plan to read and approve.
Milestone complete when
You approve the plan.
02

Test deployment & validation

I build everything your app needs on a private test address only you and I can see. You sign in and confirm it behaves the way it does on your computer, so anything unexpected turns up before your customers can reach it.

What you get
A working copy on a private address you can sign into and try.
Milestone complete when
You sign off that everything works.
03

Launch and handover

I put your app live, you confirm you can reach it, and I hand over written documentation covering every account, password, and security setting.

What you get
Your app live, and the written handover.
Milestone complete when
Your app is live and the handover is delivered.

What’s included

Every Secure Cloud Deployment includes all of this:

From $2,500, depending on the complexity of your deployment, or from $6,000 when your app holds protected records.

  • Where your app runs. Your app on cloud hosting that is set up correctly and secured, in cloud accounts in your name.
  • Your database. Backed up, and reachable only by your app rather than from the public internet.
  • Passwords kept out of the code. Every password and key held in a locked store, so there is no file with your passwords in it for anyone to copy.
  • Everything written down as it is built. Nothing is clicked together by hand, so the whole setup can be rebuilt exactly if it ever has to be.
  • Automated deployments. Your code stored safely in your own repository, with a deployment pipeline set up so future updates go live automatically instead of by hand.
  • A private test address first. Somewhere only you and I can see it, to try before anything goes live.
  • A complete handover. Written documentation of every account, password, and security setting, so anyone you hire next can pick it up without asking me anything.

Twenty minutes, and no pitch.

I'll tell you what I'd fix first in what you've built, and why. No pitch.