Optimizely Frontend Hosting Beta – Early Thoughts and Key Questions

Optimizely has opened the waitlist for its new Frontend Hosting capability. I’m part of the beta programme, but my invite isn’t due until May, while I haven’t had hands-on access yet, I’ve already been digging into what I’ll be looking for once it lands.

Sign up for the beta

What is Frontend Hosting?

This new offering is designed to simplify how frontend apps are deployed and managed alongside Optimizely CMS. It’s available as an add-on to both CMS SaaS and PaaS, and brings together:

• Hosting for headless frontend applications

• A built-in delivery network

• Web Application Firewall (WAF)

• Managed services for build, deploy and performance

This could offer a tighter, more integrated experience for those already using a headless CMS setup.

If you’re after background on other frontend hosting options, I covered related topics in these earlier blog posts:

• Frontend Hosting for SaaS CMS

• Self-hosting the Presentation Layer with Coolify

What I’ll Be Exploring in the Beta

Environment & Compatibility

• Will it work cleanly across CMS SaaS and CMS PaaS?

• What frameworks will be supported out of the box (e.g. Next.js, Astro)?

• Will it handle different build strategies?

  • Static

  • Dynamic

  • Incremental builds

• Are serverless functions on the roadmap (Lambda, Edge functions)?

• Is there a CDN and WAF already in place?

• Are preview environments supported (e.g. URLs for pull requests)?

Developer Experience

• Any limits around build minutes, concurrent builds?

• Built-in CI/CD or integrations with GitHub/GitLab?

• How is secret management handled? (Environment Variables) 

• What kind of logging and observability is available?

• Will it help surface key metrics (e.g. Core Web Vitals, SEO signals)?

• Can I get alerts if a deploy fails or performance drops?

Access & Security

• Can access be restricted (IP allow lists, password protection)?

• Is traffic control through WAF configurable?

• Can we apply rate limits?

Commercial Considerations

• How will pricing work?

  • Bandwidth

  • Seats

  • Execution time for serverless

• Multi-project or multi-site support — all under one roof?

Why It’s Interesting

For teams running hybrid headless setups, this could remove a fair bit of friction. No need to spin up hosting separately or stitch things together manually, this could mean fewer moving parts, more predictable deployment workflows, and a clearer support model.

And being Optimizely-native, it should also mean closer alignment with the rest of the platform ecosystem.

Discovery & Early Access

I was part of an early discovery interview with the team last year, which gave me a first look at the thinking behind this product. Here’s part of the follow-up I received:

"As you may recall, you participated in a discovery interview with us about CMS frontend hosting last year. Your feedback back then was extremely helpful! I wanted to let you know that we are now in a beta testing phase of frontend hosting!"

I’ve also some early preview screenshots from the discovery. I’ll include a few of those in this post to give a sense of what might be coming.

Note: The screenshots shown here are from early design mockups shared during the initial discovery phase. The UI and features in the current beta release may differ significantly as the product has continued to evolve.

Get Involved

Optimizely is actively inviting feedback to help shape this feature before full release. If this looks like something you’d want to test, you can still register via the waitlist.

Register for the beta

I’ll post more as soon as I’m hands-on in May — including walkthroughs, findings, and observations from real use cases.

Stay tuned.