Cloud-Based Help Desk Software vs Self-Hosted: What You Are Actually Choosing

Tuesday, 14:20, at Brennan Fabrication, a ninety-person engineering firm with a machine shop, an office and one IT administrator called Dev. The operations director has forwarded an article headed "Why Every Modern Business Needs a Cloud-Based Help Desk" with the note "we should be on one of these, surely?" Dev's shortlist for replacing the support mailbox already has three cloud-based help desks on it and one that would run on the firm's own server, and he has been putting off the recommendation because every brochure uses the same four words and none of them says what the words mean. The director's "surely" is the question he has to answer by Friday. Cloud is the modern way, isn't it? The honest answer is "that depends on what you mean by cloud, and on four things about Brennan that no brochure knows", and this article is that answer written out.

Cloud-based help desk software is a help desk that runs on the vendor's servers, which you reach over the internet and never install. Self-hosted help desk software runs on a server your organisation controls, whether that server is in your building or rented from a hosting company. The two words that cause most of the confusion are web-based and online, which describe how people reach a tool and not where it runs: a self-hosted desk is also used in a browser, and it is online for everyone who uses it. This article is part of our Choosing a Ticketing System series. Its sibling, Hosting and Licensing Models in Plain Words, covers hosting and paying together with a total-cost worksheet. This one takes only the hosting half and goes further into it, because "should we be on a cloud-based help desk?" is the question most desks are actually asked.

It covers the three words and the two things they describe. Then come what you actually buy with a cloud-based desk and what you actually give up, each written as a credit or a cost rather than a slogan. It covers the hybrid nobody mentions, which is your own software on a rented server, and who should choose cloud-based and who should self-host, by situation rather than by fashion. There is a table that decodes the seven claims on every cloud brochure, a short war story, and a one-page decision sheet to copy.

One disclosure before we start. QuerySolv, whose team publishes this library, is a self-hosted help desk, so it sits on one side of the line this article draws. Read the self-hosted sections with that in mind and hold them to the same standard as the cloud ones. The firm in the story is fictional. The afternoon it describes is not unusual.

Three Words, Two Things

"Cloud-based", "web-based" and "online" are used as if they were one word, and the brochure that uses all three on one page is relying on you not to separate them. They describe two different things. Where the software runs is one question: on the vendor's servers, or on yours. How people reach it is another: through a browser, or through a program installed on each machine. Nearly every help desk made in the last fifteen years is reached through a browser, so "web-based" and "online" are true of almost all of them, including every self-hosted one. When a brochure says "web-based", it is telling you that the technicians will use a browser, which they would anyway. When it says "cloud-based", it is telling you where the data lives and who runs the server, which is the thing that matters.

Put the two questions in a grid and the market sorts itself. Vendor's servers, reached in a browser: that is cloud-based, and it is the shape of most help desks sold today. Your servers, reached in a browser: that is self-hosted, and it is just as web-based as the first. Your servers, reached through an installed program: that was the shape of help desks twenty years ago and is now rare. Vendor's servers, reached through an installed program: that exists for some mobile apps and nothing else. So the real choice is the first column against the second, and the words to use for it are cloud-based and self-hosted. "Online ticketing system" is not a third option. It is either of the first two, seen from a requester who does not care where the server is, and should not have to.

Two more words belong in the glossary. "Hosted" usually means cloud-based, and sometimes means that a reseller runs a self-hosted product on their own servers for you, which is cloud-based from your point of view with a smaller company behind it. "SaaS", software as a service, means cloud-based and paid for as a subscription, which is nearly always how cloud-based desks are sold. The pairing matters, because the price model arrives attached to the hosting model, and the series article on hosting and licensing models is about pulling them apart. This article leaves the money mostly alone and concentrates on where the thing runs, because that is the question the director asked.

What You Actually Buy With a Cloud-Based Desk

