One WordPress plugin. 600+ agencies. One agency that got tired of installing 30 plugins on every client site.
Classic Monks is built by an agency, for agencies. We are the people who use the plugin every day to ship client work. We are also the people who got frustrated enough by the WordPress plugin sprawl to spend 9 months building the thing we wished existed.
An agency that ships a product
because it had to.
Classic Monks is a product of GoodMonks Solutions, a WordPress development agency founded in 2022. We build client sites. We maintain client sites. We have been the team on the other end of a 2 a.m. “the site is down” call more times than we want to remember.
The agency is based in India, with clients across the US, UK, Europe, and Australia. We are a small team, deliberately. We are not a 40-person SaaS company with a venture round and a growth quota. We are builders who charge for outcomes, and we are picky about which outcomes we take on.
That same builder-first sensibility is what we tried to put into Classic Monks. Every feature in the plugin solves a problem we hit on a real client build. None of them are guesses.
Seven years of plugin sprawl,
condensed into one build.
In 2017, Joy Chetry, the founder of GoodMonks, started building WordPress sites professionally. The work was interesting. The toolchain was not.
Every new project started the same way: a fresh WordPress install, a checklist of 20 to 30 plugins to install and configure, a stack of yearly subscriptions to manage, a long evening of debugging conflicts between plugins that had never been tested together. The first four hours of every project were spent rebuilding the same setup.
We did not build it because we wanted to start a SaaS company. We built it because we were tired. Then we found out 600+ other agencies were tired too.
After seven years and several hundred client sites, the inefficiency stopped being a cost and started being a problem worth solving.
In 2022, the agency was formalized. In 2023, after another year of running client builds, the team started prototyping what would become Classic Monks. The first version was an internal tool. The second version was tested with three partner agencies. The third version became the public plugin.
Classic Monks launched in 2025. The first version replaced 20+ plugins. The current version (1.2.1) replaces 16 of the most-installed categories across performance, security, login, forms, AI, Bricks, WooCommerce, and admin workflows. The 393+ features inside it are battle-tested across thousands of production sites.
“I started building WordPress sites in 2017 because the work was interesting. The toolchain was not. Every new project started with a fresh install and a checklist of 20 to 30 plugins. The first four hours of every project were spent rebuilding the same setup. After a few hundred sites, that stops being a cost and starts being a problem worth solving.”
Founder & Lead Developer,
GoodMonks Solutions
The plugin exists because we got tired of installing 20 plugins on every project.
The WordPress plugin ecosystem rewards fragmentation. Every problem has a plugin. Every plugin has a yearly fee. Every fee feels small in isolation. In aggregate, agencies spend thousands of dollars a year on overlapping functionality, plus the hidden cost of managing all of it.
Most plugin companies solve one category and call it done. We are not interested in being the best plugin in any single category. We are interested in being the last plugin an agency has to think about.
That is the entire reason the plugin exists. The rest of the website explains what it does. This page is about why we bothered.
A small core team based in India.
The same engineers who build the agency's client sites.
Classic Monks is built and maintained by a small core team based in India. The team is led by Joy Chetry, the founder of GoodMonks Solutions, and includes the same engineers who build and maintain client sites on the agency side.
The team is intentionally small. We are not chasing venture scale. We are building a plugin that we use on our own client work, that pays for itself, and that we can keep supporting for years without burning out.
We are not hiring aggressively. We are not raising capital. We are building a sustainable product for a specific kind of customer, and we are building it the way we build client sites: carefully, with intention, and with a long horizon.
Note: The team page on classicmonks.com is being updated. Names, roles, and photos will be added as we get current with the people who actually work on the plugin. If you are evaluating the company and want to talk to a real person, the forum and the support email are the fastest way to reach us.
Four values,
in order of how often we act on them.
1
Ship the thing you would use yourself
Every feature in Classic Monks exists because someone on the team needed it on a real client build. If we would not use it, it does not ship.
2
Be honest about what we do not do
Classic Monks is not a backup plugin. It is not a full-page cache. It is not an SEO plugin. We do not pretend those categories are in scope, and the /why page has a section called “What we won’t promise” that calls this out by name.
3
Treat the plugin like a product, not a side project
Updates ship on a real cadence. Bug reports get real responses. The changelog is public, the forum is moderated, the support inbox is read by a person, not a bot.
4
Build for the long game
We are not optimizing for a hockey-stick growth chart. We are optimizing for a plugin that still works in 2030 on a site built today. That means clean code, real testing, and no breaking changes shipped to chase a feature checkbox.
Verifiable, current, and public.
These are pulled from the live pricing page, the changelog, and the public plugin header. Updated as the plugin grows.
v2.1.0
Current version
393+
Features in plugin
1,600+
Active sites
600+
Agencies on CM
7+
Years WordPress experience
15
Day money-back guarantee
7.0
WordPress tested up to
2.3.8
Bricks Builder tested up to
Practical things worth knowing.
A few things that are worth knowing if you are considering us as a long-term bet.
Real support, not a chatbot
The support email and the forum both go to a person on the team. Response time is not instantaneous, but it is real.
Public roadmap, community-voted
Bricks is the deepest integration today. Elementor, Gutenberg, and Breakdance integrations are planned for 2026 in user-voted priority order. Roadmap input comes from the forum and from direct agency conversations.
Updates ship regularly
The current release cadence is roughly one major version per 6 to 8 weeks, with patches as needed. Every release is documented in the changelog with named credits to the community members who reported the bug or suggested the feature.
No data leaves your site
All settings, logs, and form submissions stay in your WordPress database. Classic Monks does not phone home, does not require an account to use core features, and does not lock content inside a vendor-controlled system.
Encryption where it matters
License keys are stored encrypted. Site data, form submissions, and short links are stored in your own database, on your own server. We have no copy of them.
If you want to talk to a person, here is where to find one.
One more thing.
We are not going to pretend the plugin is for everyone. It is for agencies and developers who maintain other people's WordPress sites and who would rather install one plugin and get back to work than manage a stack of 20.
If that is you, we built the plugin for you. If it is not, the rest of the WordPress ecosystem is full of good plugins, and we genuinely hope you find the right one.
The plugin is one download. The 15-day money-back guarantee is real. The support email is read by a person.
That is who we are.