Skip to content

SPONSORS.md

Latest commit

 

History

History
120 lines (92 loc) · 5.3 KB

SPONSORS.md

File metadata and controls

120 lines (92 loc) · 5.3 KB
Raw

Sponsors

wigolo is free for all, and it is meant to stay that way.

There is no paid tier, no metered plan, and no feature held back for people who pay. The core tools need no API keys and send nothing to a third party. That is the whole point of the project, and sponsorship is what makes it sustainable to keep it that way.

Thank you

TestMu AI

TestMu AI

TestMu AI (formerly LambdaTest) is the world's first full-stack agentic AI quality engineering platform, trusted by 18,000+ enterprises.

TestMu AI is wigolo's first sponsor. Thanks for the support.

Want to sponsor wigolo?

There is room for more companies and individuals alongside the sponsors above. If keeping a free, keyless, local-first web layer maintained is worth something to you or your team, I'd love to hear from you.

Get in touch: ktowhid20@gmail.com — it goes directly to the developer who writes the code, not a sales inbox.

A one-off contribution is just as welcome as a sponsorship, via Buy Me a Coffee.

Companies are invoiced directly and paid by bank transfer, so there's no platform account to set up on your side and nothing skimmed off the top by a middleman. Whatever billing details your finance team needs on the invoice, just say and I'll put them on it.

What sponsorship funds

Sponsorship goes into the work itself: maintenance and releases across macOS, Linux, and Windows; search and extraction quality; CI and benchmarking; and the time to answer issues from people running wigolo in production.

What a sponsor gets

  • A logo and a one-line description in the README sponsors section.
  • The same placement on the project website and on this page.
  • A link on every placement, with its reach measured — figures available on request, see Measurement below.

How sponsorship and the project stay separate

Sponsors support the work without steering it. That protects them as much as it protects users: nobody has to wonder whether a ranking, a benchmark, or a doc was shaped by who paid, and a sponsor is never on the hook for what the project ships. These are the standing terms for every sponsor, so they're the same conversation each time.

  • The roadmap and the code stay independent. Nothing is built, ranked, prioritised, or benchmarked differently because of sponsorship, and a sponsor's own service gets no special standing in search results, adapters, or docs.
  • Non-exclusive. Other sponsors are welcome, including ones in the same market.
  • The sponsors section stays the project's to run — its placements, tiers, and who appears in it.
  • No claim over the project. No CLA, no copyright assignment, and no limit on how wigolo is licensed or commercialised, now or later.
  • No endorsement implied in either direction. A logo here is a thank-you, not a technical endorsement of wigolo by the sponsor, or of the sponsor by wigolo.

Amounts and duration are worked out per conversation — reach out and we'll find something that fits.

Measurement

Sponsor placements are measured, so there are real figures behind them rather than a vague claim of exposure. The method is public here; the numbers are shared on request.

Every sponsor link on every surface points at a /go/<slug>/ link on the wigolo site rather than straight at the sponsor. That hop counts the click, then forwards to the sponsor's own URL with a utm_content tag naming the placement it came from, so each placement can be told apart.

What is measured:

  • Clicks, by placement, over time, from the project's own counter.
  • Reach, as a proxy for impressions — repository traffic and the site's pageviews. README impressions can't be counted accurately, because GitHub proxies and caches images; repo views are the stand-in, and they're described as exactly that.
  • What is never collected — no cookies, no third-party tracking script, no local storage, and nothing stored about the individual visitor. The counter records that a click on a placement happened, not who made it.

The implementation is in site/src/lib/sponsors.ts and the interstitial in site/src/app/go/[slug]/ — read it if you'd like to know exactly what is recorded.

Notes for contributors

  • Sponsors live in one place: the SPONSORS array in site/src/lib/sponsors.ts. Adding one there generates its /go/<slug>/ page and its card on the website.
  • Logos go in assets/sponsors/ (for the README) and site/public/sponsors/ (for the site), with a light and a dark variant — a single-theme logo goes invisible on one of GitHub's two themes.
  • Sponsor links must always go through /go/<slug>/, never directly to the sponsor, or the click goes uncounted and the placement becomes unreportable.
  • The tracked-link contract is covered by tests/unit/sponsors-links.test.ts.