The credits are real, and a desk that is honest with itself writes them down before it writes the costs. First, there is no server. Nobody buys one, finds a place for it, patches it on a Tuesday evening, or explains to the director why it needs replacing in year four. For a desk with no spare machine and nobody whose job includes looking after one, this is the whole decision, and the rest of this article is for people who have the machine and the person. Second, there is no upgrade project, ever. New versions appear, usually overnight, and the vendor's people did the testing. Third, anyone can reach it from anywhere with a browser and a password, which for a firm with technicians at home, on client sites or on the road removes a whole category of remote-access arrangement. Fourth, the vendor's entire business is running this one application, and on average they will run it with more redundancy, better monitoring and faster patching than an administrator who runs it alongside forty other things. Fifth, it scales without anyone noticing. Ten tickets a day or a thousand, the same page loads.

Each of those is a thing you would otherwise have to do, and the cloud-based desk does it for you for as long as you pay. That is a fair trade for many desks and the right trade for some, and the point of listing the credits first is that the costs below are not an argument against cloud-based desks. They are the other side of the same ledger, and a decision that reads only one side is a preference wearing a worksheet.

What You Actually Give Up

The first cost is where the data is. Every requester's name, every internal note a technician wrote about a difficult user, every attachment, every e-mail into the desk, in a building you have never seen, under a contract that says what the vendor may do with it and a law that depends on where the building is. For a design studio this is a shrug. For a clinic, a school, a law firm, a housing association or an engineering firm with defence customers it is a question somebody with a title has to answer, and the honest answer is often that the data may not go there at all. When that is the answer, hosting stops being a preference and becomes a filter, and half the market has excused itself before any feature is compared.

The second cost is change on somebody else's schedule. The buttons move the week the new technician starts, the workflow screen is redesigned in the month you wrote the training guide, a feature you built a process around is retired with ninety days' notice. None of this is malice. It is what "always up to date" means from the receiving end. The third cost is the connection. A cloud-based desk is reachable from anywhere with an internet connection and from nowhere without one, including the inside of your own building when the line is down, which is the afternoon when the most people are trying to reach the help desk. The fourth cost is outages you cannot touch. When the vendor's platform is down you read a status page and wait, and your technicians stand next to a system they could not fix if they were allowed to. The fifth is the exit. What you can export, in what format, and how long after you stop paying the data stays available are clauses in a contract, and they decide whether leaving in three years is a project or a rescue. Migration Cost Is Part of the Decision costs that project; the clauses decide whether you get to run it.

The sixth cost is not a cost of cloud hosting at all but travels with it so reliably that it belongs here: the meter. Cloud-based desks are nearly always sold per agent per month, and the model shapes the desk in ways the first-year quote does not show. The part-timer who covers Fridays becomes a question. The manager who wants to look becomes a question. The bill compounds with headcount and time, and the rate is revised at renewal. The arithmetic is done, without currency, in the hosting and licensing article. The point here is only that a desk comparing "cloud-based" with "self-hosted" is usually also comparing "rented" with "owned" whether it meant to or not, and should know which of the two it is reacting to.

The Hybrid Nobody Mentions: Your Software on Rented Iron

The brochure presents a choice between the vendor's cloud and a server under somebody's desk, because those are the two pictures that sell. There is a third shape, and it is the one most small desks that self-host actually end up with: self-hosted software on a rented virtual machine. The server is in a hosting company's data centre, which you pay for monthly like any other utility, but the software, the database and the data are yours. The hosting company sees a virtual machine. It does not see tickets, and it has no opinion about your help desk's roadmap.

This shape answers the two objections that usually end the self-hosting conversation. "We have no server room" is answered by renting one, for a sum that is usually smaller than a single cloud-based agent seat. "Our technicians work from home" is answered by the fact that a rented server is on the internet already, reached through a browser with a certificate, exactly as the cloud-based desk would be. What it does not answer is the job. Somebody still patches the operating system, checks the backups, renews the certificate and plans each upgrade, and the hours belong in the worksheet with a name next to them. A help desk that runs as a single service on an ordinary Windows server keeps that job small. One that needs its own web server, runtime and database keeps it large, and the difference is a question for the trial rather than the brochure.

