Buyer guide
Does my small business need a DevOps engineer or a system administrator?
In short
A system administrator keeps servers, networks and accounts running day to day. DevOps work automates how software is built, released and monitored so that releases are repeatable. A small business with one app often needs a little of each, part time, rather than a full-time hire of either.
Who is this guide for?
Owners of a small business that runs its own app, website or servers and are unsure whether to look for a DevOps engineer, a system administrator or neither.
What a system administrator does
A systems administrator installs, configures and maintains an organisation's computer systems, keeps them secure, manages user access, improves performance and troubleshoots problems. That is the common description of the role, and the UK government's role framework puts infrastructure engineers in a similar space: designing, building, managing and supporting the infrastructure services that other services rely on.
The work is largely about keeping things running: servers, email, storage, user accounts, updates and backups.
What DevOps work covers
AWS describes DevOps as a combination of cultural philosophies, practices and tools that helps organisations deliver applications faster. Its practices include continuous integration, where code changes are regularly merged and tested automatically, continuous delivery, where changes are prepared for release, infrastructure as code, and monitoring and logging.
In practice this means releases are made by a repeatable automated process and not by one person copying files, and that the setup of servers is written down as code.
How they differ and overlap
Google's Site Reliability Engineering book contrasts the traditional sysadmin model, where people handle change and events manually, so that the team grows with the load, with an approach where software engineers build automation. It says the traditional split between developers and operations also creates indirect costs, because the two groups have different incentives.
For a small business the line is blurry. The same person may do both. What matters is which problems you have: unreliable servers and accounts point to sysadmin work, while slow, risky or manual releases point to DevOps work.
What a small business usually needs
If you have one or two applications, the need is typically a small, well-documented setup: automated deploys, backups that are tested, monitoring that alerts someone, and a clear list of who has access. That rarely justifies a full-time hire.
A part-time engineer who sets this up and maintains it, with a runbook your team can follow, is often enough. If you have many servers, strict compliance needs or a large team shipping daily, a dedicated hire starts to make sense.
Questions to ask a candidate
Ask how releases would be made and how to go back if one fails, how backups are tested, who gets alerts and what they do, and how access is added and removed. Ask them to write the answers in a short document you keep.
Check that the cloud accounts and servers stay in your name, and that the setup can be understood by someone else if the person leaves.
How do the options compare?
| System administrator | DevOps engineer | |
|---|---|---|
| Main focus | Keeping systems and accounts running | Repeatable build, release and monitoring |
| Typical tasks | Servers, updates, access, backups, support | Automated deploys, infrastructure as code, alerts |
| Signs you need it | Servers and accounts are unreliable or untidy | Releases are manual, slow or frightening |
| Small business fit | Part time or through a provider | Part time, often alongside the developer |
What should I check before I sign?
- You can name the problem: unreliable systems or risky releases.
- Releases are made by a documented, repeatable process.
- Backups exist and a restore has been tested.
- Someone receives alerts and knows what to do.
- Access is listed, and removed when people leave.
- Cloud and server accounts are in your name.
- The setup is written down so another person can take over.
- You have considered part-time help before a full-time hire.
How pricing works
I quote in writing after a short discovery call, against a written scope. Building an app from scratch? The app cost calculator gives a first range in two minutes.
What else do people ask?
Can one person do both?
In a small business, often yes. The same engineer can keep servers healthy and automate releases. What matters is that it is written down.
Do I need either if my app runs on a managed platform?
You may need less, since the provider runs the servers. Someone still has to manage releases, access, backups and costs.
Is DevOps just a new name for a sysadmin?
Not exactly. The two overlap, but DevOps work centres on automating build, release and monitoring, while sysadmin work centres on running the systems.
When should I hire full time?
When you run many systems, ship changes daily or face strict compliance needs. For one or two applications, part-time help is usually enough.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
How can we work this way together?
- Server Care PlanIn the server care plan I look after your Linux servers and deploys month by month: updates, backups that are actually tested, monitoring, nginx and Docker setups, and releases with a way back.
- Cloud Cost ReviewIn the cloud cost plan I read your AWS or cloud bill against what you actually run, explain it in writing and then, month by month, remove waste, right-size servers and storage and test every change on the live system.