2025 Year End Review – Rebuilding Foundations Of My Business

Welcome guys to another year end review post. This one is for 2025, a year that for me felt very different compared to the ones before it. 2025 was about taking control, rebuilding foundations and making long-term decisions that will help me to continue to work on WordPress plugins, the thing that I enjoy doing the most.

As always, I’m really happy I can sit down and write this post, as I really feel that these “Year End Review” posts are my own personal checkpoints, which allow me to look at the bigger picture of events which happened this year. If you are curious about how things evolved over time for me, you can also check the previous “Year End Review” posts I wrote over the years: 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024.

Trust me, when you work daily on code or support tickets, time can really become blurry for you. A year end post like this one, forces me to bring everything back into focus and often reveals patterns I don’t notice while I’m in the middle of things. So, looking back at 2025, I am sure that one thing stands out clearly for me: this was the year of gaining independence from platform limitations which no longer aligned with how I want to build and sell my plugins.

The major tectonic shift: from CodeCanyon to WPBay

One of the biggest changes this year was moving my plugins away from CodeCanyon and fully embracing a new ecosystem I built together with Stefan, a fellow WordPress developer. This wasn’t a rushed decision, as we both felt the need of moving to a new place for a while now. WPBay was built to be a new home for our plugins, where rules are not dictated against developers, but in favor of them.

That decision materialized into the creation and launch of WPBay.

WPBay is not meant to be just another marketplace. It’s a platform built with developers in mind, focused on fair pricing and long-term growth, as this marketplace was built for ourselves in the first place. Launching WPBay was one of the most challenging things I’ve done so far, but also one of the most rewarding. From infrastructure and licensing to payments and customer experience, everything had to be thought through from scratch.

At the same time, I started moving my plugins there, one by one. This allowed me to move faster and make decisions that benefit users directly, without fighting against constraints that were never designed for complex, evolving plugins. One of these was the inability of CodeCanyon to sell plugins using a yearly/monthly subscription model. This is required for very complex plugins like Aimogen, which require monthly (if not weekly) updates to continue to function at its best (as the AI world is changing so fast).

Another major move: Aiomatic became Aimogen

Another important milestone of 2025 was the rebranding of Aiomatic into Aimogen.

This change wasn’t just cosmetic. In October I was contacted by a company that they created a new trademark for the ‘aiomatic’ name and that they request me to stop using this name for my plugin, as it was their property now. I complied without messing around too much on this subject and rebranded Aiomatic to Aimogen. The Aimogen name is inspired by the following phrase: AI MOmentum GENerator.

The rebrand also came with internal code cleanup, new admin user interface and more minor fixes for issues. Aimogen continues the trend set by Aiomatic, to not just react to AI trends, but to create new trends by itself, like the creation of the OmniBlocks feature, which allows unparalleled AI automation potential.

AI itself continued to evolve at an insane pace also in 2025. AI Models became faster and cheaper, slightly more capable (maybe not as capable as some of us anticipated at the end of the last year). So, instead of chasing every shiny new AI API, my focus was on giving users tools that actually work in production environments in a helpful way. Aimogen benefited massively from that mindset.

Latest Plugin Developments in 2025

2025 was probably the most intense development year I’ve ever had, as this was the year where many ideas that had been sitting in my head for a long time finally became reality.

So, Aimogen had, by far, the most active development cycle. Throughout the year it slowly transformed from a powerful AI assistant into a full automation layer inside WordPress. The AI Content Editor stopped being “just an AI powered editor” and became a real creation tool, capable of generating complete posts, working with templates, editing existing custom fields and managing SEO-related data automatically. A lot of attention went into making AI-generated content feel native to WordPress, not just bolted on it.

Another focus was on the chatbot, which gained smarter behavior, language detection based on the visitor’s browser, better conversation control, the ability to handoff the conversation to real humans, conversation endings and more. Under the hood, Aimogen became much more dynamic, by adding support for a wide range of AI providers, which expanded massively, from OpenAI and Google to DeepSeek, xAI Grok, Venice AI, Alibaba Qwen, Ollama Cloud and others. MCP support was also a major milestone this year, allowing Aimogen to work both as an MCP client and server, integrating itself with tools like Claude Desktop or ChatGPT.

Automation also reached a new level. OmniBlocks became smarter and more flexible, with AI-generated templates, new WordPress event triggers, speech-to-text blocks, form-based triggers and the ability to call complex OmniBlock sequences directly from the chatbot. AI forms themselves evolved also, gaining LaTeX and HTML support, remote usage, captchas, and deeper integration with other plugins like Paid Memberships Pro, Booking Calendar, wpForo, Rank Math. On the other hand, Aimogen learned how to automatically rename media files for SEO using AI, generate bulk SEO fields for media items, choose different image generation strategies for featured images versus in-content images and even work with Stable Diffusion as a proper image editor. Storage support expanded well beyond basic setups, adding compatibility with many S3-compatible providers like Backblaze, Linode, Storj, Vultr, and IBM.

So, as you can see, Aimogen got tons of new features this year. Outside of Aimogen, other plugins also moved forward steadily. Threadsomatic matured into a reliable Threads auto-poster (which is also sold only on WPBay), WordPressomatic gained multi-site publishing ability, VKomatic adapted to API authentication changes and scraping-related plugins (like Crawlomatic) received important stability and compatibility updates. Nothing was left behind, even during a year full of big structural changes like 2025.

WPBay itself was also part of this development story. Beyond the launch, it quickly started hosting plugin sale campaigns and getting feature updates to evolve in a better platform for its sellers.

Continuously documenting my journey during 2025

Throughout 2025, I continued publishing videos and sharing progress, talking about the experiments I do and about the lessons I learned. Some of the most dear and meaningful moments this year didn’t come from code, though. They came from watching curiosity spark in someone else. That brings me to how I want to end this little post I am writing.

Ending 2025 with a smile on my face

At the end of this year, me and my daughter Maya did managed to do something together, that genuinely made me stop and smile. She was interested on her own to built her first blog on wordpress.com and asked me for help, so she can start her first little blog. We documented this process, in the below video.

The result was a moment she’ll probably remember for a long time. I’ll let the resulting videos speak for themselves:

As 2025 comes to an end, I’m really grateful for the freedom to build things my way and what to thank everyone who supported the transition to WPBay, the users of my plugins who continue to trust my work.

So, a big thank you for being part of this journey! I hope 2026 will allow me to write a similar post during its ending period.

Happy New Year and see you in the next one! 🙂