WebCodex is an open-source project. Financial sponsorship can help, but long-term project support also includes build and test infrastructure, code-signing services, cloud credits, hardware, documentation, and engineering collaboration.
The goal is to make support visible and useful without turning the product or documentation into an advertising surface.
Individuals and teams may support ongoing maintenance, releases, documentation, and issue triage through project funding channels when those channels are available.
Funding does not purchase roadmap priority, security exceptions, private authority, or influence over review and release decisions.
Infrastructure support can be especially valuable for WebCodex because the project validates behavior across Windows, macOS, Linux, multiple architectures, hosted CI, and self-hosted deployments.
Useful support may include:
- CI or build capacity;
- macOS, Windows, Linux, x64, and arm64 test resources;
- code-signing or release infrastructure;
- cloud compute, storage, bandwidth, or test environments;
- hardware for platform-specific validation.
When infrastructure is provided by a third party, WebCodex may acknowledge that support in project documentation or on the project website.
Organizations may propose engineering or ecosystem collaboration around integrations, deployment environments, interoperability, testing, documentation, or other work that is useful to the wider project.
A partnership does not imply endorsement, exclusivity, privileged product authority, or a commitment to merge a particular change. Normal security, review, compatibility, and release requirements still apply.
Sponsor and partner recognition should remain proportionate to the support provided and should not interfere with normal use of WebCodex.
WebCodex intends to keep the following defaults:
- no intrusive sponsor popups in the runtime or Desktop application;
- no third-party tracking added merely for sponsor attribution;
- no payment QR codes or similar direct-payment graphics in primary product surfaces;
- no sponsor-controlled technical claims, security policy, or release decisions;
- clear separation between acknowledgement and product endorsement.
Appropriate recognition may include a Sponsors section in the README, a project website sponsor page, release or infrastructure acknowledgements, or a small static logo/name listing where relevant.
Sponsor listings should name only active, verifiable support. Until such support exists, the project should not publish placeholder logos or imply partnerships that have not been established.
For now, use the repository's GitHub Issues to propose infrastructure sponsorship or a project partnership. Describe the scope of the proposed support and the intended public attribution. Do not post credentials, payment information, private access tokens, or other secrets in a public issue.
Individual funding links or additional project contact channels may be added here later when they are formally enabled.