Cloud design software company Figma is officially transforming its AI design assistant, Figma Make, from a prototyping sandbox into a live, visual software editor that connects seamlessly to the production codebase.
Announced today, the update allows product managers, designers, and non-technical builders to import existing Git repositories directly into the Figma desktop app, visually edit the application’s underlying code via Canvas, and push those changes back to engineering via standard GitHub pull requests.
Engineering Governance and Licensing
Importantly for enterprise deployments, this integration does not bypass established engineering guardrails. Figma Make operates entirely within a standard version control workflow.
The platform serves as a local development environment where design changes are deposited according to local commits.
When a designer is ready to ship, they spawn a branch and open a pull request (PR) directly from Figma Make.
From an enterprise governance perspective, this means that visual AI edits are subject to the same continuous integration pipelines, security checks, and code reviews as any traditional engineering commitment.
Figma Make is a proprietary commercial service that’s available for full seats on Figma’s paid plans – ranging from $16 per month for professional teams to $90 per month for enterprise deployments – but it interfaces cleanly with open-source and proprietary Git repositories without imposing new licensing restrictions on the generated code.
Breaking the One-Way Barrier
When Figma Make originally launched a year ago in May 2025, it successfully bridged the gap between static wireframes and interactive prototyping, but it was structurally isolated from the real-world software lifecycle.
It operated on a rigid, one-way push mechanism: users could export AI-generated projects to a brand new GitHub repository, but at the time, Figma Make could do that. No Receive upstream changes or sync with the existing codebase.
Today’s update fundamentally changes that architecture: by enabling connections to any Git provider, builders no longer have to maintain parallel, out-of-sync environments.
Teams can connect a production or sandbox repository, highlight specific UI elements, and use natural language or contextual annotations to inspire Figma’s multi-model AI—which toggles between Anthropic’s Cloud 3.6 Sonnet, Cloud Opus, and Google’s Gemini models—to write the underlying code.
The agent dynamically reads the surrounding code architecture, applies visual edits, and anchors the generated code to the team’s existing design system guidelines.
Competitive landscape: Figma Make vs Lovable vs Cloud Design
As code generation becomes commoditized by larger language models, competition for ownership over the visualization layer of software development has split into different approaches.
Figma Make is no longer just competing with other design canvases; It’s full-stack coping "vibe coding" Platforms like Lovable and LLM-native environments like Anthropic’s Cloud Design, which just launched last month. Each platform targets a fundamentally different user and purpose:
- Figma Make (Design-First System): Operating at $16 to $90 per month for full seats, Figma Make caters to established product teams that prioritize brand loyalty. This design system wins on compliance, automatically pulling from existing color tokens, typography rules, component variants, and auto-layout structures. It’s built for teams that want deep, layer-based canvas manipulation while keeping code ownership strictly within their existing GitHub architecture. Figma Make also integrates with SupaBase to provide a backend environment that provides latent storage, computation, and a Postgres database. And new capabilities take Figma Make beyond most vibe coding platforms. Users can work locally against the repo from which their team commits changes, which actually get merged, rather than generating code that engineers have to rebuild against the actual repo. Even if a user doesn’t have an existing codebase or design to draw from, they can use Figma Make to quickly create functional applications.
-
Lovable (Code-First Production): Priced at $25 per month for Pro and $50 per month for Business tiers, Lovable serves as a standalone, full-stack application builder. Unlike Figma Make, Lovable relies on a native backend architecture (often paired with a database like SupaBase) and a slider-driven UI styling approach. It implements a strict automatic two-way sync with GitHub, treats the repository as the final source of truth, and is optimized for single developers or small startup teams who want to launch production-ready SaaS apps from scratch without maintaining bulky vector design files.
-
Cloud Design (AI-Native Prototyping): Anthropic’s built-in canvas environment is accessible to users on a Cloud Pro ($20 per month) or Max ($100-$200 per month) subscription. Despite lacking the granular vector control of Figma Make or the full-stack database integration of Lovable, Cloud Design is ideal for product managers and engineers who need to create quick, functional UI prototypes and instantly hand them off to coding agents like Cloud Code. However, heavily iterative design sprints can quickly burn through Anthropic’s strict token limitations, making it less viable as a primary design hub.
to navigate "vibe coding" Era
The emergence of two-way repo synchronization makes the reality of the enterprise clear "vibe coding" ERA: The primary hurdle in product development is shifting from raw engineering bandwidth to architectural governance and design intent. Technology leaders navigating this fast-moving landscape should take a look at the early marketing hype to understand who will benefit from this new paradigm.
Figma Make is not a general-purpose, standalone application builder; Instead, it is a highly specialized frontend optimization tool designed explicitly for established, mid-to-large cross-functional product teams.
figma It’s clearly noted in their documentation that designers who already have access rights to their company’s existing corporate codebase are currently best suited for this functionality. As a result, enterprise leaders should consider adopting Figma Make if they have a mature engineering organization with a well-defined design system, rigid repository guardrails, and a desire to unlock faster iteration cycles. This directly addresses the technical friction felt by the 45% of designers and 59% of product managers who already contribute code on a regular basis but prefer to work from a visual canvas rather than a command-line terminal. By turning Canvas into a local development environment, it allows these non-technical builders to execute visual layouts, typography tweaks, and color changes independently, removing tedious frontend implementation from core engineers.
In contrast, organizations or teams launching a zero-to-one Skunkworks project, or single developers building lightweight SaaS products from scratch will find far better utility in a code-first, full-stack platform lovable. Because Lovable seamlessly orchestrates backend logic and database integration like SupaBase, it excels at rapidly spinning up functional applications without the need for pre-existing vector infrastructure or legacy codebases.
Meanwhile, individual product managers or software engineers wanting rapid, text-prompt-driven UI wireframing without rigid design system constraints are better served by Immediacy Cloud Design.
For enterprise leaders wary of over-committing capital or locking their custom builds into a proprietary AI backend, the wisest path forward is compartmentalization. Figma Make’s reliance on the standard Git workflow – relying on local commits, isolated branches, and mandatory engineering pull request reviews – means it enforces the same security and code quality standards required for enterprise maintainability. By choosing Figma Make as a targeted frontend bridge for existing systems, and using platforms like Lovable for external, greenfield prototyping, leaders can safely adopt productive new AI tooling without risking their core architectural integrity.
Why does Figma need to continue innovating?
Figma completed its initial public offering on July 31, 2025, pricing its shares at $33, after the deal was oversubscribed 40 times following heavy institutional demand. The stock immediately soared 250% to an intraday high of $115.50 on its first trading day.
However, in the following months, Figma’s stock (NYSE: FIG) experienced a severe correction, falling 81% from its peak by May 2026 to trade around the $21 to $22 range, well below its initial IPO price.
The collapse reduced its market capitalization to approximately $11.3 billion. Financial analysts attribute this aggressive rerating to structural IPO pricing mechanics, low float and widespread "software apocalypse," Because investors are increasingly shifting capital out of traditional SaaS products and into AI-native workflows.
Figma’s current state is an existential risk. As enterprises increasingly shift their software spend toward generic AI models and native coding agents like Cloud Design, Cloud Code, and OpenAI Codex, traditional "vanilla" Cloud design software looks increasingly commoditized.
Figma Make represents the company’s important counter-attack in this era "Vibe coding." To regain its premium valuation, Figma will have to prove to Wall Street that its platform is not just a static vector canvas that AI tools can easily bypass, but an indispensable, live orchestration layer where human intent, enterprise design systems, and AI-generated production code are seamlessly integrated.
With the new Figma Make two-way GitHub integration and governance, the company is on its way to showing skeptics that it has a way forward in AI-powered. "vibe coding" Development era.
<a href