Clear, Simple Licensing for Every Use Case

Open source at the core, commercial options for enterprise. Choose the license that fits your project.

License overview

Open Source

AGPL-3.0-only

Free
  • Protocol spec, soft-binding algorithms, and verification tooling
  • Community support via GitHub
  • Patent grant included
  • Must share modifications under AGPL
  • Network use triggers source disclosure

Ideal for

  • Personal projects
  • Academic research
  • Open-source tools
Browse the repositories

Commercial License

For proprietary use

Custom
  • No copyleft obligations
  • Priority support with SLA
  • Patent grant included
  • Custom integration assistance
  • Private modifications allowed

Ideal for

  • SaaS products
  • Proprietary software
  • Enterprise deployment
Contact Sales

WritersLogic SaaS

Just subscribe

From $0/mo
  • No SDK licensing needed
  • All features included
  • Managed infrastructure
  • Automatic updates
  • Standard support included

Ideal for

  • Writers & authors
  • Students
  • Content creators
Try Free

What's Covered

Each component of the WritersProof ecosystem falls under a specific licensing model.

ComponentAGPL-3.0CommercialSaaS
cpop_engineYesYesIncluded
cpop_protocolYesYesIncluded
cpop_jitterYesYesIncluded
cpop_cliYesYesN/A
Desktop AppsN/AProprietaryN/A
Web AppN/AN/ASubscription
REST APIN/ACustomIncluded

Frequently Asked Questions

Common questions about licensing the WritersProof ecosystem.

If you are building a proprietary product that incorporates cpop_engine or cpop_protocol, yes. If your project is open source under a compatible license, or strictly personal or academic, the AGPL-3.0 license covers you at no cost.

Running cpop_cli as a standalone tool is fine under the AGPL. Embedding it within a proprietary product or distributing a modified version in a closed-source context requires a commercial license.

A pending patent application covers the WritersProof protocol. Both AGPL and commercial licensees receive a patent grant, so you are free to implement the protocol under either license without patent concerns.

We offer startup-friendly terms on a case-by-case basis. Reach out to [email protected] with your use case and team size, and we will work with you.

If you deploy cpop_engine as part of a network service (e.g., a SaaS product or API) that users interact with over a network, the AGPL requires you to make the complete corresponding source code available to those users. This is the key difference from the standard GPL.

Contact sales

Need a Commercial License?

Email us with your use case and we will respond within 24 hours. Include your company name, intended use, and any integration requirements.

[email protected]

Or schedule a call — we are happy to walk through your integration needs.