Figma Make Now Builds the Database Too. That’s Three Builders in a Month.

TL;DR: On 15 October Figma put Payload inside Figma Make. Prompt an app now and it also sets up a database, file storage, user login and an admin panel. That makes Figma the third major builder in a month to absorb the backend — the part that actually breaks vibe-coded apps. A no code backend is genuinely the right direction. Two asterisks: hosting is a free beta with pricing “to be announced”, and most of what Figma shipped this week is for design teams, not solo builders.

What Figma actually shipped

Figma announced on 15 October that Payload — an open-source headless CMS and application framework it acquired in 2025 — is now integrated into Figma Make.

The line that matters: prompting an app in Figma Make also sets up its backend. A database. File storage. User login. An admin panel. You describe the thing; the plumbing arrives with it. That is a no code backend, delivered alongside the interface it serves.

It’s written up by James Mikrut, who is both a product manager at Figma and Payload’s CEO, and the examples are deliberately ordinary: a delivery service site that takes driver applications, a newsletter signup that sends confirmation emails, event listings, an IBM designer’s internal sites that his own team updates. You can upload a CSV and it becomes a collection.

Availability: “Payload is available on all plans, with access rolling out to all accounts over the coming weeks.” So your no code backend may not have arrived yet.

Why a no code backend is the whole game

If you’ve built anything with an AI tool, you already know the shape of this problem. The front end is the easy part. The thing that falls over is everything behind it — where the data lives, who’s allowed to read it, how someone logs in, how you change a price without redeploying.

We’ve written that story from three directions this quarter. In September, Lovable bought the part of your app that breaks. Days later we found 16,326 apps leaking their users’ data through one unticked setting on a database nobody had configured. The pattern is consistent: people can build the app; they can’t safely run the bit underneath it. A no code backend is the industry’s answer to that gap.

So a no code backend arriving as part of the prompt is the right instinct. The question is never whether you can get a database — it’s whether you understand what you’ve got.

Three builders, one month

Worth stepping back, because this is now a trend rather than a product launch:

When	Who	What they absorbed
22 September	Lovable	Bought Sutro — the backend
25 September	Replit	Bought Atta — analysis and charts over your data
15 October	Figma	Shipped Payload inside Make — database, storage, login, admin

Every one of these is the same bet on the no code backend: the builder that owns it owns the customer, because that’s where the app stops being a demo. If you’re choosing a tool this year, that convergence matters more than which one writes nicer components.

The two asterisks

The hosting is free because it isn’t priced yet. Figma’s own wording: “The hosting infrastructure for Payload-backed Figma Make projects is currently in beta and free to use.” The company says it will announce pricing and packaging before they take effect, which is the right way to do it — but a free beta is not a cost you’ve planned for. Build accordingly.

The other launch has a date on it. Figma also moved code layers into open beta on 15 October — real, running code living on the canvas next to your design, which you can prompt, edit directly, or push to a branch as a pull request. It consumes AI credits, and creating and editing is free on paid plans only until 4 November 2026. After that it comes out of your credit allowance.

Kris Murphy of Checkout.com, quoted by Figma, calls code layers “a proper bridge between design and development”. That’s a fair description — and it’s also Figma answering a question we covered from the other side in July, when Replit Design arrived promising to kill the Figma handoff. Figma’s reply is essentially: the code lives here now.

What this isn’t

Most of what Figma announced this week is not for you if you’re a solo builder, and it’s worth saying so plainly.

TechCrunch’s write-up of the full Config India slate covers Specs (a Markdown editor where teams define their design language), design context (libraries and guidelines that agents consult to stay on brand), wider access to the agent on canvas, and more than 20 new MCP tools. Those are design-system features for organisations with design systems. If you’re one person building one product, they’re noise.

Figma’s chief design officer Loredana Crisan gave the framing: “There are 17-times more lines of code being produced today than in the past”, much of it “built to discover what the product is” rather than to ship. That’s an accurate description of what our readers do all day — and it’s the reason the backend question keeps coming back, because discovery code becomes production code the moment something works.

How to approach it

1. Check whether you actually have it. Payload access is rolling out over weeks. If Figma Make isn’t offering a backend yet, that’s why.
2. Build something small and real — a signup that stores entries, an event list you can edit. The value of a no code backend shows up the second you need to change data without rebuilding.
3. Open the admin panel and look at what’s in it. This is the step people skip, and it is the only one that makes a no code backend safe. Know what’s stored, who can see it, and what happens if the wrong person gets a login.
4. Don’t put anything on free beta hosting that you’d be upset to move. Pricing is coming. Keep an export path.
5. If you only use Figma for pictures, note the 4 November date before deciding whether code layers is worth your credits.

Who should care (and who shouldn’t)

• Already building in Figma Make: this is the significant one. Your prompts now produce something with a no code backend attached.
• Building in Lovable, Replit or Bolt: nothing changes today, but the direction is now unmistakable across three tools. Worth factoring into a switching decision, not panicking over.
• Working with a designer, or you are one: code layers and Specs are a genuine workflow change. The handoff is dissolving from both ends.
• Running a business on a vibe-coded app already: step 3 is the one for you, today, whichever tool you use.
• Not using Figma at all: the table is the takeaway. The builders are racing to own the backend, and that is where your data will end up living.

Our take

We think the backend convergence is the most important thing happening in this category, and it’s being reported as a series of unrelated product launches.

Three tools in under a month have moved to own the layer where data, identity and permissions live. A no code backend is good for non-developers in the obvious way — you get a working database without learning what a migration is — and it quietly raises the stakes in a way nobody is advertising. The easier the backend is to create, the less likely anyone is to look at it. That is exactly how 16,326 apps ended up publicly readable.

On Figma specifically: cautiously positive. As a no code backend it is a real, open-source project with a real CMS behind it rather than a thin wrapper, and “available on all plans” is a more generous line than most of its competitors have drawn. We’d use it for a content-backed site tomorrow.

We would not yet run a business on the free hosting beta. Not because we expect Figma to behave badly — it has said it will announce pricing before it takes effect — but because “free, pricing to come” is a position, not a plan, and you want an export route before you need one.

And the thing we’d genuinely watch is whether any of these three ship a default that’s safe rather than merely convenient. A no code backend that arrives with sensible permissions already set would be worth more to this audience than any number of new components.

Not sure which builder fits what you’re making? Take the 60-second Vibe Coding Tool Finder quiz →

FAQ