Skip to content

Latest commit

 

History

History
70 lines (52 loc) · 2.89 KB

File metadata and controls

70 lines (52 loc) · 2.89 KB

Commercial Licensing

Webhookery is publicly available under the GNU Affero General Public License version 3.0 (AGPL-3.0-only). The public license is suitable for users who can comply with AGPL obligations, including source-availability obligations for modified network-service deployments.

Commercial license exceptions are available for organizations that want to use Webhookery in proprietary products, private SaaS systems, closed internal deployments, or other contexts where AGPL obligations are not suitable.

This is not legal advice. Have counsel review AGPL and any commercial agreement before relying on it.

Paid Options

Offer Customer hosts? Webhookery hosts? Notes
Commercial license exception Yes No Written permission for agreed proprietary use cases.
Self-hosted support Yes No Deployment review, upgrade help, troubleshooting, and security notices.
Release evidence package Yes No SBOMs, vulnerability scan results, OpenAPI checksum, acceptance evidence, and hardening notes.
Custom integration work Yes No Provider adapters, evidence workflows, deployment hardening, or receiver integration work.

Starting Ranges

These ranges are public planning anchors, not a quote. Final pricing depends on scope, deployment risk, provider mix, support expectations, and written agreement.

Offer Starting range
Commercial Evaluation EUR 490-1,000
Release Evidence Package EUR 2,500-5,000
Production Readiness Review EUR 7,500-12,500
Commercial License + Support EUR 9,900-24,900 per year
Custom Integration / Provider Adapter Fixed scope or EUR 150-250/hour

See docs/commercial-evaluation.md, docs/production-readiness-review.md, and docs/support-packages.md for buyer-readable scope boundaries.

Commercial License Scope

A commercial license is a separate written agreement. It does not remove or reduce the rights granted to the public under AGPL. It can grant extra permission for a named organization, product, deployment, or distribution model where AGPL terms are not a fit.

Commercial terms can cover:

  • proprietary embedding or distribution,
  • closed-source network-service operation,
  • private modifications without AGPL redistribution obligations,
  • support and upgrade commitments,
  • signed release and evidence delivery,
  • self-hosted deployment review,
  • operational runbook review.

Commercial terms do not broaden the canonical non-claims in docs/security-promise.md unless the written agreement explicitly narrows scope for that customer, deployment, or engagement.

No SLA, compliance certification, legal evidence certification, hosted service, or provider-side completeness guarantee is included unless a written agreement explicitly says so.

Contact

For commercial licensing or paid support, contact Aatu Harju through LinkedIn:

https://www.linkedin.com/in/aatu-harju