Stuck? Start here.
Most answers are already written down, so search the guide first. Not in there? Check GitHub Issues, then send a bug report.
Three stops, in this order.
-
Search the guide
Installing, property sources, custom widgets, MCP, licensing — most answers are already written down there.
-
Search GitHub Issues
Someone may have hit it already. If not, a public issue with steps to reproduce is the fastest way to get it looked at — and the next person finds the answer too.
-
Send the bug form
For a bug you'd rather not report in public, or anything that doesn't fit an issue.
Report a bug.
Whatever you send here gets read. What decides how quickly it gets fixed is whether it can be reproduced.
A report that can be fixed has
- The version and how you installed it — portable build, Docker or from source.
- The exact steps that make it happen, starting from a fresh page load.
- What you expected, and what you got instead.
- Anything from the browser console or server log that looks related.
No response time is promised here, or on issues — a guaranteed answer every working day is the one thing a small team can't honestly sell. Need it fixed on your own schedule? Patch it yourself, since the source is yours, or hire it out through Services.
The source is already yours.
Your machine runs fifteen years. Your HMI never waits on us.
- Open, today
- All the code that draws your screens is public. Fix it and rebuild it yourself.
- Your files stay yours
- Plain JSON and CSV. It's written into
LICENSE-EXCEPTION.md. - Licences never lapse
- Perpetual, with no renewal date. The free build runs your project any day.
Sources: COMMERCIAL.md in the repository.
How fast will I get a reply?
No promised time, on any of the three channels — that is deliberate, not an oversight. A guaranteed response on every working day of the year is the one thing a small team cannot honestly make, so it is not sold rather than sold badly. In practice, docs answers are instant and issues get looked at as they come in.
Where do I report a security vulnerability?
Not the bug form or a public issue — a working exploit in a public issue exposes every deployment until a fix ships. Use GitHub's private vulnerability reporting under this repository's Security tab, or email info@next-hmi.com with subject SECURITY. Full policy: security in the guide.
I bought a redistribution licence — do I get faster support?
No, and that is by design. The licence buys white-label, release from the AGPL source obligation, and a signed key — never a response time or a support tier. Support is a separate line, quoted per assignment, open to licence holders and free-build users alike.
Is there a community forum or chat?
Not yet. GitHub Issues is the current venue for anything public. If that changes — Discussions, a chat — it will be linked from this page rather than announced somewhere you would have to go looking for it.
I need this fixed on my own timeline. What are my options?
Two, and both stay available regardless of what support answers: patch it yourself — the whole platform is yours to read, fix and rebuild — or hire it out through Services, quoted per assignment rather than queued behind a ticket. See why that is always on the table.