Kevin Geary Threatened to Pull Automatic.css From Bricks Over a Dispute. Today's Licence Wouldn't Stop Him.
Automatic.css runs on Bricks at the discretion of a company that sells a competing builder. If you build on Bricks with ACSS, your client sites depend on that discretion.
Kevin Geary threatened to pull Automatic.css, or ACSS, from the Bricks page builder unless Bricks reversed his ban within three weeks. ACSS is a CSS framework for WordPress page builders.
The reason wasn’t a technical one. Bricks had removed him from its Facebook community.
I’ve seen the post. He put it in his own community.
Who that lands on
Say you build on Bricks with ACSS. Your spacing, colours and type come from its variables and classes, on every client site you’ve built that way.
Then the man who controls ACSS posts about pulling it from your builder, over a fight you weren’t part of.
Your client sites. Your maintenance contracts. Your maintenance problem, had he gone through with it.
And Bricks isn’t the flagship. Digital Gravy, the company behind ACSS, sells a competing builder called Etch for WordPress. The ACSS docs list “Etch (Flagship Integration)” first.
Frames users are stuck in the same spot. Its pricing page answers “Do I need Automatic.css to use Frames?” with “Yes”.
The dispute
On 19 February 2026, Bricks founder Thomas Ehrig posted a “Quick moderation update” in the Bricks Community group on Facebook. There’s also a Reddit thread about it.
He wrote that Geary “was removed from the Bricks Community on Feb 15, 2026, due to a long-running pattern of disruptive, belittling, and hostile interactions toward other members.”
Then he got to ACSS: “Kevin then shared a post in his own community, threatening Bricks to reverse his ban within three weeks or he would stop supporting Bricks in ACSS.”
Ehrig said that reached Bricks only “through screenshots from worried users”. His view: “Tying product support to moderation decisions is not an acceptable way to handle this.” He added that Geary’s “public stance appears to have changed”.
He also disputed a “no warning / no email” claim. He said he emailed Geary on 31 December 2025, and that Geary replied to that email on 17 February 2026.
The reasons for the ban are Ehrig’s account, and I haven’t seen the comments he means. The post I saw, about pulling ACSS from Bricks, is another matter.
Nothing in today’s licence stops him
The ACSS licence agreement, last updated on 13 August 2026, says releasing updates is “at the sole discretion of Digital Gravy, LLC”. I found no clause guaranteeing compatibility with any builder. That version is dated after the dispute, and I couldn’t find the one in force in February.
About eight months after the February ban, ACSS still lists Bricks as supported, and I can’t find a notice ending that support. He didn’t pull it.
But you found out what your stack rests on: one man’s mood and “sole discretion”.
If you run ACSS on Bricks
When ACSS 4.0 dropped Oxygen and Breakdance, two other page builders, Digital Gravy promised in writing that existing sites would stay on ACSS 3.x, with “critical bug fixes and security updates for the next 5 years”. That covers Bricks sites too, and the same post lists Bricks as still supported in 4.0.
What isn’t in writing is how long that lasts, or how much notice you’d get before it ends. Ask Digital Gravy for both. Then build one site without ACSS, so you know what leaving costs.