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

Lean operations

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 β†’
Customer operations

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 β†’
Product studio

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

MIT Team Edition / open-core
Mattermost

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 β†—
AGPLv3 / open-core
Nextcloud

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 β†—
AGPLv3 / commercial editions
Metabase

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 β†—
AGPLv3 / open-core
Formbricks

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 β†—
AGPLv3
Twenty

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 β†—
GPLv3
ERPNext

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 β†—
AGPLv3 / open-core
Plane

Self-hostable projects, work items, cycles, pages, and integrations

Tradeoff: Check which governance and enterprise capabilities require a paid edition.

Project documentation β†—
MIT / open-core
Chatwoot

Self-hosted shared inbox, live chat, help center, API, and integrations

Tradeoff: Messaging channels, deliverability, upgrades, and uptime become operational responsibilities.

Project documentation β†—
MPL-2.0
Penpot

Web-based interface design and prototyping with self-hosting

Tradeoff: Validate design-system migration and collaborator workflows with a real project first.

Project documentation β†—
Open-source clients and server
Bitwarden

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 β†—
MIT core / open-core
Activepieces

Self-hostable workflow automation for common business integrations

Tradeoff: Verify the license and connector maturity for every workflow; enterprise features are separate.

Project documentation β†—
GPLv3
Mautic

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 β†—
MIT core
Medusa

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.