Companies funding Mnemosyne development
Compute credits, hosting, and developer tooling that keep Mnemosyne's benchmarks, CI, and integrations running. Every partnership is disclosed and editorial control stays with us.
Compute Partners
LLM, embedding, and GPU API credits powering our nightly benchmarks, multi-model recall suites, and provider parity tests.
| Partner | ||
|---|---|---|
| We're looking for LLM, embedding, and GPU compute partners. If your company runs an OSS credits program, get in touch. | ||
Compute Partners are disclosed material connections under FTC Endorsement Guides (16 CFR Part 255).
Infrastructure & Tooling Partners
Hosting, observability, and developer tooling credits that keep this site, our CI, and our maintainer workflow online.
| Partner | |
|---|---|
| partners.tooling.empty | |
Tooling Partners are disclosed material connections under FTC Endorsement Guides.
Creative Partners
Platforms and model providers powering generative creative work — text-to-image, text-to-video, voice, music, and design tools — used to build Mnemosyne's brand, website, demos, and creative assets.
| Partner | |
|---|---|
| We're looking for creative partners — text-to-image, text-to-video, audio, music, and generative design platforms — who want to support open-source visual storytelling. | |
Creative Partners are disclosed material connections under FTC Endorsement Guides (16 CFR Part 255).
Want to be a creative partner?
Open an issue on GitHub or email us with what you offer. We respond within a few business days.
Open an issue on GitHubBackers
Individuals and small companies supporting development through OpenCollective, GitHub Sponsors, and Ko-fi. Thank you.
Support on OpenCollectiveSponsorship Policy
This page is part of the Mnemosyne project, maintained by the Mnemosyne core team. The sponsorship program is independent, editorial control stays with the maintainers, and every partnership is disclosed publicly.
What we accept
Mnemosyne accepts in-kind sponsorships in these categories:
- Compute credits (LLM, embedding, GPU inference)
- Hosting and infrastructure credits
- Developer tooling licenses and observability platforms
What we do not accept
Some things aren't on the table, regardless of how the partnership is structured:
- Payment for feature prioritization or roadmap placement
- Payment for integration order in code or documentation
- Sponsorships from companies whose products conflict with our values (surveillance, privacy violations, vendor lock-in by design)
- Editorial veto over benchmark methodology or technical content
Disclosure standards
All sponsor contributions appear on this page with clear 'Compute Partner' or 'Tooling Partner' labels. When we publish content about a sponsor or their product (benchmark results, release notes, blog posts, social mentions), we use '#ad' or 'Sponsored' language per FTC Endorsement Guides. We publish our editorial control policy publicly so anyone can see what we will and will not do.
Editorial control
The maintainer retains full control over benchmark methodology, results, and any technical claims made about sponsor products. Sponsors cannot edit, veto, or suppress our technical content. If a sponsor's product has a real flaw surfaced by our benchmarks, we publish it.
Termination
Either party can end a sponsorship at any time. On termination, we remove the partner's listing within 30 days.
Get in touch
Open an issue on GitHub tagged 'sponsorship' or email sponsors@mnemosyne.site. We respond within a few business days.
We respond to all serious inquiries within a few business days. Tell us what your company offers and how Mnemosyne would use it.
Open an issue on GitHubor email sponsors@mnemosyne.site