Figma Make gets a backend with Payload and brings design closer to real shipping

From a pretty idea to an app that pulls real data

The problem that held back product teams wasn't designing fast: it was what happened next. The design team would finish a prototype in Figma, engineering would start from scratch to build the database, authentication, and admin panel, and the so-called "handoff" became the cycle's real bottleneck. Figma's official release notes, published throughout October 2026, show Figma Make leaving behind its role as just that clickable showcase.

What Figma announced at Config India 2026

On October 15, 2026, during Config India 2026, Figma launched a package of features that changes what fits inside the editor before a single line of code leaves for an external repository. The center of the change is Payload, the backend framework that Make now scaffolds on its own inside the generated app.

The point that sums up the shift is in the feature's own description, in Figma's release notes:

Make now natively scaffolds a Payload backend, giving your app a CMS, database, media, APIs, auth, and an admin panel, turning a prototype into a production app.

Figma, official Release Notes, October 15, 2026

Figma hosts all of this alongside the design files, according to the note itself: data and design now live in the same place.

The design agent exited beta on October 6

Before the Config India package, Figma had already taken the canvas AI agent out of beta status, on October 6, 2026. The update brought lower latency and a way for the agent to find files scattered across the platform on its own.

• Guidelines in markdown files are now read by the agent on every prompt that uses the referenced library.
• It's possible to watch, live, a colleague's agent working on the canvas via the chat pile.
• The agent searches and references design files, FigJam sticky notes, and Figma Slides content from a single prompt.
• Figma nodes can be pasted directly into the prompt box as context.
• Generative plugins and custom skills exited beta alongside this, and custom skills reached the Starter plan.

Since that date, using the agent has consumed AI credits, which changes the cost calculation for anyone automating repetitive design tasks day to day.

Other pieces that close the loop

Two smaller updates, which still fit the same logic of reducing friction between design and code, shipped before Config India. On October 13, 2026, Gemini 4 Argon started running inside Figma Make's model selector, available on all plans, giving one more generative AI option for anyone already building in there.

On October 5, 2026, Figma enabled connecting multiple GitHub organizations to a single plan, currently restricted to Organization and Enterprise plans. For teams that keep code design systems in repositories split by product, this means the code sources feature mentioned above can see more than one source of truth without requiring everything to sit under a single organization.

What this changes in the flow between design and engineering

In short: the traditional handoff, where design hands off a mockup and engineering rebuilds it from scratch, stops being the only way out. With Payload scaffolded, code layers converting frames into code, and code sources pulling real components from a repository, an app with login, data, and an admin panel can be born and published inside Figma itself.

This doesn't remove engineering from the process, but it changes the point where engineering steps in. Instead of receiving a static Figma file and asking "how does this become a system?", the technical team now reviews an app that already runs, already persists data, and already has authentication, deciding what needs hardening before going into real production. The Config India product update's quote calls this a move from "prototype" to "production app," but it's worth noting that it is Figma, not an SRE team, that is defining what counts as production.

Where the math still doesn't add up

None of the October 2026 notes mention accessibility as a criterion for code layers or the Payload scaffold. That's a warning, not a detail: if the app is born ready to publish, accessibility needs to enter as a rule in the Guidelines file that feeds the agent, because there's no indication it comes guaranteed by default. Treating this as part of the definition of "done" remains the design team's job, even with a shorter pipeline.

It's also worth separating what's already stable from what's still experimental: code layers and Specs remain in open beta, code sources is in closed beta, and centralized design systems is preview-only, with no beta. The free code layers editing offer ends on November 4, 2026, close enough for anyone who wants to test it before the AI credit cost kicks in.

For teams with compliance requirements, security audits, or infrastructure that scales beyond what a Figma-hosted Payload backend supports, the path still runs through dedicated engineering reviewing, and possibly rebuilding, what came out of the editor. Shipping directly from Figma works well for an MVP, a proof of concept, or an internal app; for a critical product at scale, the release note makes no such promise, and it would be giving the announcement undue credit to think it does.