How StackRegent feature ideas are reviewed and planned

Write an idea that gets understood#

The most useful ideas start with the problem, not only the solution. "Our customers deploy .NET apps from Azure DevOps and we copy the files by hand" tells us more than "add Azure DevOps", and often leads to a better answer, perhaps one that also works for GitHub Actions or GitLab. Then say what you would like to happen.

A good idea answers:

• Who needs it: the server administrator, resellers, or hosting customers in their own panel.
• What they are trying to do, and what they do today instead.
• How often it comes up, and on how many servers or accounts.
• What it touches: IIS, PHP, ASP.NET, mail, DNS, databases, backups, the REST API, licensing, or the installer.

One idea per post. Two unrelated wishes in one idea are hard to vote on and hard to plan.

Check for the same idea first#

Search the board before posting. If someone had the idea already, vote for it and add your use case as a comment. Ten votes on one idea say far more than ten copies of it. When we find duplicates, we mark the newer one Duplicate and point to the original.

How ideas are reviewed#

Every new idea is read by the StackRegent team. During review we check that the idea is clear, that it is a feature request rather than a bug report or a support question, and that it is not already on the board or already in the panel under another name. Clear ideas are then listed as Open for votes. If something already does what you asked, we say where to find it.

Bug reports and support questions are better handled in a support ticket, where we can ask for logs and server details. Security problems belong in a private report to support@stackregent.com, never on a public board.

How we decide what to plan#

Votes matter, but they are not the only thing we weigh. We also look at:

• Reach: how many kinds of hosting setup the feature helps, from a single company server to a provider with resellers.
• Fit: whether it belongs in a Windows hosting panel, and whether it works the same for administrators, resellers and customers.
• Safety: a panel runs with administrator rights on every server it manages, so features that touch security, isolation or updates get extra care.
• Effort and upkeep: how much work it is to build, test on Windows Server 2016 to 2025, and keep working through updates.
• Third parties: whether it depends on software or services we do not control.

When we plan an idea, its status becomes Planned and the team adds a note about what is decided. Being built means work has started. Plans can change as we learn more; when they do, the note says so.

What we do not promise#

Moving an idea to Planned is a statement of intent, not a delivery date. We do not commit to dates or versions on the board, and a planned feature may ship in a different form than first described, or in parts. If we decide against an idea, it becomes Not planned with the reason, so you are not left waiting.

Every StackRegent plan has every feature, so a released idea reaches all licensed servers through the normal signed updates; nothing is held back for a higher plan. What each version actually brought is in the release notes and the changelog.

Comments and conduct#

Comments should add information: a use case, a detail, an edge case, a workaround that helps others. "+1" comments add nothing a vote does not. Keep it civil and on topic, and leave out customer data, passwords, license keys and server addresses. New members' comments may wait for a moderator before they appear.

Want to talk an idea through before posting it? Start a thread in the community forum and link it from the idea once it takes shape.