dctx maintenance
dctx is open source under the Apache-2.0 license and free for any use, including commercial use. A maintenance agreement is how organisations that depend on dctx pay for its upkeep. Paying never changes the license and never closes a feature.
What an agreement covers#
- Security fixes. Response targets are counted from the moment a report is confirmed:
- Critical: a fix or mitigation within 72 hours.
- High: a fix within 7 days.
- Medium: a fix in the next release.
- Long-term support. The 1.x line receives backported fixes for 18 months after 2.0 is released.
- Priority on bug reports. Reports from covered organisations are triaged first.
- A say in the roadmap. Covered organisations can propose priorities in a regular review. The maintainer keeps the final decision.
- Advance notice of breaking changes. You hear about a breaking change before it ships, with a migration note.
- Invoice and written commitment. You receive invoices and a signed maintenance commitment for procurement and vendor review.
Security reports still go through SECURITY.md, whatever your tier.
Tiers#
| Tier | Who it is for | What you get |
|---|---|---|
| Supporter | Individuals and teams who want to fund dctx | Sponsorship and your logo in the README. No service commitments. |
| Team | One organisation that depends on dctx | Everything under "What an agreement covers", for one organisation. |
| Partner | Organisations that build products on dctx | Team, plus integration help and a named contact. |
Supporter sponsorship runs through GitHub Sponsors. Team and Partner agreements are arranged directly.
Pricing and contact#
Pricing on request: info@tejl.com
Write to that address with your organisation, the tier you want and a contact name.
Guarantees#
- Paying never changes the license. dctx stays Apache-2.0 for everyone.
- Paying never closes or paywalls a feature. Every feature stays in the open source project.
- The core (
pack) and every modality stay open.