Aimogen is the direct continuation of Aiomatic. When the plugin was renamed, the intent was not to reboot or rebuild the product under a different identity — it was to remove a trademark conflict without interrupting the development trajectory. As a result, nothing meaningful in the code, features, or user experience was removed, deprecated, or fundamentally altered simply because of the name change. The plugin you knew as Aiomatic became Aimogen with the same internal engine, the same feature set (and expansions), the same data structures, and the same development roadmap.
Here’s what changed in a precise, user-facing way:
1. Brand and Name
The plugin’s identity changed from Aiomatic to Aimogen. Everywhere the old name was displayed — admin menus, documentation headers, readme files, and internal text — it now shows Aimogen. This affects:
- WordPress admin labels
- Plugin header text
- Update notifications
- Documentation and changelog entries
This rename is purely cosmetic and semantic. Functionality did not change.
2. Licensing and Distribution
With the rename came a shift in how licensing and updates are managed:
- Aimogen is now available on WPBay in addition to CodeCanyon.
- Envato (CodeCanyon) customers can migrate their license to WPBay.
- Coupons were provided to smooth the transition (full or partial credit depending on support status).
- A grace period exists where Envato licenses still work, after which WPBay licensing becomes required for updates and activation.
The licensing backend changed, but the plugin logic, feature availability, and update mechanism remain the same from the user’s perspective. Only the source of license validation changed.
3. Update Infrastructure
Because of the new licensing platform, the update delivery system has been adapted to support WPBay releases. Users may notice:
- A different update notification source
- A migration interface to enter a purchase code
- New subscription handling
However, updates—both minor and major—continue uninterrupted and on the same release schedule as before.
Now let’s be clear about what did not change — the core parts that matter day to day:
Features Did Not Change
All Aiomatic features moved over intact. This includes:
- Content generation (single, bulk, CSV, RSS, YouTube captions, Amazon reviews)
- AI Content Editor
- AI Chatbots with personas
- Voice chat and real-time interaction
- Image generation
- Embeddings and workflows
- SEO integrations
- Multimodal AI
- Provider architecture (OpenAI, Azure, AimogenAPI, Gemini, Claude, etc.)
Nothing was removed, and all previous feature configurations continue working after the rename.
User Data and Settings Did Not Change
Your settings, generated content, limits, logs, chat histories, provider configurations, and workflow setups remain exactly as they were under Aiomatic. The internal database tables, meta keys, options, and stored data structures have not been reset or migrated.
Developer Interfaces Did Not Change
Any hooks, filters, REST endpoints, internal APIs, and data structures that developers relied on remain the same. Custom code built for Aiomatic continues to work without modification, assuming it referenced plugin features and APIs rather than the old plugin name string.
Provider Integrations Did Not Change
Connections to OpenAI, Azure, AimogenAPI, and all other supported AI providers continue exactly as before. Nothing in how the plugin connects, authenticates, or executes AI calls was altered due to the rename.
Workflow and Automation Logic Is Identical
All execution pipelines, triggers, chatbot workflows, and content transformation logic behave the same. There was no redesign of how AI calls are orchestrated.
Why the Rename Happened #
A trademark conflict arose: another company holds the Aiomatic trademark and requested the name be retired. Rather than engage in a dispute or risk legal issues, the decision was made to rename the plugin and preserve development continuity. This was a branding decision, not a product decision.
What This Means for You #
If you were already using Aiomatic:
- You don’t lose features or data.
- Your existing setup continues to function.
- You will migrate your license to WPBay at some point, but everything within WordPress stays the same.
- All future development, including new features, improvements, and integrations, will happen under the Aimogen name.
If you are new to Aimogen:
- You are getting the same mature feature set with a clean brand and stronger update infrastructure.
- Documentation and tutorials reflect the new name but apply retroactively.
In summary:
Aiomatic → Aimogen is a rebranding and licensing transition, not a rewrite, pivot, or feature reset. The heart of the plugin — its AI capabilities, integrations, and extensibility — remains exactly as powerful as before, and continues to grow without friction.
