ClientWP vs Gutenbricks
We used Gutenbricks for years. The features were there. What was missing was predictability — when the next update would land, what it would change, and who would answer when something broke on a client site at 9 p.m. on a Sunday. This is an honest comparison, from people who have been on both sides of it.
The full comparison
Feature parity is not the whole story. A plugin you build your agency on is a long-term relationship with the people who build and support it.
| On a client site | Gutenbricks | ClientWP |
|---|---|---|
| Who can change the layout | Anyone with builder access, at any hour | Only you. Structure and classes are never exposed |
| What the client sees | The full builder: every panel, every setting | The fields you released, in the editor they already know |
| Training required | A builder walkthrough and a written “please don’t touch” list | None. It is the standard WordPress editor |
| Layout alternatives | Duplicate the template and keep both in sync by hand | Variants in one template. The client switches, the copy survives |
| Repeating content | One shared field set per page, or a template per card | Rows per block instance, so two lists on one page stay separate |
| Adding new sections | Every core block is available, including the ones that wreck the design | You allow, restrict or block each one, site-wide |
| Editing rich text | A plain textarea, or raw HTML with a warning attached | A real WYSIWYG with lists, bold, italic and links |
| Changing the design later | Touch every page that copied the old markup | Edit the template once. Every page follows |
| Migration from the other plugin | Rebuild every template by hand | Step-by-step migration with backup, verification and log |
| Support availability | Unpredictable — tickets can go unanswered | 24/7 human support from our team in Italy and Bulgaria |
| Who answers support | A queue, often staffed by people who have not seen the code | The people who write and maintain the plugin |
| Roadmap predictability | Release dates slip, no public commitment | Owned by us, developed on a plan we control and publish |
| Risk of the builder being abandoned | Real — we lived through it with Oxygen | None. We built this because we needed it ourselves |
Gutenbricks
- — Unpredictable support — tickets can go unanswered
- — Release dates slip with no public commitment
- — Support often staffed by people who have not seen the code
- — No migration path away if you decide to switch
- — The fear of an Oxygen-style rewrite is real
ClientWP
- ✓ 24/7 human support from our team in Italy and Bulgaria
- ✓ A roadmap we control and publish
- ✓ Support answered by the people who write the code
- ✓ Step-by-step Gutenbricks migration with backup and log
- ✓ Owned by two friends who built it because they needed it
Switch with confidence
The migration moves your Gutenbricks templates in minutes, with a backup and a log. If it does not fit the way you build, we refund within 14 days — no questions.
Single
For the individual creator shipping one site at a time.
- Every feature
- 12 months of updates and support
- Migration included
Agency
For agencies running a portfolio. Recommended.
- Every feature
- 12 months of updates and support
- Move licences between projects
Unlimited
For enterprises and large agencies that do not count sites.
- Every feature
- 12 months of updates and support
- Priority on support requests
Prices exclude VAT. When a licence lapses the plugin keeps working; updates and support stop. 14-day no-questions refund if it does not fit the way you build.