Found something that looks wrong? A clear, reproducible bug report is the fastest way to get it fixed. This page explains where to send a report, what to check before you do, and what to put in it so we can act on it without a back-and-forth. It applies to ordinary bugs — a daemon that misbehaves, a playbook that does the wrong thing, an unexpected error. Security issues are handled differently and must not be reported here; see the callout below.
Check first — it might already be solved. Many issues have a known cause or a documented workaround. Before reporting, skim the relevant Troubleshooting page and the latest release notes — the behaviour you are seeing may be a known limitation, a fixed bug in a newer build, or an intentional change.
A couple of minutes of checking saves you a slow round-trip and often answers the question outright:
Binions is published by SmartX Technologies Ltd (United Kingdom). There are two places to reach us, depending on what your report is about:
| Your report is about… | Where to send it |
|---|---|
| The platform — a bug, a crash, wrong behaviour | Use the contact options on the website, https://binions.io |
| Your account, licence, lanes, tokens, or installs | Sign in to your customer portal, https://portal.binions.io |
| A security vulnerability | Do not report it here — use private disclosure (see below) |
Binions is in alpha. The platform is in pre-production, so there is no public forum, issue tracker, or published response-time commitment yet. The website and your customer portal are the channels to use today.
The more of the following you include, the quicker we can pin down the cause. At a minimum, a useful report tells us:
The Preparing a report page turns this into a short checklist, and Collecting logs gives the exact commands to gather the version, the daemon logs, and the trace of a single failing run.
Security issues go elsewhere. If you have found a vulnerability — anything that could let someone bypass licensing, reach an internal service, or compromise a host — please report it privately through Reporting vulnerabilities. Never post a security problem to a public channel or a normal bug report.
Finally, keep it factual and reproducible. One clear report — version, daemons, steps, expected vs. actual, logs — is worth more than several vague ones.