BRX Prod is currently in Beta. While in beta we are offering 40% license discounts

Pricing

How we differ to other plugins

What sets us apart

A fair question, and one I get often. There’s a healthy and growing ecosystem of tools around Bricks Builder — here’s how BRX Prod fits in.

The short answer

BRX Prod is a productivity toolkit — tools that make Bricks itself faster to use. It’s not a CSS framework, not a design system, not a starter theme. If you already have a way of building sites you’re happy with, BRX Prod plugs in alongside it without changing how you work.

What it isn’t

To save you time, here’s what BRX Prod is not:

  • Not a CSS framework. It doesn’t ship a system of utility classes, design tokens, or pre-built components. You bring your own conventions; BRX Prod helps you author and apply them faster.
  • Not a starter theme or template kit. It doesn’t put pages or layouts on your site. Other tools do that well; this one doesn’t compete.
  • Not a frontend dependency. Nothing BRX Prod does ends up in the HTML / CSS / JS that ships to your visitors. If you deactivated the plugin tomorrow, your sites would render exactly as they do today.
  • Not a different way of using Bricks. BRX Prod runs alongside Bricks’ native UI — it doesn’t replace the panels, the structure tree, the class manager. It adds shortcuts, helpers, and AI on top.

What it is

BRX Prod focuses on the builder-time experience: the time you spend actually inside the Bricks editor putting a site together. Specifically:

  • Better keyboard shortcuts and a custom CSS panel with typeaheads and BEM helpers.
  • Structure-panel enhancements (BEM auto-generation, expand/collapse, element shortcuts).
  • AI-assisted text completion, image generation, and font pairing — integrated where you’d naturally reach for them.
  • Workflow tools (layout-width labels, content debug, attribute bar, isolation mode) that you opt into per feature, per project.
  • A clean separation between Bricks’ UI and BRX Prod’s UI — different colour palette, distinct visual language — so you always know what’s what.

Where it overlaps with other tools

The Bricks ecosystem is small enough that any new tool will overlap with something else. BRX Prod is no exception. Where you’ll see overlap:

  • Other tools that focus on builder productivity — we share a philosophy: developer experience inside Bricks is worth investing in. Where we differ tends to be on which workflows we prioritise and how opinionated each tool chooses to be.
  • Tools that ship a CSS framework or design system — these solve a different problem (how to write CSS). BRX Prod is downstream of that decision — it helps you author whatever CSS you already write, faster.
  • AI plugins for WordPress — most are surface-level integrations with one provider. BRX Prod’s AI is specifically tuned for the Bricks editor: image controls that know about the element you’re editing, completion that respects your global instructions, font pairing that installs results into Bricks’ theme styles.

What might make BRX Prod the right choice

The pitch is short:

  • You build with Bricks Builder regularly.
  • You want it to be faster to use without changing the way you build.
  • You don’t want to add anything to your live sites that you’d have to support forever.
  • You’d rather opt in to features you’ll actually use than have a wall of toggles enabled by default.

What might make a different tool the right choice

If any of the following are true, another option may serve you better — and that’s fine:

  • You want a complete CSS framework or design system bundled into Bricks.
  • You want a starter site or template kit you can import and customise.
  • You want a plugin that runs on the public-facing site (e.g. for animation effects or UI behaviours that need to ship to visitors).
  • You want a tool that makes opinionated choices for you out of the box, rather than one that defaults to off.

If you’re not sure which side of these you sit on, email brxprod-support@brxprod.com and tell me what you’re trying to do. If BRX Prod isn’t the right fit I’ll say so — saving us both time.

The honest part

I built BRX Prod for the way I work. The pillars (no frontend impact, productivity over framework, opt-in, framework-agnostic, visually distinct) reflect choices I’ll defend strongly — not because they’re universally right, but because they’re what makes the plugin internally coherent. If those pillars line up with how you want to work, you’ll probably get along with BRX Prod. If they actively conflict with your workflow, no amount of features will make up for the friction — and you should pick a different tool.