Own more of the stack
Open-source software packages, with the operating cost included in the decision.
Self-hosting can reduce lock-in, but it trades subscription convenience for upgrades, security, backups, monitoring, and support. We show both sides and connect you with implementation help.
Decision kit
The zero-dollar license is not the zero-dollar option. Compare subscription, infrastructure, migration, and operator labor with an editable worksheet.
Open the cost model →Pullable kit
Compare Pipedrive, HubSpot, Salesforce, and the Twenty open-source path with editable labor assumptions and a reconstruction test.
Run the free CRM kit ↗Pullable kit
Compare Zapier, Activepieces, n8n, or another platform by billing unit, failure recovery, license, and clean-instance reconstruction.
Run the automation kit ↗Migration kit
Plan destination access, a one-time pilot, plaintext-export controls, reconciliation, cleanup, and rollback without placing secrets in the kit.
Migration kit
Compare Outline's source-available BSL with AppFlowy's AGPLv3 main repository, then test export scope, import fidelity, hosting, and rollback.
Migration kit
Separate individual and organization export authority, test native-file conversion and access reconstruction, and prove destination backup and restore.
Starter packages
Small teams replacing several per-seat subscriptions
- ERPNext
- Mattermost
- Nextcloud
- Plane
- Bitwarden
Recommended for identity, backups, migrations, email, and upgrade automation
Request an implementation match →Teams owning the customer-data and support path
- Twenty
- Chatwoot
- Mautic
- Activepieces
Recommended for data modeling, deliverability, workflow failure handling, and migration
Request an implementation match →Design and engineering teams that want portable working data
- Penpot
- Plane
- Mattermost
- Bitwarden
Useful for SSO, observability, backups, and managed hosting
Request an implementation match →Options by job
Self-hosted team chat with channels, direct messages, files, calls, and integrations
Tradeoff: Confirm the exact edition and license; group calls, enterprise controls, uptime, search, mobile delivery, and upgrades need explicit validation and operations.
Project documentation ↗Self-hosted files, sync, calendar, contacts, office integrations, and team collaboration
Tradeoff: Storage sizing, office integration, backups, upgrades, antivirus, and external sharing policies require ongoing administration.
Project documentation ↗Self-hosted dashboards and business questions over existing databases
Tradeoff: Analytics quality still depends on modeled data, permissions, query performance, and reliable warehouse operations.
Project documentation ↗Self-hosted forms, surveys, in-product feedback, and response analysis
Tradeoff: Validate edition boundaries, spam controls, consent language, email, and data retention before collecting customer responses.
Project documentation ↗Customizable CRM with self-hosting, APIs, workflows, and data export
Tradeoff: You own upgrades, backups, email/calendar integration, and security when self-hosting.
Project documentation ↗Accounting plus CRM, HR, inventory, manufacturing, and order management
Tradeoff: A broad ERP has materially more setup and process-change work than a small accounting app.
Project documentation ↗Self-hostable projects, work items, cycles, pages, and integrations
Tradeoff: Check which governance and enterprise capabilities require a paid edition.
Project documentation ↗Self-hosted shared inbox, live chat, help center, API, and integrations
Tradeoff: Messaging channels, deliverability, upgrades, and uptime become operational responsibilities.
Project documentation ↗Web-based interface design and prototyping with self-hosting
Tradeoff: Validate design-system migration and collaborator workflows with a real project first.
Project documentation ↗Password management with hosted and self-hosted deployment options
Tradeoff: Self-hosting a security-critical service requires disciplined patching, backups, monitoring, and recovery tests.
Project documentation ↗Self-hostable workflow automation for common business integrations
Tradeoff: Verify the license and connector maturity for every workflow; enterprise features are separate.
Project documentation ↗Self-hosted marketing automation, campaigns, segments, forms, and email workflows
Tradeoff: Email deliverability, sender reputation, consent, upgrades, and queue operation remain your responsibility.
Project documentation ↗Composable commerce backend for custom storefronts, products, carts, orders, and integrations
Tradeoff: It is a developer platform, not a turnkey hosted store; storefront, hosting, payments, tax, operations, and upgrades need owners.
Project documentation ↗Self-hostable payment orchestration across multiple processors with routing, retries, vault, reconciliation, and checkout components
Tradeoff: It does not remove processor fees, merchant accounts, PCI scope, compliance, fraud, reconciliation, or production operations; verify each connector and payment flow.
Project documentation ↗Managed, self-hosted, or hybrid?
Choose self-hosting for a concrete control, compliance, customization, or lock-in requirement—not because the license price is zero. A hybrid stack is often the lower-risk answer.