What does a free self-hosted help desk really cost?
Budget the servers, mail setup, maintenance and recovery work behind an open-source help desk, then compare a managed hosting quote.
Start with the service you must keep running
A support system receives requests, stores their history and helps people respond. A free software download covers only part of that service. Before choosing self-hosting, write down the channels you need, the expected ticket volume, the attachment sizes and the hours when support must work. A team with an existing operations owner faces a different purchase decision from a team that has nobody responsible for servers. Compare the complete service in both cases.
Assign ownership before installation
Name the person responsible for installation, mail configuration, monitoring, updates and recovery. Give a second person enough access and documentation to take over. Allocate time for routine work and exceptions. Record where credentials are managed and how they are replaced when someone leaves. If this responsibility would fall to an external provider, request a written scope and response arrangements. A server invoice does not tell you who fixes an application failure.
Separate recurring costs from setup work
Use distinct lines for infrastructure, backups, mail delivery, monitoring, support and administration time. Put installation, migration, training and initial configuration in a setup section. Existing infrastructure can reduce an incremental cash invoice, but it does not eliminate the work required to run another service. Use the hours your team actually expects to spend rather than treating maintenance as free. Keep billing currency, tax treatment, term and renewal details with every quote.
Make a normal month and a busy-month estimate
Model ordinary ticket intake and a period with a product launch or seasonal surge. Increase attachments and retained history as well as ticket count. Identify which costs vary with storage, traffic, agents or outside services. For labour, include a routine month and a month with an update or failed mail connection. The result should explain what changes the bill and who responds; a single cheapest-month total can hide the workload you will actually face.
Test mail and recovery together
In a controlled evaluation, create a synthetic ticket with a small attachment. Reassign it, reply and reopen it. Check the reply-from address, threading and the handling of an automated response. Restore the sample ticket and attachment from a backup into an appropriate test environment. Confirm that incoming mail and outgoing replies still work after recovery. Record the actual elapsed work and any missing information in the runbook before relying on the service for real enquiries.
Compare equivalent managed hosting
Ask a managed provider for the same channels, agents, storage, attachment sizes, support hours and migration scope. Identify the features in the retained paid package rather than the temporary trial. A hosted agent cap does not establish a limit on the self-hosted software. Conversely, a self-hosted capability does not mean it is bundled into every hosted tier. Compare the responsibilities transferred to the provider alongside recurring fees and remaining work for your own team.
Make the operating decision reviewable
Document the chosen approach, its named owner, expected setup work and normal and busy-month costs. Set an acceptance checklist for intake, escalation, customer replies, permissions, exports and recovery. After rollout, record real administration hours, failed mail events and recovery incidents. Review those measurements at renewal. The strongest case for self-hosting is a workflow and operating model your team can sustain; the strongest case for managed hosting is a useful transfer of work and responsibility at an acceptable cost.
Put the guide into practice
Explore help desk tools, then compare your shortlist.
Explore the category →