By the Onsites AI team · Last updated · 5-minute read
Self-hosting open-source support software is genuinely free and genuinely yours: no license line, no vendor counting your seats, source code you can fork if the relationship ever sours. For a tinkerer, a two-person startup, or a company whose IT staff wants a project, Chatwoot-style OSS is a fine choice and this guide will not pretend otherwise. This guide is for the other desk: the five-to-fifty-person team whose support tool must be running — updates applied, backups proven, upgrades rehearsed — by people whose real job is answering customers. The comparison is OSS freedom against a licensed self-hosted product (Onsites: $15/seat/mo billed annually, 10-seat minimum, 60-day trial, updates included) where maintenance is the vendor's included job and the buyer keeps the part that matters: your Docker host, your data, your compliance story, no Onsites access at all.
The OSS ledger is denominated in engineer-hours, and honesty requires pricing them. Setup: install, configure the reverse proxy, wire TLS and email — half a day to a day for a practiced hand. Updates: the recurring line — review release notes for breaking changes, stage, migrate, verify: an hour on quiet releases, an afternoon on rough ones, monthly-ish on an active project. Backups: configure, schedule, and — the part everyone skips — restore drills that prove the backup works; another recurring hour. Incidents: the 2 a.m. the disk fills or the upgrade wedges mid-migration; the on-call is yours. An honest self-hosting shop prices the steady state at a few engineering hours a month and the tail risk as "someone senior drops everything." That is the real meter: quiet most months, expensive exactly when support is busiest. None of it is a reason to avoid OSS; it is the price of owning the wrench.
The mirrored ledger on the licensed side reads shorter because the lines moved. Updates included: the vendor ships them and stands behind them; your part is running the provided upgrade path (the updates guide documents the ritual) — hours, occasionally, not afternoons of archaeology. Support included: when the desk misbehaves, there is a vendor whose product it is — the OSS equivalent is "someone on your team reads the source," which is a different staffing plan. Artifacts included: the compose file, the backup/restore scripts, the upgrade runbooks are the product's deliverables rather than community wiki pages. The license itself: $15 per seat monthly billed annually with a 10-seat minimum, licenses final-sale, and a 60-day trial that requires no payment up front — the meter is published and flat, and the seat bill is the whole bill. What stays yours reads the same in both columns: your servers, your storage, your data, and nobody else's hands inside the box.
Beyond the recurring hours, three variables swing the OSS ledger more than any feature list. Community velocity vs your stability: an active OSS project ships often, which is joy for contributors and churn for operators — every upgrade decision needs release-note archaeology, and skipping upgrades for a year makes the eventual catch-up an afternoon into a week. The integration perimeter: the OSS desk is one product in a stack you assemble — email infra, storage, dashboards — and each piece carries its own update line; the maintenance hours in the worked example understate the full perimeter by assuming the surrounding stack already existed. Knowledge concentration: in most OSS self-hosts, exactly one person truly knows the box; they accept the 2 a.m. calls, they take vacations, and they eventually take jobs — and the desk's operational knowledge walks out with them. Document it, rotate it, or price it. None of these argues against OSS self-hosting; they are the variables that separate the shops where it works from the ones quietly rebuilding their desk on a weekend in March. The licensed path prices these lines in: velocity managed by the vendor, perimeter documented by runbooks, knowledge backed by support.
Feature comparisons between OSS and licensed desks usually mislead by comparing screenshots. Ask instead where scope and depth compound. Channels: both cover the major ones (email, chat, messaging); verify the markets that matter — WeChat and LINE native vs plugin. The CRM: OSS desks typically stop at contact records; a desk with accounts, pipeline and conversation-linking built in removes the second system. The commercial loop: quotes, orders, invoices, contracts from the thread — OSS never has this (it is a support product, not a commercial one); the licensed desk makes it native, which is the difference between answering "where is my invoice" and actually having one in the thread. AI: OSS integrates what you bring; the licensed desk ships drafts, replies, translations, summaries by prepaid credits — or, self-hosted, bring your own model entirely. Both stacks can reach most places; the licensed path bundles the compounding parts.
Put numbers on the decade decision because hand-waving is how desks choose badly. A 15-seat support org, five years. OSS path: $0 licensing; setup ~10 engineering hours; steady state ~3 hours monthly (updates, backup checks, drift) = 180 hours; two rough incidents a year at 4 hours = 40 hours; total ~230 engineer-hours — at even a modest internal rate, a five-figure sum. Licensed path: 15 seats × $15 = $225/mo billed annually = $13,500 over five years, maintenance included, support included, updates included; your IT touches the box a few hours a year. The comparison is not a slam dunk in either direction — a team that wants the wrench and has the hands gets valuable software for free, and fork rights are worth something. It is a staffing question wearing a pricing question's clothes: who owns the 230 hours, and do they exist? The Docker guide shows what the licensed box's operations actually look like.
Giving OSS its fair column in full: tiny budgets where the license line is the line; teams with genuine engineering appetite who want to own, fork and modify; shops whose IT staff treats the maintenance as professional development; and situations where even a licensed vendor's binaries are one step too closed. The licensed self-hosted path wins when the desk's operator count makes the seat math sane, when support uptime outranks tinkering, and when the buyer wants the compliance story ("no Onsites access to our data, we run the backups, we hold the keys") without buying the maintenance job too. Both are honest self-hosting; they differ on who holds the wrench. Price the hours, count the seats, and the answer usually falls out in an afternoon.
Is self-hosting open source support software really free?
The license is $0. The costs are your engineering hours: setup, update review and application, backup drills and incident response — a few hours monthly for a steady-state desk, more on rough releases. Great for teams that want the wrench.
What does a licensed self-hosted desk include?
Onsites self-hosted: $15 per seat per month billed annually (10-seat minimum), updates included with no maintenance fee, support included, 60-day trial with no payment up front, Docker compose plus backup/restore scripts included, BYO AI model and storage, and no Onsites access to your instance.
How do the five-year costs compare for a 15-seat team?
OSS: ~230 engineer-hours over five years (setup, updates, backups, incidents) at $0 license. Licensed: $13,500 total ($225/mo), with maintenance and support included. The right answer depends on whether your engineers want the project or the product.
Can we keep our data fully on our own infrastructure with Onsites self-hosted?
Yes: you run the Docker host, own the storage, hold the keys, and Onsites has no access — the compliance story ("our servers, our data") is the point of the purchase.
When does OSS win over the licensed desk?
Tiny budgets, engineering-hungry teams that will genuinely own the maintenance, and buyers who need fork rights. The licensed path wins for desks that need uptime and vendor support more than they need a project.