Sponsors

OculiX is built and maintained without commercial intent. It’s free under the MIT license, it will stay free, and there are no premium tiers planned. But running a project takes time, electricity, coffee, and the occasional CI hour — and any support is appreciated.

Ways to support

GitHub Sponsors

If you or your company use OculiX in production and would like to help cover the maintenance cost, you can sponsor the project via GitHub Sponsors. Any amount, recurring or one-off, helps.

There are no tiered perks, no exclusive features behind sponsor walls, and no priority queue. Sponsorship is a thank-you, not a transaction.

Contribute code or docs

Time is worth more than money. A PR that fixes a real bug, a docs page that prevents fifty support questions, an RC test on Apple Silicon — all of those are worth more than a one-line “thanks for the project” donation. See Contributing.

Spread the word

If OculiX saved you a week of automation work, mention it on:

• Your team’s internal wiki
• A blog post or talk
• A reply on Hacker News or Reddit when someone asks about RPA or visual testing
• A LinkedIn post tagging @julienmerconsulting

That kind of organic surface area is how this project keeps reaching new contributors.

Adopt at work, openly

If your team uses OculiX, let us know — even off the record. Knowing which industries lean on the project helps prioritize the roadmap. Email contact@oculix.org or open a discussion on GitHub.

Current sponsors

A heartfelt thank you to everyone supporting the project. The list of named sponsors is on the GitHub Sponsors page — and there are many more who help anonymously, in code, in bug reports, in RC tests, in translations.

If you’ve ever opened an issue or commented on a PR, you’re already on the list — just not the one with the badge.

Angels & patrons — OSS only

OculiX has zero commercial trajectory. There’s no SaaS to be built, no paid tier to ship, no exit to engineer. But we’re not against angels — backers who fund open source projects because they believe in keeping good tools free and well-maintained.

If you’re an OSS-friendly patron, foundation, or company that wants to underwrite continued maintenance, an integration, a translation push, or a multi-month roadmap of features that stay public, we’re open to talking. The conditions are simple:

• Everything funded ships in the public repo, under MIT, available to everyone — no private forks, no paid tiers.
• No expectation of commercial return, no equity, no exit path.
• Public acknowledgement of the funding is fine and welcome; no other strings.

If that fits your model, write to contact@oculix.org. If it doesn’t — i.e. you’re expecting OculiX to become a paid product — we’re not the right project, and we’d rather not waste your time.

On the spirit of the project

OculiX is MIT-licensed, which legally lets you do almost anything — including commercial use, including rebranding, including building products on top of it. We mean that genuinely: if OculiX helps you make something, we’re happy. Use it at work, ship it inside your product, embed it in a paid service. That’s what the license is for.

What we’d love in return, when it makes sense:

• Keep the link to the upstream project somewhere visible (a footer, an about page, a README)
• Open an issue or a PR when you find something — even a small fix
• Let us know you’re using it, even off the record, so the project knows it’s useful
• If a feature you’ve built is genuinely upstreamable, send it back as a PR

We aren’t going to police anyone’s usage. The MIT license is the contract — everything else is good faith. So far, good faith has been the rule, not the exception.

Thank you

To Raimund Hocke for two decades of SikuliX — every line of OculiX rests on that foundation. To every contributor who has ever opened a PR or tagged a bug. To the testers who pull every RC. To the translators making OculiX speak more languages. And to the geckos. 🦎