feega
all pages
alternatives: side by side
alternatives: situations
alternatives: alternatives to one tool
alternatives: alternatives for your coding agent
frameworks
editors
on this page
← All alternatives

The open-source, local Framer alternative for Claude Code users

By Andrea Buttarelli, founder of Feega · checked 2026-11-22 · how we checked

Keep Framer if designers own the site. If your landing page lives in a repo and Claude Code writes it, Framer would mean a second home for the page. Feega edits the repo directly, and Claude Code keeps working in it.

see it in action → The short version of this comparison, for Claude Code users.

The Feega editor with the Layers tree on the left, a running page in the middle and the Properties bar with a selected link on the right
The editor on a running page: Layers, the page itself and Properties, with the source file and line under the selection.

Framer, Claude Code and Feega at a glance

FramerFeega
Where the page livesIn a Framer project, hosted by FramerIn your repo, hosted wherever you host
Source filesNo code export or git sync on the pages we readYour own files, edited in place
Your coding agentClaude Code works in your repo; the tool wants its own copyReads the project, writes the code, loads the Feega skill
AgentsExternal Agents connect through MCP or a local CLI setupThey read the files Feega writes
PriceFree at $0, Basic $10 a month, Pro $30 a monthFree, Apache-2.0

Framer, Claude Code and Feega side by side

FramerClaude Code in your repoFeega
Where the code livesIn a Framer project, published to Framer hosting (Framer help: publishing and hosting)In your repoIn your repo
Pricing modelFree $0, Basic $10, Pro $30 a month, with AI credits (Framer pricing, 22 November 2026)Your Claude plan or API usageFree, Apache-2.0
Export and gitNot stated on the pages we readPlain gitPlain git; Feega never commits
Local or cloudCloud editor and hostingTerminal and editor (Claude Code: skills)Local, no account
Agent accessClaude Code connects through MCP or a local CLI (Framer help: AI and agents)Reads and writes your filesShows the selected element’s source
FitsDesigner-owned marketing sitesWriting and refactoring codeHand edits on code that exists

Framer wants the page inside Framer

On the pricing and help pages we read, Framer publishes the site to its own hosting. None of those pages mentions exporting the site as code or syncing it with git, so the Framer project stays the source of truth for the page.

That works until the landing page belongs to your product. Tokens, copy and components that also live in your app have to be copied across by hand each time one of them changes.

Page in a canvas
  1. Design in Framer
  2. Publish to Framer hosting
  3. Copy tokens by hand
  4. Repeat for each change
Page in your repo
  1. Open the repo
  2. Click the element
  3. Set the value
  4. Review the diff
Neutral illustration of the two paths.

A real edit, written to source

Here is what a hand edit leaves behind in src/lib/Hero.svelte. Feega writes at the line of the element you clicked, as a Tailwind class or a rule in your own CSS, and nothing else in the file moves.

Both tools take Claude Code as a partner, but only one leaves the page in your repo. The diff is the same one your agent will read on its next turn, and the same one git will show in review.

A call-to-action resized by hand after Claude Code wrote the landing page. The change is a CSS rule in the component.

Claude Code codes, you design, one set of files

Feega has no AI of its own. It sits next to Claude Code: Claude Code writes the component, you open the running page, click the element and set the padding or the type by hand. Both of you write to the same file, and git shows both as ordinary diffs.

Feega also reveals the selected element’s source in a text editor beside it, so Claude Code sees the line you picked. Right-click the element and choose Copy for agent to hand it the file, line, selector and preview width in one paste.

The Feega editor: the Layers tree on the left, a release monitoring landing page in the middle with its hero button selected, and the Properties bar on the right
The Feega editor: layers, the live page and the Properties bar.

when to choose which

choose Framer if

  • Designers publish the site themselves.
  • You want hosting and a CMS in one place.
  • The page shares no code with your app.

choose Feega if

  • Claude Code already writes your landing page in a repo.
  • You want the page to share components and tokens with the app.
  • You want every change as a diff, with no credits.

what each one costs

Framer’s free plan is $0 with 500 AI credits a month and a Framer domain. A custom domain needs Basic at $10 a month, and Pro is $30 a month, per its pricing page on 22 November 2026. Agents and other AI features spend credits.

Feega is free and open source under Apache-2.0, with no credits and no account. Hosting and your agent’s plan stay what they are today.

set up Claude Code once

Feega ships a skill for Claude Code. In Claude Code, install it as a plugin with /plugin install feega --marketplace andreabuttarelli/feega, or run npx skills add andreabuttarelli/feega in the project.

Per Anthropic’s docs, a skill is a SKILL.md file whose instructions load only when they are used, and a project skill lives in .claude/skills and can be committed. Facts that never change belong in CLAUDE.md, which Claude reads at the start of every session. The docs suggest keeping procedures in skills and facts in CLAUDE.md, so a good split is the skill for how, and one line in CLAUDE.md for the rule that class names stay literal.

The skill teaches Claude Code to add feega-source-map to a Next.js or Vite config, to start the editor with npx feega, and to write markup Feega can edit back.

moving a Framer landing page into a repo

None of the Framer pages we read describe a code export, so plan for a rebuild. Keep the Framer site live while you work. In your repo, ask Claude Code to build the page from the design, one section at a time, using your own components and tokens.

Once a section exists, open it in Feega and fine-tune spacing, type and colour by eye against the live Framer page. That is the part of a rebuild that eats the most prompts, and the part Feega does without a model.

