Webiny Enterprise CMS+ ⚡️

How well does your CMS handle scale? Are you locked in to an expensive SAAS product that doesn't allow you the freedom to customize it around your business? Introducing Webiny. The Enterprise open-source CMS made for scale and control. youtube.com/watch?v=-KWwVt…

Real-time updates in the admin app used to mean wiring up your own Websockets layer. ⚡ In Webiny 6.4, that’s built in — just import the Websockets service into any custom API route, list active connections, and send messages. Screenshot shows a broadcast notification route — message goes out to every connected admin in just a few lines. Notifications, live updates, collaborative features — all easier to build now.

We’ve been quietly modernizing our internal dev toolchain, and with @rspack_dev’s rslib now replacing babel for Webiny package builds, the migration is finally done! rsbuild took over from webpack. @OxcProject’s oxlint from eslint and oxfmt from prettier. And now rslib from babel. Faster builds, fewer dependencies, way less config to maintain. The pipeline finally feels like one coherent thing instead of a stack of tools glued together over the years. 🙂

External apps can now talk to Webiny Background Tasks directly. 🔥 With the new Tasks module in v6.3, you can list task definitions and runs, pull execution logs, trigger new tasks, and abort running ones — all from outside Webiny. Full TypeScript declarations are included in the SDK playground, so you get autocomplete and type checking out of the box. Learn more in the SDK reference 👉 webiny.com/docs/reference…

After years of experience building various forms for ourselves and our clients, we’ve finally built our own form library which gives us full control over the data model, the rendering, the functionality. Conditional rules, computed values, conditional sync/async validation, extension via plugins - Webiny now has it all! And it’s fully programmatic. React is just the UI layer. The brain of the form is pure Javascript. The video demonstrates focusing of invalid field buried deep in tabs, and collapsed accordions. When your form has hundreds of fields scattered across tabs, this is a must have.

Uploading images to your File Manager? Webiny’s first AI Power-Up has you covered. 🔥 Auto-generated tags. Auto-generated descriptions. Zero manual work. Drop in an image — get back rich metadata, ready to filter, search, and reuse across your content. AI Image Enrichment — now live in v6.3. Your media library, smarter by default. 🚀

Webiny 6.3.0 is now available! 🚀 This release introduces AI PowerUps, rolling out first for paid plans. Connect OpenAI or Anthropic in your Admin settings and use natural language prompts to generate page content in the Website Builder. Images uploaded to the File Manager are also automatically enriched with AI-generated tags and descriptions, making your media library more searchable without extra manual work. For developers, there's a new declarative FormModel API for building admin UI forms — the same system now powering Page Settings internally. The SDK gains a tasks module for interacting with Background Tasks from external applications, and input validation across all SDK methods now catches common mistakes before they hit the network. We'd love to hear how these features work for you in your projects! Changelog: webiny.com/docs/release-n… Upgrade guide: webiny.com/docs/release-n…

DID YOU KNOW Webiny has a built-in background tasks system? 🚀 Long-running jobs — reports, imports, AI pipelines, batch processing — don’t belong in a request/response cycle. Define a task. Webiny handles the rest. ⚡ Built-in support for: • Aborting mid-run ⛔ • Multi-step iterations 🔄 • Input typing & validation ✅ • Status tracking out of the box 📊 No extra infra. No queues to wire up. No workers to manage. Just your logic, running in the background. 🔥 See how it works → webiny.com/docs/backgroun…

New Chapter on Learn Webiny Course :book: — Building with AI Agents and Webiny MCP Server. Webiny ships with a built-in MCP server. One command (`npx webiny-mcp configure {agent}`) and your AI coding agent stops guessing about Webiny — it loads the right skill, follows your project's patterns, ships code that fits. It's the recommended way to build with Webiny going forward.

v6.3 is almost here. ☕ Shipping next week — and this one’s loaded. The headliner: AI Power-Ups. Generate page content with natural language prompts (bring your own provider, define your personas). Plus AI Image Enrichment — every image you upload gets tagged and described automatically. And there’s plenty more in the box. 🚀 More details soon. 👀

