Community
Community guidelines
These guidelines apply to every category of the forum.
The forum works because people help each other. These are the rules that keep it that way. They are short on purpose — if something here needs a lawyer to interpret, we have written it badly.
Who can read and post
Anyone can read the forum, without an account. Posting is open to customers with an active license and to beta testers while a beta program is running. Some categories are narrower — the Beta Test area is for people in the program, and Showcase is for things you have actually built. If you can read a category but not post in it, that is why.
Treat people well
Disagree with the argument, not the person. No harassment, personal attacks, slurs, or content that demeans someone for who they are. Being technically right does not license being unpleasant about it, and "just being honest" is not a defence for cruelty. People asking beginner questions are the reason a forum is worth having; answer them as you would want to be answered.
Never post secrets
License keys, activation requests, API tokens, passwords, private keys, and TLS certificates do not belong in a public post — and neither do the internal hostnames, IP addresses, or network layouts of a deployment you would rather strangers did not know about. Redact logs before pasting them. If you post something sensitive by accident, edit it out and tell us; we will help, and we will not make it a thing.
Security issues go to us first
If you find a vulnerability in KyriosForge or anything else we make, please do not post it publicly. Open a support ticket, or use the contact on our Security Advisories page. We will work it with you and credit you when it is fixed if you want the credit. Public disclosure before a fix exists puts other people's deployments at risk, which is the opposite of what a security report is for.
Make a question answerable
Post in the category that fits, and give enough to work with: what you ran, what happened, what you expected instead, the version, the platform, and the relevant part of the log. "It does not work" cannot be answered by anyone, however much they want to help. If you solve it yourself, come back and say how — the next person searching for the same error will thank you.
Self-promotion and spam
Showcase is the place to show what you built, including if it is commercial. Elsewhere, keep promotion incidental to the conversation. No affiliate spam, no bulk posting, no AI-generated filler posted to farm presence. Recommending a competing tool because it genuinely fits someone's problem is fine, and welcome — we would rather be honest than the only answer.
Licensing
Do not use the forum to share license keys, to help someone work around activation, or to arrange access to a tier they are not entitled to. If the pricing does not work for your situation, tell us — students, academics, and nonprofits have paths, and we would rather hear the problem than watch someone route around it.
How we moderate
We may edit, lock, move, or remove posts, and may suspend forum access for repeated or serious breaches. We will normally say why. The lightest thing that solves the problem is what we reach for first — most of the time that is a reply, not a deletion. If you think a moderation decision was wrong, open a support ticket rather than relitigating it in the thread; we will look again, and we do change our minds.
A note for the beta
Beta builds are pre-release. Things will break, behaviour will change, and something you report today may be gone tomorrow — that is the point, and the reports genuinely shape what ships. Say which build you are on when you report something, and expect answers to be provisional. Nothing discussed in the beta area should be taken as a commitment about the final product.
Something not covered here?
If a situation is not addressed by any of the above, use your judgement and assume good faith on everyone else's part. If you are unsure, ask us.
Open a support ticket