Live webinar · Craft&Crew in partnership with Webflow
Friday, November 13 · 12:00 PM ET
45 minutes · Live Q&A · Recording provided
What recent PHP vulnerabilities reveal about security, business continuity and the operational responsibilities of running enterprise websites on open-source infrastructure.
For enterprises running WordPress, Drupal and other PHP-based platforms, security involves far more than keeping software current. The infrastructure, the PHP runtime, the CMS, its extensions, the integrations and the response process all need a clear owner.
Join Craft&Crew, in partnership with Webflow, for a practical discussion of the business risks behind traditional CMS operating models, what to evaluate in your current stack, and how a managed platform changes who is responsible for security and maintenance.
The business question
When the next critical vulnerability lands, these are the questions your leadership team will ask.
The patch is rarely the expensive part. The coordination around it is.
What you’ll get
01
Dave Hale will showcase an enterprise that took its website offline as a precaution after the PHP vulnerabilities, and why the response reached the executive team.
02
Steve Lavigne will discuss PHP, infrastructure, CMS core, extensions and dependencies, and why tested response procedures matter as much as fast patching.
03
The operating model behind a self-managed website: who watches, who fixes, who decides on downtime and who tells the business. And what that costs to run.
04
Diego Rangel will discuss what Webflow Enterprise takes on, the controls it gives you, and the responsibilities that stay with your team.
05
Fit, integrations, compliance and keeping your search equity through cutover. And the cases where a traditional CMS is still the right call.
06
A practical checklist for reviewing ownership, dependencies and response readiness, whether you stay on your platform or move.
Bring your hardest questions about your stack.
We’ll leave time for live Q&A on fit, integrations, compliance, SEO and migration feasibility.
Shared responsibility
Every website runs on a shared-responsibility model. The question is where the lines sit.
On a self-managed CMS, your team or your vendors own almost every layer: the servers, the PHP runtime, CMS core, every extension, monitoring and the response when something breaks. Managed hosting moves some of that to your host.
A managed platform moves more of it. It doesn’t move all of it, and any honest evaluation starts by drawing the lines clearly.
Self-managed CMS → Webflow Enterprise
What stays with your team
Who has access, and what they can change
Integrations and third-party scripts
Site configuration and content
Compliance obligations
Your incident and communications plan
The goal isn’t to own nothing. It’s to own the right things, and know exactly what they are.
Why Webflow Enterprise
On Webflow Enterprise, there’s no server or PHP runtime for your team to patch. Webflow runs the hosting infrastructure, including security updates, and Enterprise adds single sign-on and role-based permissions for your editors.
That changes the work, not the need for governance. Your team still decides who has access, which integrations to connect and how to respond when something goes wrong. Diego will walk through exactly where those lines sit, including Webflow’s limitations.
Why listen to us?
Craft&Crew has delivered more than 700 enterprise web projects across Webflow, WordPress, Drupal, Craft CMS and custom platforms.
We’ve supported enterprise teams through vulnerabilities on self-managed stacks, and we’ve moved organizations to managed platforms when that was the better fit. As a Webflow Enterprise Premium Partner, we can speak to both sides of the decision.
700+
Enterprise web projects delivered
Premium
Webflow Enterprise Partner
Craft&Crew · Host
CEO
Dave is CEO of Craft&Crew, a Webflow Enterprise Premium Partner that has delivered 700+ enterprise web projects across Webflow, WordPress, Drupal, Craft CMS and custom platforms. He opens with a real enterprise response to the recent PHP vulnerabilities and hosts the conversation.
Craft&Crew
President & CTO
Steve is President & CTO of Craft&Crew and has spent decades in enterprise web architecture. He’ll walk through where risk sits across a self-managed CMS stack, and what a tested response looks like.
Webflow
Forward Deployed Engineer
Diego has been at Webflow for over four years. He started as its first Enterprise Technical Support agent, moved into Solutions Engineering, and is now a founding member of the Forward Deployed Engineering team, working hands-on with enterprise teams on Webflow Enterprise.
November 13 · Live
Spend 45 minutes on the risks behind your CMS operating model, and what it would take to change them.
Craft&Crew in partnership with Webflow
Friday, November 13 · 12:00 PM ET · 45 minutes · Live Q&A · Recording provided
Can’t join live? Register anyway and we’ll send you the recording.
