Sponsor AcmeMux
AcmeMux does not need to pretend every supporter is buying coffee. General support sustains maintenance. Roadmap sponsorship funds a specific, accepted outcome under written scope and delivery terms.
General support
Support security maintenance, issue triage, documentation, infrastructure, and release engineering. General support is appreciated but does not change feature priority.
Invoice-based support is available now. A public self-service funding account will be added when it is operational.
Roadmap priority
For an already accepted proposal, a contribution of at least $500 guarantees placement in the sponsor-funded queue ahead of voted and maintainer-selected features.
It does not guarantee that $500 covers implementation, or promise a release date by itself. Scope, remaining funding, milestones, acceptance criteria, and delivery terms are agreed in writing before payment.
Scoped implementation
Organizations can fund a complete accepted feature, provider integration, packaging milestone, or documentation project. The agreement defines the deliverable, timeline, review process, and public attribution.
Contact is direct and invoice-based; there is no public checkout or recurring billing yet.
Sponsor protections
The maintainer confirms architectural fit and legal, security, and operational feasibility before accepting funding.
Funded work must pass the same tests, review, documentation, licensing, and release requirements as every other change.
Unless separately agreed for sensitive disclosure work, sponsored features remain part of the open-source project.
A payment cannot dictate an unsafe design or override maintainer judgment about implementation quality.
Priority applies only after the proposal and terms are accepted in writing. Unsolicited payment creates no delivery obligation.
Accepted sponsored work is identified on the roadmap unless confidentiality is required during coordinated security work.
Why support it
AcmeMux puts a constrained operational surface around lego without reimplementing ACME or creating a second private-key store. Maintaining that boundary requires ongoing review as certificate authorities, DNS APIs, operating systems, and upstream lego behavior change.
Funding helps keep the project secure and useful without advertising, telemetry, or a hosted demo that can consume public cloud resources.