The hybrid also sharpens the data question in a useful way. Data on a rented server in your own country, in a database you can copy at will, under a hosting contract that concerns machines rather than tickets, satisfies most policies that "the vendor's cloud" does not, and it is worth asking whoever owns your data policy which of the three shapes they can live with before assuming the answer is the one under the desk. Many can live with the rented machine. Few can live with the vendor's platform. Almost all can live with the server in the building, and the server in the building is the shape with the most hours attached, so the hybrid is often the honest middle.

Who Should Choose Cloud-Based, Honestly

A desk should choose a cloud-based help desk when it has nobody to run a server, not nobody who could learn but nobody whose job it will be, with a name, next year as well as this one. It should choose cloud when its technicians are mostly outside the building and it has no remote-access arrangement and no wish to build one. It should choose cloud when the data in its tickets is of a kind nobody with a title minds being in a vendor's data centre, and that is true of more desks than the self-hosting side of this argument likes to admit. It should choose cloud when it needs voice, the widest channel list and integrations with a dozen other cloud tools, because that is where those are. It should choose cloud when the horizon is short or the headcount uncertain, since paying monthly and leaving by not renewing is worth something when you do not know what the desk will look like in two years. And it should choose cloud when it is a desk of two that will stay a desk of two, for whom the monthly bill for two seats is small, and whose administrator's evening is worth more than the server it would save.

The honest test is to write the five credits from the earlier section down the side of a page and tick the ones that describe your desk. Three or more ticks and cloud-based is the natural answer, unless the data question has already excused it. One or none and the credits are things you are paying for and would not have bought separately, which is how a director ends up on a cloud-based desk because an article said "modern" and nobody did the ticks.

Who Should Self-Host, Honestly

A desk should self-host when its rules, contracts or regulators say the data stays on equipment it controls, because then the choice has been made and the only remaining question is which self-hosted desk. It should self-host when the desk serves people inside a building that must keep working when the line to the outside does not, which describes factories, hospitals, schools and anywhere with a shop floor. It should self-host when the horizon is long and the team is growing, because that is where a one-time licence and a server beat a meter, and when it wants the manager, the warehouse lead and the Friday technician to have accounts without a monthly conversation about seats. It should self-host when it has been through a vendor retiring a product, moving a feature to a higher tier or redesigning a screen in a busy month, and has decided it would rather choose its own quiet week. And it should self-host when it has the person: a named administrator with a few hours a month and a backup routine that already covers forty other things, for whom one more Windows service is not a project.

The honest test here is the job. Write down who patches the server, who checks that last night's backup restored, who renews the certificate before it expires, and who plans the next upgrade. If every line has the same name and that person is leaving in the spring, the self-hosted desk has an owner for one more season. If some line has no name, it has no owner, and the cloud-based column is the honest one regardless of the data. The self-hosting side of this argument loses more desks to an un-named certificate than to any feature a cloud vendor ever shipped.

The Seven Claims on Every Cloud Brochure, Decoded

The same seven phrases appear on nearly every cloud-based help desk's front page, and each of them is true in a way that is smaller than it sounds. The table says what each one means for your desk and the question to ask before it goes in the decision record. None of the claims is false. All of them are written by someone who wants the second column to go unread.

Self-hosted brochures have their own three phrases, and fairness says they belong in the same light. "Your data stays with you" is true and is also a job with hours attached. "No subscription" usually means a licence bought once plus optional upgrade payments, plus the server, plus the hours. "Full control" means you decide, which means you must. A desk that decodes the cloud brochure and takes the self-hosted one at face value has not finished.

A Short War Story: The Afternoon the Line Went Down at Brennan Fabrication

Dev ran the fair trial the series recommends: two cloud-based desks and the self-hosted candidate, real tickets, two weeks, the whole team. On the Thursday of the second week a contractor cut the fibre to the industrial estate at 13:50. The machine shop's job scheduling, which ran on a server in the building, carried on. The office phones, which did not, went quiet. Within ten minutes eleven people wanted IT, because the thing they used to e-mail the vendor had stopped working too and they assumed it was Dev's fault. The two cloud-based desks were unreachable from inside the building. The self-hosted candidate, on a virtual machine in the server room, took eleven tickets by the portal and the form in the next half hour, and Dev worked them from the shop floor on a laptop. The line came back at 16:10. When it did, the two cloud desks showed nothing, because nobody had been able to reach them to say anything.

