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.
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: 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 β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.