You have no dedicated system operator.
Your top requirements are adoption speed, predictable support responsibility, built-in integrations and minimal operational work. Validate data-export options and subscription tier limits before committing.
Independent software buyer research · October 12, 2026
Choose managed SaaS when you need dependable operations without owning an infrastructure team. Choose self-hosting when control is a documented requirement and someone is accountable for security, upgrades and recovery. The license price alone should never decide.
Decision boundary
The answer changes with your recovery obligations and skills—not just the team size.
Your top requirements are adoption speed, predictable support responsibility, built-in integrations and minimal operational work. Validate data-export options and subscription tier limits before committing.
You need specific hosting, deployment or code-level controls; you can budget for operations, security and recovery; and you accept that the team—not the vendor—owns deployment failures.
“We need data ownership” does not automatically imply “we must self-host.” Separate exportability, contractual rights, encryption, data residency, deployment control and actual ability to recover data. They are different procurement questions.
Four dimensions
SaaS: Provider operates its managed service; your team still owns configuration, user access and adoption.
Self-hosted: Your organization owns the deployment, patching, monitoring, restore process and incident response.
Ask: Who will respond if the CRM is unavailable at 09:00 on Monday?
SaaS: Review where the vendor processes data, export rights, contract terms and applicable service commitments.
Self-hosted: You can choose infrastructure location, but must secure databases, backups, logs and credentials yourself.
Ask: What written evidence do you need for location, retention and deletion?
SaaS: Managed integrations may accelerate adoption but can introduce tier limits and vendor-specific workflows.
Self-hosted: Code-level changes may be possible, while every customization adds upgrade and maintenance responsibilities.
Ask: Which integrations must survive a CRM version upgrade?
SaaS: Seat, feature-tier and usage charges can grow; confirm exactly which features and users are in your plan.
Self-hosted: Software licenses may be free while hosting, monitoring, recovery, administration and commercial add-ons are not.
Ask: What is the fully loaded 12-month cost, including internal hours?
Worked example
Twenty publishes self-hosting instructions and cloud plans. Its canonical GitHub LICENSE describes a repository with predominantly AGPLv3 code, some MIT components and commercially licensed enterprise-marked files. The free self-hosted edition is not a promise that every enterprise feature is free.
Its official Docker Compose configuration includes application infrastructure beyond a single web page: a PostgreSQL database, Redis and persistent storage. Budget the work to operate that stack.
Open the Twenty research profile →HubSpot offers free and paid CRM editions. Its official pricing page currently limits its free tools to two users, so a 10-person sales team must budget a relevant paid tier rather than treating the entire deployment as free.
Compare the specific HubSpot subscription that delivers your required controls, integrations, permissions and records—not a generic description of “HubSpot.”
Open the HubSpot CRM profile →Scope note: This is a documented comparison of deployment models and vendor claims, not a hands-on performance/security benchmark of either product. Product features, licensing and prices can change.
Original tool
The worksheet deliberately counts internal maintenance hours, one-time work and commercial add-ons.
Use your own assumptions. The defaults are illustrative, not market prices or a quote for Twenty, HubSpot, or any vendor.
Model: SaaS = 12 × (seats × monthly seat price + monthly add-ons) + migration; self-hosted = 12 × (monthly infrastructure + maintenance hours × hourly cost) + setup + paid licenses.
Not included: taxes, downtime, regulatory review, non-linear growth, staff turnover, switching costs after month 12, special enterprise contracts or feature equivalence. The less-expensive column is not automatically the better choice.
Readiness checklist
Someone can maintain backups, access controls, security patches and upgrades every month.
You can restore a recent copy and know the recovery time and data-loss window.
You know whether hosting geography, deletion controls or contractual obligations actually require self-hosting.
Email, calendar, identity, file storage and automation dependencies are written down before migration.
You checked the exact community, hosted and commercial-feature terms that apply to your target version.
You can export contacts, companies, deals, activities, files and relevant custom fields if you change systems.
Research sources
The factual product claims above are based on the following official vendor materials and repository documentation, reviewed October 12, 2026. The decision matrix and TCO worksheet are Belobrov Technologies analysis, not vendor endorsements. No hands-on deployment, paid subscription or security penetration test was conducted for this guide.
Deployment architecture and operational setup. Review version-specific instructions.
Primary evidence for AGPLv3, MIT components, enterprise-marked commercial files and application exception.
Primary-source evidence that self-hosting involves a database, Redis and persistent storage.
Vendor-stated Free, Starter and paid editions; terms and price tiers may change.
Vendor-stated seat and object limits; check limits at procurement time.
Need a scoped choice?
We can structure a procurement comparison, check contested licensing/hosting facts, and show where key evidence is missing.