You’re holding six client sites on retainers. One of them calls at 9pm because the homepage is broken. Who fixes it — you, the client’s marketing hire, or a vendor’s support queue? That question is what the Webflow Source vs Framer vs Astro decision really comes down to for a freelancer.
Webflow‘s Source workspace gives marketing teams and AI agents shared, governed access to a site’s code — the company’s biggest move yet past visual website building, according to CMSWire’s coverage of the launch. That’s not just a feature announcement. It’s a question about where your client sites live next year, and who can touch the code once they’re live.
What Webflow Source actually changes
Source is pitched at marketing teams, not at the solo builder. The pitch is that marketers and agents work from the same governed codebase instead of waiting on a developer or a designer to ship a change.
Read that from a freelancer’s chair and the implication is plain. The platform is optimizing for teams that want to edit the site without you. That’s not a betrayal — it’s a business model. But it does change what you’re selling when you hand over a Webflow build.
We’ve already written about what the Source pivot means for agencies holding client sites, and about how the plan stack is costed in 2026. This piece is the narrower one: you, one client site, and three ways to keep it online.
Webflow Source vs Framer vs Astro: the three paths
There’s no single winner here. There’s a winner per client.
| Path | What you’re buying | Best for | The catch |
|---|---|---|---|
| Webflow | A visual builder plus hosting, with the platform now steering toward agentic, code-level editing | Clients who want to edit copy and layout themselves without touching a repo | You’re renting the platform. Pricing and plan structure are the vendor’s call, and the roadmap is aimed at marketing teams |
| Framer | A design-first site builder with hosting attached | Portfolio-style and marketing sites where the visual result is the product | Hosting is bundled per site, so confirm current plan pricing before you commit to several client sites at once |
| Astro | A framework you own, deployed to a host you choose | Clients whose site is mostly content and who won’t need a visual editor | You’re now the maintainer. Framework upgrades are your problem, not a vendor’s |
Notice what the table doesn’t say: any of these is cheap. It says who absorbs the maintenance when something changes.
Where Astro actually stands right now
Astro‘s own release notes are the useful counterweight to the Webflow story, because they show what “you own the code” costs in practice. Astro 7.3 adds an --ignore-lock flag to astro preview, so you can run more than one preview server at once — useful when you’re running Playwright tests. It also passes Astro‘s runtime logger into custom image services and cache providers, so their warnings respect your logging setup instead of writing straight to the console.
That’s the trade in miniature. Astro 7.1 added the same escape hatch to astro dev; 7.2 added a lockfile to astro preview without it; 7.3 closed the gap. Small, specific fixes, shipped on a framework’s schedule, landing in your lap to apply.
If you’ve never run a Playwright suite against a client site, that release note means nothing to you — and that’s the honest signal that Astro isn’t your path for that client.
What hosting actually costs you
Astro’s own blog is a running record of the deployment side. The September 2026 roundup leads with a migration story — Evil Martians moving from Gatsby to Astro in nine days without rewriting a single React component — plus the Astro Germany meetup and a Starlight 0.42 release.
Deploy targets matter more than the framework for a freelancer’s margin. Cloudflare Pages lists unlimited sites, seats, requests and bandwidth across all plans, with HTTP/3, QUIC, image compression and SSL included, and GitHub integration with built-in builds. For a freelancer running six small client sites, “unlimited sites” on the host is the line that decides whether the stack is viable.
Compare that to per-site hosting on a visual builder and the arithmetic is worth checking yourself. One client site on a builder plan is one thing; six is a subscription stack you have to explain to each client — so confirm current plan pricing before you commit.
The decision rule
Run each client site through these three questions before you pick a path:
- Will the client edit the site themselves? If yes, a visual builder earns its subscription. If no, you’re paying for an editor nobody opens.
- Is the site mostly content? Content-heavy sites are where a framework plus a static host stops being overkill.
- Who fixes it at 9pm? On Webflow or Framer, you escalate to a vendor. On Astro, you are the vendor.
That third question is the one freelancers skip, and it’s the one that decides whether the cheap-looking option is actually cheap.
What to do this month
Don’t migrate anything because Webflow announced Source. Migrate when a specific client site fails one of the three questions above.
If you’re holding a Webflow site for a client who now wants their marketing team editing copy directly, Source is aimed squarely at them — and your role shifts from builder to maintainer. Price that shift into the retainer before you renew.
If you’re holding three Framer sites for clients who never open the editor, that’s the stack to audit first. And if you’re already comfortable in a terminal, Astro 7.3’s release notes show what you’re signing up for: you get control, and you get the upgrade work.
The pivot isn’t the story. What you charge to live with it is.
Sources
- CMSWire: Webflow Launches Source Agentic Workspace for Marketers
- Astro 7.3 release notes
- What’s new in Astro — September 2026
- Cloudflare Pages plans
122 ready-to-use AI prompts — organised by discipline and category, each copyable in one click, free and no sign-up needed. Browse the prompt library →