With every new feature we ship, we auto-add a Webiny skill for it. Ship a feature → ship a skill. 🚀 And Webiny agent skills keep getting better over time, which means smarter prompts + sharper results. 🧠 Your agent grows with the platform.

AI Power-Ups are in the works. 🔬 Plug in your provider, drop in an API key, pick your model — and Webiny gets a brain. We’re cooking. Hold tight. 👨‍🍳 More soon!

Small addition, big DX win. 🚀 Coming in v6.3: `Infra.Env.IsProd` and `Infra.Env.IsNotProd`. Before, if you wanted something to run only in production-like envs, you had to list each one out manually — prod, staging, and so on. Easy to forget one. Easy to drift out of sync. Now, since you already declare your production environments once via `Infra.ProductionEnvironments`, you can just wrap things in `IsProd` (or `IsNotProd`) and let Webiny figure out the rest. One source of truth. Cleaner code. Less room for mistakes.

Last week, we swapped ESLint for oxlint (@OxcProject) in our monorepo. 1m 14s → 1s for static code analysis. 💥 Wait… 1 second?! That can’t be right. Must be a broken config, right? Maybe our ESLint setup wasn’t perfectly tuned? 🤔 Could be. But still: 10,130 files linted in 544ms using 4 threads with 20 rules. 0 warnings. 0 errors. Tested it. It really works. Now we have lighting-fast linting in our CI. ⚡

Following up on yesterday’s Dev Tools permissions post. 🫵 We didn’t just add a single on/off toggle for Dev Tools access. We went granular. Each playground gets its own Access Scope: 🔵 `GraphQL Playground` → Full access / No access 🔵 `SDK Playground` → Full access / No access So you can give a role full access to the `GraphQL Playground`, but lock down the `SDK Playground` entirely. Or vice versa. Or neither. Or both. Mix and match per role. 🎯 Fine-grained permissions, right where you need them. 🚀

Been rethinking the sidebar a bit. 🤔 Previously, hitting “Support” popped open a dropdown with... everything. GraphQL Playground, SDK Playground, Configure Next.js, Documentation, GitHub, Slack — all lumped together behind one vague label. Functional? Sure. Intuitive? Not really. So we reorganized: 🔧 `Dev Tools` → GraphQL & SDK Playgrounds now live here 🌐 `Website Builder` → Configure Next.js moved in (where it belongs) 🧹 Documentation, GitHub, Slack → removed (already on the dashboard) No more mystery dropdown. Each thing lives where you’d expect to find it. But we’re still iterating — wdyt? Better? Worse? Would you organize it differently? 👀

Adding a new API HTTP route in Webiny used to take a couple of plugins. In v6? A single `` in `webiny.config.tsx` — method, path, and a pointer to your implementation. That’s the whole setup. 🔥 Your route logic lives in its own file. Clean class, `execute` method, return a reply. Config on one side. Implementation on the other. Nothing in between. 🚀

While building out the new infra, we quickly ran into a need for a proper encryption service — so we built one. 🔐 In v6.3, we’ll be adding an `Encryption` module that follows the same pattern as our other services — injectable anywhere in your app via Webiny’s DI system. Need to encrypt something inside a route, a hook, a plugin? Just declare the dependency and you’re good to go.

We swapped Prettier for oxfmt (@OxcProject) in our monorepo. 41 seconds → 7 seconds for code formatting checks. 🚀 Same output. 6x faster CI. 10,860 files formatted in under 6 seconds using 4 threads. 🤯

One of our plans is to introduce AI integrations into Webiny — we’re calling them AI Powerups. We’re starting where we always start: the infrastructure. Step one was adding an `Ai` interface into Webiny’s DI system so it can be used anywhere in your app — an HTTP route, a lifecycle hook, a background task. The screenshot is just one example of what that looks like in practice. More updates as this takes shape. 👀

With the upcoming v6.2.0, we ask you to set up the MCP server right during project creation. Pick your AI agent, and Webiny configures everything automatically — config files, instructions, ready to go. No extra setup steps. You start building with AI from minute one. ⚡