> For the complete documentation index, see [llms.txt](https://builderstack.gitbook.io/builderstack-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://builderstack.gitbook.io/builderstack-docs/self-hosted-open-core-license-traps-ram-baselines-and-saas-crossover-math-2026.md).

# Self-Hosted Open-Core License Traps, RAM Baselines & SaaS Crossover Math (2026)

Primary-source license audit, container RAM baselines, and SaaS seat crossover math for self-hosted engineering teams.

Evaluating open-source alternatives to commercial SaaS strictly by GitHub stars or base license badges leads engineering teams into unexpected paywalls and infrastructure overhead. Many modern open-source repositories split permissive or copyleft cores from proprietary enterprise directories (`ee/`), Sustainable Use License (SUL) clauses, or restricted companion builds.

For side-by-side TCO modeling, primary license excerpts, and deployment sizing across 25+ self-hosted tools, refer to the [BuilderStack Side-by-Side OSS vs SaaS Comparisons](https://dceniac.com/oss/vs/).

### 1. Open-Core vs Permissive License Boundaries (ee/, SUL & cal.diy)

Three architectural licensing patterns consistently separate free single-developer setups from production team rollouts:

* **ee/ Enterprise Directories:** Projects with an MIT or AGPL core frequently isolate SAML/OIDC SSO, SCIM provisioning, audit logs, and granular RBAC inside a commercial `ee/` directory governed by a paid license key.
* **Sustainable Use License (SUL):** Allows internal self-hosting and source inspection while blocking hosted multi-tenant SaaS monetization and reserving team collaboration features for paid tiers.
* **Public Companion Forks (cal.com vs cal.diy):** When upstream enterprise code moves closed-source, companion repositories often impose single-user or strict AGPLv3 boundaries that block drop-in multi-seat commercial team deployments.

### 2. Workflow Automation TCO: Full-Execution vs Per-Step Pricing (n8n vs Activepieces)

Workflow automation bills diverge sharply once multi-step orchestrations run on high-frequency webhooks or cron schedules:

* **n8n Cloud vs Community Self-Hosted:** n8n Cloud bills per full workflow execution rather than individual steps, keeping complex 15-node flows predictable. However, the free Community self-hosted edition omits shared projects, SSO, and Git-backed environments—pushing self-hosted Business licensing to a €667/mo (\~$720/mo) floor at 40k executions or Enterprise contracts.
* **Activepieces MIT Core:** Activepieces ships an MIT core (with enterprise governance gated in `ee/`), while managed Cloud tiers bill per task/step. High-step orchestrations often favor self-hosting on a modest VPS, whereas smaller teams hitting n8n shared-project limits frequently see lower TCO on Activepieces paid tiers.

Model your exact monthly execution volume, average step count, and shared team seats using the [n8n vs Activepieces TCO & License Calculator](https://dceniac.com/oss/vs/n8n-vs-activepieces/).

### 3. Scheduling & Investor Data Rooms (Cal.com vs Calendly & Papermark vs DocSend)

External-facing scheduling and fundraising portals expose two distinct cost traps:

* **Cal.com vs Calendly:** Closed-source upstream Cal.com licensing and cal.diy AGPLv3 single-user boundaries create a sharp SAML SSO / SCIM crossover point around 44 seats when benchmarked against Calendly Teams and Enterprise plans. Compare exact seat tiers using the [Cal.com vs Calendly Seat & SSO Crossover](https://dceniac.com/oss/vs/cal-vs-calendly/).
* **Papermark vs DocSend:** Papermark ships its core under `AGPL-3.0` while gating Data Rooms and enterprise controls inside proprietary `ee/` modules. Self-hosting Papermark requires running Next.js alongside PostgreSQL, S3-compatible Blob storage, and a Tinybird analytics pipeline, while SaaS buyers weigh DocSend per-seat pricing against Papermark bundled 3-seat tiers. Review the [Papermark vs DocSend Data Room & Self-Host Breakdown](https://dceniac.com/oss/vs/papermark-vs-docsend/).

### 4. Infrastructure RAM Baselines & Egress Math (Twenty CRM & LiveKit)

Beyond licensing, under-provisioned containers and unbudgeted network egress derail self-hosted rollouts:

* **Twenty CRM:** Running Twenty via Docker Compose requires provisioning concurrent memory for the main server, background worker queues, PostgreSQL, and Redis, while accounting for `AGPL-3.0` derivative obligations and the $19/user/mo Enterprise key required for row-level permissions and SAML SSO. Review container sizing in the [Twenty CRM Self-Hosting RAM & License Audit](https://dceniac.com/oss/twenty/).
* **LiveKit:** Licensed cleanly under `Apache-2.0`, LiveKit WebRTC SFU eliminates open-core licensing traps and shifts build-vs-buy math purely to host CPU cores, memory headroom, and outbound video bandwidth egress rates. Estimate self-hosted node capacity with the [LiveKit Self-Hosted Bandwidth & Cloud Calculator](https://dceniac.com/oss/livekit/#calculator).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://builderstack.gitbook.io/builderstack-docs/self-hosted-open-core-license-traps-ram-baselines-and-saas-crossover-math-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