That is half the story, and Dev wrote the other half in the decision record the same evening, because he knew the director would hear only the first half. The self-hosted candidate had kept working because it was in the building; it had also been down for forty minutes the previous Monday, when Dev had restarted the host for a Windows update without checking what was on it. The cloud-based desks had never been down in the trial, and would have been reachable from home that Thursday if anyone had been at home. Brennan's data question had been settled on day one, in the self-hosted column, by a defence customer's contract nobody on the shortlist had read until Dev asked. What the Thursday had decided was not which was better. It was which failure Brennan could live with: the one in its own building that its own administrator could fix, or the one on somebody else's status page. The director, shown both halves, chose the first, and asked who would own the server. Dev said he would, and wrote it down, and put the certificate expiry in the calendar before he closed the laptop.

The Decision Sheet

The sheet below is the hosting half of the decision on one page. It is meant to be filled in before any feature is compared, because its first block is a filter and the rest are weights. Fill it in with whoever owns the data policy in the room, because the first block is theirs to answer and the rest are yours. A sheet that reaches the end with the data block blank has not been filled in.

CLOUD-BASED OR SELF-HOSTED — THE HOSTING DECISION SHEET
Desk: ______________________   Prepared by: ______________   Date: ____________
Data policy owner present: ______________

BLOCK 1 — THE FILTER (answer before anything else)
  Do rules, contracts or regulators say ticket data stays on equipment we control?  [ ] yes  [ ] no
  If yes: cloud-based candidates are out. Compare self-hosted candidates only, including rented-server shapes.
  If no: does anyone with a title object to ticket data in a vendor's data centre abroad?  [ ] yes  [ ] no

BLOCK 2 — THE CLOUD CREDITS (tick the ones that describe us)
  [ ] Nobody's job includes running a server, this year or next
  [ ] Technicians are mostly outside the building, with no remote access we want to build
  [ ] We need voice, many channels, or integrations with other cloud tools
  [ ] The horizon is short or the headcount uncertain
  [ ] We are a very small desk and will stay one
  Ticks: ___  (three or more leans cloud-based; one or none leans self-hosted)

BLOCK 3 — THE SELF-HOSTED CONDITIONS (name a person for each, or leave it blank honestly)
  Patches the server monthly:            ______________
  Checks backups and tests a restore:    ______________
  Renews the certificate before expiry:  ______________
  Plans and runs each upgrade:           ______________
  Blank lines: ___  (any blank line is an un-owned job; cloud-based is honest unless it is filled)

BLOCK 4 — THE CONNECTION
  When our internet line is down, must the desk keep working for people inside the building?  [ ] yes  [ ] no
  Hours the line was down in the last twelve months (ask the ISP):  ______

BLOCK 5 — THE EXIT
  Cloud candidate: export format ________  retained for ________ after we stop paying  clause no. ______
  Self-hosted candidate: database and files we hold ourselves?  [ ] yes  [ ] no

BLOCK 6 — THE SHAPE
  [ ] Vendor's cloud   [ ] Our software on a rented server   [ ] Our software in the building
  Reason, in one sentence: ____________________________________________________________

Horizon for the money comparison (from the total-cost worksheet): ____ years
Decision: ______________________   Owner of the hours lines, if self-hosted: ______________
Signed: ______________________

Dev's sheet for Brennan took twenty minutes and most of it was Block 1, which the defence contract answered. Block 3 had his name on every line and the spring on none of them. Block 4 was answered by the Thursday. Block 6 was the server room, because the building already had one, with a note that the rented-server shape was the fallback if it ever did not. The director's "surely" got a one-page answer on the Friday, and the one page was this sheet. The modern way, Dev said, was to know which failure you could live with, and to write down who owned the other one.

Frequently Asked Questions