Figma Make began as a way to turn a prompt into a working prototype. Since May 2026 it can also open a real codebase and send changes back as pull requests. That second part is still a closed beta: access is by waitlist, it runs only on a Mac, and the work happens on your own machine.
If your team needs to change a product that already exists, and Make isn’t available to you yet or doesn’t fit how you work, this guide covers seven alternatives. They are grouped by who on your team does the work, because that decides most of the choice.
Where Figma Make stands with an existing codebase
Start with what it does. In the beta, Make connects to a Git repository and opens your running app. You change the UI in three ways: adjust properties in a panel, annotate elements on the screen, or describe the change in chat. Each change is saved as a commit, and you can open a pull request without leaving Figma. Figma describes it as designed for UI changes to existing screens.
Figma’s documentation also lists the limits that matter if you want to rely on it today:
- Access is by waitlist. It rolls out by organization, in batches, and joining the waitlist doesn’t guarantee a place. Figma hasn’t given a date for general availability.
- Mac only. It runs in the Figma Beta desktop app for Mac. Windows support is planned.
- It runs on your machine. Make clones the repository to your computer and starts your app’s dev server there. Each repository needs a one-time setup by an engineer before designers and PMs can use it.
- GitHub is the only fully supported provider. GitLab and Bitbucket connect through SSH, and you open the pull request in the provider’s own interface. GitHub Enterprise Server isn’t supported.
- Pricing hasn’t been announced. The codebase features are free during the closed beta.
These are the limits of an early beta, and Figma says it is working on them. They matter if you need something your whole team can use this quarter.
What to look for in an alternative
If your goal is to change a product that already exists, five things matter more than how fast a tool produces a first screen:
- It works in your real repository, on your Git provider. If it builds somewhere else, someone has to port the result.
- It uses your real components and design tokens. Generic components stand out next to the rest of your app.
- It shows the change in your running product. The real test of a change is how it looks inside your product.
- Your engineers receive a pull request. They review it like any other change, and nothing merges without them.
- It fits the person doing the work. Tools for engineers assume an editor, a terminal and a local setup. If the work starts with a PM or a designer, pick a tool built for them.
The 7 best Figma Make alternatives for an existing codebase
1. Cursor
Best for: engineers, and designers who are comfortable working inside a code editor.
Cursor is an AI code editor. Its built-in browser has a visual editor: you can drag elements to rearrange a layout, inspect a component’s props, adjust styles using your own color tokens, or click an element and describe the change. The agent then updates the underlying code.
Watch out for: it is a code editor first. Someone needs the project open and running in Cursor, so it suits people who already work in the codebase. If the person with the idea is a PM, Cursor speeds up the engineer who receives the handoff, and the handoff itself stays.
2. AutonomyAI Studio
Best for: PMs and designers who need to change a product that already exists, without setting up a development environment.
AutonomyAI Studio works inside your production codebase and already knows your components, tokens and patterns. In Design Mode you point at an element in the live product and edit it. You can also describe a change in plain language, or bring design context from a Figma file through the Figma plugin.
Each task runs in its own isolated cloud sandbox. Studio renders the change in your running app and checks the result before it opens a pull request, and your engineers approve every merge. Studio connects to GitHub, GitLab, Bitbucket and Azure DevOps. Pricing is per task, so you pay for the work done, whatever the size of the team. More than 170 product teams use it.
Watch out for: it is built for changing an existing product. If you are starting a new app from a blank page, a greenfield builder is the better fit.
3. Builder.io Fusion
Best for: product, design and engineering teams that want a visual workspace connected to their repository.
Fusion is Builder.io’s AI development product. Its documentation says it connects to a GitHub, GitLab, Azure DevOps or Bitbucket repository, learns your design system from the repositories you connect, and delivers every change as a pull request. Designers and product owners can propose changes without writing code.
Watch out for: pricing is per user, with a monthly allowance of AI credits on each seat and extra credits sold separately. Work out the cost for the number of PMs and designers you want to include.
4. Claude Code
Best for: engineers who prefer to hand an agent a task and review what comes back.
Claude Code is Anthropic’s coding agent. It reads your codebase, edits files across the project, runs commands, creates branches and opens pull requests. It runs in the terminal, in IDE extensions, in a desktop app and in the browser.
Watch out for: it assumes the person driving it can read and judge code.
5. v0 by Vercel
Best for: teams on Vercel that want to generate and iterate on UI quickly.
v0 can import an existing GitHub repository. It starts from the branch you choose, pushes its changes to a separate working branch, and publishes through a pull request.
Watch out for: an imported repository is connected to a Vercel project. If your product deploys somewhere else, test how previews and publishing fit your pipeline before you commit to it.
6. Lovable
Best for: new apps and early ideas.
Lovable turns a prompt into a working app with a live preview, and syncs the code to GitHub.
Watch out for: it can’t connect to a repository you already have. Lovable’s documentation says Git sync “always creates a new repository.” To start from existing code, you download it as a ZIP and import it into a new project. We cover this in more detail in 8 Lovable alternatives for teams with an existing codebase.
7. Bolt.new
Best for: going from an idea to a working app or site by chatting.
Bolt.new builds apps and websites from a prompt. You can import an existing GitHub repository.
Watch out for: the imported project is linked to the repository’s main branch, and Bolt pushes all changes there. You can’t switch the project to another branch, which doesn’t fit teams that review work in feature branches.
Side-by-side
| Tool | Works with your existing repo | Built for | Best fit |
|---|---|---|---|
| Figma Make | Yes, in closed beta. Mac only, runs locally, GitHub fully supported | Designers and PMs, after an engineer sets up the repository | UI changes to existing screens, for teams admitted to the beta |
| Cursor | Yes | Engineers and technical designers | Visual and code edits inside an editor |
| AutonomyAI Studio | Yes. GitHub, GitLab, Bitbucket and Azure DevOps | PMs and designers | Product and design changes to an existing product |
| Builder.io Fusion | Yes. GitHub, GitLab, Azure DevOps and Bitbucket | Product, design and engineering teams | A visual workspace connected to the repository |
| Claude Code | Yes | Engineers | Delegating multi-step coding tasks |
| v0 | Yes, via GitHub import | Teams on Vercel | Fast UI on Vercel |
| Lovable | No. Git sync creates a new repository; existing code comes in by ZIP import | Anyone | New apps and early ideas |
| Bolt.new | Imports as a project on the main branch only | Anyone | New apps and sites by chat |
Product details are from each company’s website and documentation, checked November 20, 2026. These products change quickly, so check current documentation before you decide.
How to choose
- You’re in the Make beta, on a Mac, with a GitHub repository and an engineer to set it up. Try it. It’s free during the beta.
- Your engineers want to go faster. Give them Cursor or Claude Code.
- You’re starting something new. Use a greenfield builder like Lovable or Bolt.new. That is what they do best.
- Your PMs and designers need to change the product you already have, on whichever Git provider you use. That is the job AutonomyAI Studio was built for. See how teams use it to improve existing features, or compare it with other approaches.
To see it on your own codebase, book 20 minutes and we’ll run a real change on yours.
Frequently asked questions
Can Figma Make work with an existing codebase?
Yes, in a closed beta that began on May 28, 2026. Make connects to a Git repository, opens your running app, and can open a pull request with your changes. Access is by waitlist and rolls out by organization.
Does Figma Make’s codebase feature work on Windows?
No. During the closed beta it runs only in the Figma Beta desktop app for Mac. Figma says Windows support is planned.
Does Figma Make support GitLab and Bitbucket?
Partly. GitHub is fully supported, including pull requests. GitLab and Bitbucket connect through SSH: you can clone a repository and push branches, and you open the pull request in the provider’s own interface. GitHub Enterprise Server isn’t supported.
How much does Figma Make cost for codebase work?
The codebase features are free during the closed beta. Figma hasn’t announced pricing for the open beta or general availability.
Which Figma Make alternative is built for product managers and designers?
AutonomyAI Studio and Builder.io Fusion are both built for people who don’t write code and both deliver changes to an existing repository as pull requests. Cursor and Claude Code are built for engineers. Lovable and Bolt.new are built for starting new apps.


