OculiX is free and open source under MIT. It isn’t built as a commercial product, there’s no SaaS, no usage tracking, no paid SLA out of the box. But none of that means closed — if your team is using OculiX seriously, we want to hear about it, and we’ll do what we can.
Bug reports
Crashes, regressions, unexpected behavior, broken docs → open an issue at oculix-org/Oculix/issues.
A good report has: a minimal reproducer, expected vs actual, environment (OS / Java / OculiX version), and the stack trace. The IDE menu Help → Copy diagnostic info grabs all that in one click.
Questions & discussions
For broader questions — “how do I…?”, “what’s the best way to…?”, “is OculiX a good fit for…?” — use GitHub Discussions. The community answers there, and so does the maintainer when time allows.
Security issues
For anything sensitive (auth bypass, RCE, credential leakage in logs), do not open a public issue. Use GitHub’s private vulnerability reporting.
Full policy in SECURITY.md. Acknowledgement within 48h.
Your team uses OculiX at work
If a team, a department, or a whole company runs OculiX in production and wants to talk to the maintainer directly — about a specific need, an integration question, roadmap influence, or just to say hello — email [email protected] or open a discussion.
Many companies on the Showcase page found OculiX through a single engineer’s bug report.
OculiX is maintained by around a dozen contributors, with about three active maintainers at any given time, mostly on personal time. The realistic first-response numbers:
| You report a… | First response in… |
|---|---|
| Reproducible crash | A few days, often sooner |
FindFailed you can repro | A week |
| Feature request | Triaged within a week — implementation timeline varies wildly |
| Security advisory | Acknowledged within 48 hours |
| Email from an organization | Read within a few days, replied within a week |
Six dedicated engagements, each with its own page. Click through for scope, deliverables, examples, and FAQ.
OculiX is an expert open-source project with 20 years of lineage — the reference for JVM visual automation, not a commercial vendor. That doesn’t mean “no” to your requests — it means everything is case-by-case, decided in direct conversation with the maintainer rather than through a procurement department. Things that have actually happened:
master faster than the normal RC cycle because a regulated industry hit it and provided a clean repro.In short: if you have a real need, write to us before you assume it’s impossible. The honest answer is often “yes, here’s how” or “yes, with this caveat” — not “no”.
Build from source
If you need a fix that’s on master but not yet released:
git clone https://github.com/oculix-org/Oculix.gitcd Oculixmvn clean install -DskipTestsThe fat-jars in each module’s target/ directory are exactly what gets uploaded to Maven Central on release.
Fork and patch
OculiX is MIT-licensed. Fork it, patch the issue you care about, run your own build. If the patch is generally useful, open a PR upstream — it’s the highest-leverage thing you can do for the project.
Subscribe to releases
The fastest way to know a fix is out: watch the repo. GitHub → Watch → Custom → Releases. You get an email for every new RC and stable.
OculiX runs entirely on your machine. Nothing phones home, nothing sends telemetry, no analytics, no auto-update. The optional MCP server module writes an Ed25519-signed, SHA-256-chained JSONL audit journal — designed for environments where every action needs to be auditable.
Where OculiX fits well
Worth a conversation first
For procurement-grade documentation packs, head to the Security & compliance page or reach out at [email protected].
If OculiX saved you time and you’d like to give back, the most useful things are:
We’d love both — a contributor entry and a sponsor entry. Either alone is already a huge help.