If you would rather keep the page in Framer and still use Claude Code, Framer lists that as External Agents, connected through MCP or a local CLI setup. That is a different arrangement, and the page stays in Framer.

what to ask Claude Code, and what to do by hand

Ask Claude Code for the structural work: a new section, a form, a data loop, a refactor. Ask it to write the markup so Feega can edit it back. That means literal Tailwind classes, visible words in the markup and icons from the supported libraries.

Do the small visual passes yourself in Feega. Spacing, radius, colour and type size are quick to set by eye and slow to describe, and a hand edit costs no tokens. When you are done, tell Claude Code to read the diff, so that its next change starts from the page you shaped.

where Framer is still the better choice

Framer is built for people who design in a canvas and publish without a developer. Its paid plans add a CMS, staging, branching with previews and redirects, so designers can ship on their own.

Feega has no CMS, no publishing and no hosting. If the people changing the page never open a repo, Framer fits them better.

more on Framer and your agent

This page covers Claude Code. The wider comparison is on Framer alternatives. Other agents with the same question:

Feega is free. Download it or read the agents page in the docs.

Claude Code can drive Framer, and that is a different job

Framer help: AI and agents says Framer MCP connects tools like Claude to your projects so they can create pages, edit content and manage CMS collections, and it describes a local CLI setup as an alternative. Framer developers lists Claude Code, Codex and Cursor as external agents that update a Framer project.

In both cases the output lands in Framer. If your landing page is a Svelte, Next.js or Vue file in the same repo as the app, that route adds a second home for it. The better question is whether the page should live in the repo at all. If yes, the Framer overview explains what changes.

The Changes tab of the Feega editor on a home goods shop after one edit: one file changed, a border-radius of 12px with Show diff and Revert buttons
The Changes tab after one edit: the file touched, with Show diff and Revert.

moving the page: a checklist for Claude Code

None of the Framer pages we read describe a code export, so treat the move as a rebuild. Keep the Framer site live and ask Claude Code to build each section from a screenshot and the copy. Give it your tokens first, from your own stylesheet, so the new page uses real variables instead of copied hex values.

Per Claude Code: memory and CLAUDE.md, put the rule in CLAUDE.md that class names stay literal on elements people will tweak. When the section exists, open it in Feega and fix the spacing and type by eye, then check Changes. Framer’s own Framer help: publishing and hosting page describes a reverse proxy for putting a Framer site behind your host, which is a way to keep the old page up during the move.

Try Feega in two minutes: run npx feega in your project folder, or install the extension.

Download Feega →

what you give up when you leave the canvas

Framer’s paid plans add a CMS, hosting locations and staging per Framer pricing. Feega has none of those, and neither does Claude Code. A repo-based page needs your own hosting, your own CMS choice or Markdown files, and your own review step.

What you gain is one codebase, one history and an agent that sees all of it. The Properties docs list the values you can set by hand, and the pricing page shows that Feega itself stays free.

The agent guide lists every command and what each agent can see.

Read the agent docs →

try Feega with Claude Code in five steps

  1. Install the skillRun /plugin install feega --marketplace andreabuttarelli/feega in Claude Code, or npx skills add andreabuttarelli/feega in the project.
  2. Ask for setupSay “set this project up for Feega”. Claude Code adds the source map where the framework needs it.
  3. Open the pageSay “start Feega”, or run npx feega in the app folder. The running page opens next to your layers.
  4. Click and setPick the element and change its values in the Properties bar. Copy for agent hands the element to Claude Code when you want it to take over.
  5. Review togetherRead the diff in Changes, then let Claude Code carry on from the new files. Commit with your own identity.

mistakes people make

Moving a site that designers still publish weekly. A repo takes publishing away from them. Move the page only where changes already happen in code.

Letting the agent write class names through cn() on every element. Feega refuses expressions it cannot trace to one line. Keep literal strings on the elements people tweak.

Describing a two-second drag to the agent. Spend the tokens on code, and set the spacing by hand.

questions

What does Framer cost?

The free plan is $0. Basic is $10 a month and Pro is $30 a month, with AI credits and caps on pages and bandwidth.

How do I install the Feega skill in Claude Code?

Run /plugin install feega --marketplace andreabuttarelli/feega, or npx skills add andreabuttarelli/feega in the project.

Does Claude Code see what I select in Feega?

Feega reveals the selected element’s source beside it, and Claude Code is one of the agents that read the editor selection per the Feega docs.

Does Feega use Claude Code’s tokens?

No. Feega has no model behind it and sends nothing anywhere.

Does Feega replace Claude Code?

No. Claude Code writes code and Feega sets visual values in the same files.

how we checked

We make Feega, so read our column with that in mind. We read each product's public pages on 2026-11-22 and compared what they offer, not finished work. Something wrong? Write to hi@feega.app.

  1. Framer pricing
  2. Framer developers
  3. Framer help: AI and agents
  4. Claude Code: skills
  5. Claude Code: memory and CLAUDE.md
  6. Feega docs: use Feega with AI agents
  7. Framer help: publishing and hosting

Feega is not affiliated with, endorsed by, sponsored by or connected to any company or product named on this page. All product names, logos and trademarks belong to their respective owners and are used only to identify those products. Information comes from their public pages on the date shown and may have changed since; check the source before you decide. This page is not legal, financial or purchasing advice.

Keep Framer for a site designers own. Keep Claude Code and the repo for a page your product shares.

download for free →