Aimogen feature requests are handled publicly and transparently through a dedicated ideas board. This keeps development direction visible, avoids duplicated requests, and allows the community to actively influence what gets built next.
All feature requests go here:
Trello board – https://trello.com/b/2yxVZapo/aiomatic-feature-ideas
This board is shared with the legacy Aiomatic name for continuity. It is the official feature ideas board for Aimogen.
Feature requests should not be sent via email support. Support is for bugs and malfunctions. Feature ideas belong on the Trello board so they can be discussed, refined, and voted on publicly.
When you submit a feature request, you can either:
- add a new card if the idea is not listed yet
- vote or comment on an existing card if it already matches your idea
Voting matters. Cards with strong community interest are prioritized more easily than isolated requests.
A good feature request explains the problem, not just the solution. Describe what you are trying to achieve, why the current functionality is insufficient, and what kind of workflow would improve things. Avoid implementation assumptions. Aimogen evolves based on use cases, not just technical novelty.
Requests that include real-world scenarios, scale considerations, or monetization use cases tend to be evaluated faster because they show broader impact.
The Trello board reflects the real development pipeline. Cards typically move through states such as ideas, under consideration, planned, in development, and completed. Not every idea will be implemented, but every idea is reviewed. Public visibility keeps expectations aligned.
Commenting on existing cards is often more effective than creating duplicates. If a card already exists, adding your use case or edge case in the comments gives it more weight without fragmenting discussion.
The board is also the best place to understand why certain features are delayed or rejected. Some ideas conflict with Aimogen’s design principles, cost-control model, or long-term maintainability. Public discussion helps clarify those decisions.
Feature requests are evaluated alongside:
- technical feasibility
- performance impact
- cost implications
- security and abuse risk
- compatibility with existing workflows
- long-term maintenance burden
This is why some ideas take time even when they are popular.
In short, if you want to influence Aimogen’s future, the Trello ideas board is the right place. Post your idea, explain the use case, vote on others, and follow progress openly. That feedback loop is a core part of how Aimogen continues to evolve.
