Proposal: No paywall for self‑hosted core; paywall only for DocuSeal‑hosted services

Thanks for DocuSeal. Today, essential features are paywalled even when self‑hosting and using our own infrastructure (per the pricing page: Teams/Tenants and Roles, API/Webhooks, company email address, and basic branding). This makes the free self‑hosted version impractical and undermines the autonomy expected from an open‑source deployment.

Proposal: if we run DocuSeal on our own servers and services (DB/storage/SMTP/queues), all core features needed for a complete multi‑user workflow should be unlocked with no per‑user fee. Paid tiers should focus on DocuSeal‑hosted value—managed cloud, email delivery through DocuSeal’s infra, compute/storage, SLA support, SSO/advanced auditing, higher limits, and specialized verifications. We are not asking to make the hosted service free; only that the OSS self‑hosted core not be restricted.

Impact and next steps: this change would broaden global adoption and contributions while keeping a clear business path for hosted offerings. Could maintainers confirm which “core” features still depend on DocuSeal infrastructure and outline a path to decouple them for self‑hosted? Happy to help define core vs. enterprise and test a self‑hosted profile. Community: please +1 and share your use cases.