Are you using or leaning toward using a self-hosted ticketing system?
While many of our clients choose to use our hosted, SaaS version of our ticketing system, we also offer self-hosted for those that prefer it. Choosing this option means that you take more responsibility and control over managing it.
If you’re using a self-hosted ticketing system, we’ve got a few tips here for managing it well:
Free download: Tips for managing your knowledge base
Companies have various reasons for opting for self-hosted over hosted versions of software, and they’re worth considering if you’re wavering between the two. Self-hosted software may be chosen for reasons such as:
The choice generally comes down to level of control, which is why it’s important to follow a few best practices to manage your self-hosted system. There are things that you have to take care of that would otherwise be taken care of by the host company with a hosted version.
Here are a few tips from us for managing your self-hosted ticketing software:
When you choose a hosted software, the host is responsible for backups of data and ensuring that you’ll be able to retrieve data if anything goes wrong. When you choose to self-host, backups become your responsibility.
We suggest that you back up everything regularly. It often pays to be paranoid about backups because anything could happen at any time to lead to loss of data. There are multiple potential causes of data loss: human error, deliberate data deletion by a disgruntled employee, malware hijacking your system or even a hard drive crash. You need to be prepared in any case.
At a minimum, you probably want to be backing up daily to ensure minimal loss of data should an event occur. You might choose to back-up on media that you own, in which case it is suggested that back-ups are stored off-site (if your building caught fire, you can potentially lose back-ups and current data).
Another method many organizations use is to back-up via the cloud. There are services specifically for cloud-based data back-up, or you can create your own using something like AWS. The key is to ensure that stored data is encrypted and that the right people have administrative access. There was an incident illustrating the importance of this, where a former American College of Education employee changed their Google account password and held them to ransom for it, holding up stored email and course materials for 2000 students.
This is related to the previous point - you should follow all security best practices, especially if you want to stay compliant with GDPR, HIPAA and any other requirements. For example, you may need:
Self-hosting software may require you to manage compliance with GDPR and HIPAA
If the organization is Windows-based, Windows-integrated authentication allows users and and employees to log into the system without entering any passwords whatsoever. The system logs them in using their “domain account.”
This is recommended for intranet (rather than internet) environments as it does not send the user credentials in the request. Microsoft lists the following reasons to recommend an intranet environment:
(JitBit allows for Windows-integrated authentication for both SaaS and self-hosted environments)
You’re probably choosing to self-host because you have the expertise to do so, but that doesn’t mean you won’t ever require help with your chosen software.
Your choice of vendor is important here - some will offer minimal support if you self-host, whereas others (like JitBit) offer guided emergency support, using “TeamViewer” or similar screen-sharing tools.
We suggest you choose a vendor who you can rely on for support if and when needed.
When software updates come out, it’s very important to keep up with them as a matter of routine. Of course in a self-hosted environment, you must enact the updates yourself.
Updates consist of new features, bug fixes, security updates and industry trends. In fact, it’s possible that missing an update could take you out of compliance with certain security protocols if that update is related to those requirements.
There are many self-hosted open source software solutions, with associated pros and cons. To help mitigate possible risks, we suggest looking for the following:
If you’ve chosen a good software vendor, they should hopefully have a decent knowledge base prepared for the software. When you self-host, there may be things that you need to add about your company policies and procedures.
Keep your knowledge base updated so that any of your team is able to complete tasks when required.
A good ticketing system should also have a knowledge base that is easy for customers to use. This can help to cut back on tickets, especially if they can easily find the answer they need.
Download our tips for managing your knowledge base here
There are many benefits to going with a hosted software rather than self-hosting. For example:
That’s our final thought on this. While we totally understand that some companies will prefer to self-host, perhaps due to organizational security policy, we’re huge fans of SaaS. If you’re able to choose hosted software, you’re potentially saving a lot of time and avoiding the risk that vital security updates or other important tasks get missed by your department.
If you still need to choose self-hosted? Be sure to follow these tips. It’s a lot of responsibility to ensure that it is well-managed.