Prefer English?
Prefer English? Switch the website language for a better experience.
Announced on September 2, 2026 at Webflow Conf by Ben Haefele, Webflow's CPO, Source is an agentic platform that connects your codebase and your entire martech stack in a shared workspace between AI agents and visual developers. It is currently in a limited research preview, accessible only by application via webflow.com/source.
The idea behind Source is not to replace the Designer or the visual Webflow editor you already know. It is to give AI agents governed access to production code, so they can carry out concrete tasks — audit, content, brand, review — without every intervention requiring a full human round trip. Webflow structures this access around six dedicated Views: Audit, Agents, CMS, Inbox, Review and Brand. Every role in your organization gets an interface built for them, rather than a single generic dashboard.
The difference boils down to one sentence: Cursor and Copilot require an engineering workflow — cloning the repo, branching, pull request, code review — whereas Source gives agents direct access to the production environment, backed by native governance.
In practice, a Copilot agent proposes a change that someone then has to review, test, and merge. That is an excellent tool, but it assumes a technical team well versed in the git cycle. Source flips the logic: permissions, brand system compliance and audit trail are built into the platform itself, not bolted on afterward by your team. The agent operates within a framework already shaped by your brand rules and access rights.
This architecture changes the nature of the risk. The question is no longer "will AI break my code" but "is the governance I have configured the right one". And correctly setting up permissions, a brand system an agent can actually work with, and a readable audit trail is not something you improvise on a Friday afternoon.
| Criteria | Cursor / Copilot | Source by Webflow |
|---|---|---|
| Code access | Via local clone, dedicated branch | Direct, in the production environment |
| Required workflow | Git, pull request, human review | Built-in governance (permissions, audit trail) |
| Interface | Single, developer-oriented | Six role-based Views (Audit, Agents, CMS, Inbox, Review, Brand) |
| Team prerequisites | Technical team well versed in the git cycle | Business-side configuration + expert supervision |
Because the promise of Source — autonomous agents inside your production environment — only holds value if the governance behind it is thought through from day one. A poorly calibrated Audit View generates noise you cannot act on. A Brand View with no structured brand system upstream leaves an agent inventing rules on your behalf. And an audit trail nobody reviews serves only to ease someone's conscience, not to secure a project.
Webflow itself spells this out explicitly in its positioning for agencies: Source is a chance to turn agency know-how into a sellable product, through custom Views per client, to take on more technical projects than before, and to become the AI consultant clients are already asking for. This is not a tool you open alone on a Tuesday morning hoping to figure it out. It is a shift in posture that calls for a partner who has already practiced agentic automation, not just read the documentation.
At Mazette.co, we are not approaching Source as some theoretical novelty we are discovering alongside our clients. We have already built our own agentic pipeline in-house: a system that writes, translates, illustrates and publishes Webflow content automatically, with strict governance rules on what the agent can decide on its own and what always gets escalated for human validation.
This is not a minor detail. It is the difference between an agency that will read the Source documentation at the same time as you, and an agency that has already settled the hard questions: where to draw the line between agent autonomy and human oversight, how to structure a brand system so it stays legible to an AI, how to build an audit trail that actually serves someone rather than just ticking a compliance box. We made these calls on our own production before ever proposing them to a client.
An AI agent without governance thought through in advance is not a time saver — it is a risk pushed further down the road, usually surfacing at the worst possible moment.
In practice, our support is built around three areas, adapted to how mature your project is and to the gradual rollout of the research preview.
This is a natural extension of what we already document on the topic of brand AI visibility, notably in our article on Webflow AEO Analytics now covering Claude and Gemini. Source and AEO respond to the same underlying shift: AI is becoming a full-fledged actor in both the production and the discovery of web content, and you need a strategy for both sides of that equation.
{{webflow}}
We are not going to sell you a dream: Source is in a limited research preview, access has to be earned through an application, and nobody today has six months of hands-on experience with this tool. Any agency claiming otherwise is either lying or exaggerating.
What we can say with confidence, however, is that the underlying logic — AI agents with direct access to production code, governed by built-in oversight rather than a classic git cycle — matches exactly what we already practice in-house with our automated editorial pipeline. We have scars, we have rules that exist because we watched an agent do something we had not anticipated and had to fix. It is that kind of experience, not a reading of a press release, that makes the difference between solid guidance on Source and a risky test run.
Our conviction: clients who apply early for Source and get guidance from an agency already fluent in agentic governance will have a real operational head start by the end of 2026, once the preview opens up more broadly. Better not to discover the pitfalls once the competition has already solved them.
{{seo-aeo}}
If you are applying for the Source research preview, or if you simply want to understand what this platform would concretely change for your Webflow site, let us talk about it. We can frame your use case together, structure governance upfront, and help you avoid the mistakes we have already made and fixed internally. Contact Mazette.co to discuss it, or first explore our full approach to Webflow expertise and our method.
Code
Over 120 companies have already stepped out of the shadows with us.
You can apply directly at webflow.com/source. Access is currently limited to the research preview, with Webflow gradually selecting organizations and partner agencies based on their use case.
No, these are different approaches rather than direct competitors. Cursor and Copilot fit into a traditional engineering workflow with git and code review, while Source gives agents direct access to the production environment with built-in governance, making it more suited to product and marketing teams than developers alone.
Because the value of Source depends entirely on the governance set up beforehand: permissions, brand system, audit trail. An agency that has already experimented with agentic automation in production, like Mazette.co with its own editorial pipeline, avoids the calibration mistakes that make these tools ineffective or risky without expert supervision.
Impactful titles, polished meta descriptions, sitemaps, Schema.org, Hn structure, and audits: these are the SEO foundations that make your content readable by both Google AND generative AI. We cover both simultaneously.
With over 180 clients, our agency is one of the few in France to hold the Webflow Premium Partner label, supporting you in every area, including custom web design, sophisticated automation, conversion optimization, and SEO and GEO visibility.
We create bespoke web designs focused on performance, user journeys, and conversion. Join over 180 clients who have trusted us to elevate their brand.
