Services

DevOps and cloud infrastructure

Servers, backups and deploys you don't have to think about, until the day you need them and they work.

Book a call Or email us

DevOps and cloud infrastructure work covers the servers, deploys, backups and monitoring an app or website runs on. Vyorde does it for small and mid-size companies and startups that have software in production and nobody whose job it is to make sure it stays up, stays backed up and can be released without drama.

What you get

What's included

  • A written inventory of what runs where and who has access
  • Cloud accounts and servers set up or tidied, in your name
  • An automated deploy, with a way to roll back
  • Scheduled backups stored separately, and one restore done on purpose to prove they work
  • Monitoring and alerts that go to a named person
  • An access review: old accounts removed, keys and passwords moved out of the code
  • A recovery document that says what to do when something goes down

What's not included

  • A penetration test or a security certificate. Those come from a specialist firm, and we can prepare the system for one.
  • Fixing bugs in the application itself. That is Maintenance & Support, or a Custom Software project if it is large.
  • Day-to-day care once the setup is done. That is a Maintenance & Support agreement.

You'll probably like this if

  • Your app runs on a server nobody has logged into for a year.
  • You have backups, probably, and nobody has tried restoring one.
  • Every release is a nervous evening with one developer who knows the steps.

How it goes

  1. We take stock.

    What runs where, who has access, how it's deployed and what happens if it breaks.

  2. We fix the biggest risk first.

    Usually backups or access. The boring things that hurt most when they fail.

  3. We automate the routine.

    Deploys, updates and checks, so they don't depend on one person's memory.

  4. We document and hand over.

    A plain description of the setup, and how to recover when something goes wrong.

Every project follows the same five steps. See the full process.

What changes the price

  • How many servers, apps and environments you run
  • Whether there's a migration involved
  • How much downtime your business can tolerate
  • Security or compliance requirements

Tell us what you need and you get a quote in writing before anything starts.

Before you start

  • A list of every server, hosting account and domain you know about
  • The names of everyone who has, or once had, access
  • A description of how a release happens today, even if it is one sentence
  • When the last backup was taken, and whether anyone has restored one
  • How long the business can be offline before it hurts

You don't need all of it for the first call.

Questions about DevOps and cloud

Which cloud provider do you use?

Whichever suits the job and your budget. It runs on your account either way, so you can change providers later.

Can you make us fully secure?

Nobody can promise that. We fix the common gaps, keep access tight and set up monitoring, so problems are spotted early.

Do you need access to everything?

Only what the work needs, through accounts you control and can switch off when we're done.

How long does DevOps work take?

The first look at what you run is short, and our Technical Audit package, 1 to 2 weeks, covers the security side of it. The work that follows depends on what it finds. Setting up backups and monitoring is quick. A migration to a new provider takes longer, mostly because it is rehearsed first, so that the real move is short.

What do you need from us to start?

Admin access to your hosting or cloud account, the code repository and the domain settings, or the person who has them. Anything written down about how releases happen today. And an answer to one question: how long can the business be offline before it costs real money? That decides most of the design.

Who pays the cloud bill?

You do, directly to the provider, on an account in your company's name. We don't sit between you and the invoice. We size things for what you run today and tell you roughly what each part costs before switching it on. If a cheaper setup would do the job, we will suggest it.

What needs doing after the setup is finished?

Updates still have to be applied, alerts answered and backups restored now and then to check they work. The handover document lists these jobs and how often they come round. Your own developers can take them on, or they can go into a support agreement with us.

More questions are answered on the FAQ page.

Want to start smaller?

Try the Technical Audit package first. For a website or web app that feels slow, shaky or invisible, when you want to know why before paying anyone to fix it. Typical timeline: 1 to 2 weeks. The exact dates are in your quote.

See all three packages

Last updated

Not sure your backups work? Let's find out.

Book a call

Or write to us from the contact page.