WR - Webflow + React

In 2023, Webflow released Devlink, a framework for doing realtime exports of Designer layouts into an external React development environment.

In 2025, Webflow announced Webflow Cloud, which offers an integrated hosting setup to host and integrate your apps directly into your Webflow site.

For React developers, this is a great way to get Webflow-level designer support in their React projects.

What is Devlink?

https://webflow.com/devlink

https://docs.developers.webflow.com/docs/devlink-documentation-and-usage-guide

Webflow + React give you the UX layer. For business logic, data processing and database support, you'd extend that. Here are some popular approaches.

What is Webflow Cloud?

Announced May 2025, Webflow Cloud establishes a path for developers to host your Devlink-built app as part of your Webflow-hosted site, under a folder path like /app.

This gives you a path to maintain branding between your site and your app, and to continue that branding and SEO all the way directly into your branded site.

• https://www.mysite.com would be your main Webflow site, CMS, ECom functionality, localized pages, etc.
• https://www.mysite.com/app or another path you choose would be your custom app hosted as part of your site.

While I have not yet accessed the BETA, I think it's likely that you could host anything you want under those custom app paths, and that you could host multiple.
However the intended dynamic here appears to be to use Devlink to build your site with the HTML+CSS controlled in the designer, and then deploy it directly as part of a larger site.

It's unclear at this point whether Webflow Cloud offers deeper integration into the Webflow ecosystem, such as;

• The ability to provide routing services for redirection and rewriting of Webflow paths site-wide.
• A direct form of access to the CMS that supports querying and batch updates, without API rate limit issues.
• The ability to open up Webflow.js for events and element control.

React Stacks

MERN Stack

1. MongoDB: A NoSQL database.
2. Express.js: A web application framework for Node.js.
3. React: For building user interfaces.
4. Node.js: A JavaScript runtime environment for server-side code.

JAMstack

1. JavaScript: For handling all dynamic programming during the request/response cycle.
2. APIs: For all server-side functions.
3. Markup: For structuring the content.
4. Often, React is used as the JavaScript library to build the frontend, along with static site generators like Gatsby or Next.js.

Full-Stack React with TypeScript

1. Using React for the front-end.
2. Node.js and Express.js for the backend, often with TypeScript for type safety and enhanced developer experience.
3. A variety of databases can be used, like PostgreSQL, MySQL, or MongoDB.

React with GraphQL

1. React for the frontend.
2. GraphQL as a query language for APIs, often with Apollo Client for state management in React.
3. Backend could be Node.js with Express.js, or other backend solutions that support GraphQL.

React with Firebase

1. React for building the frontend.
2. Firebase for backend services like authentication, real-time database, hosting, and storage.

React with Next.js

1. React for building user interfaces.
2. Next.js as a React framework for server-side rendering, static site generation, and building web applications with an emphasis on performance and SEO.

React with Serverless Architecture

1. React for the frontend.
2. Serverless functions (like AWS Lambda, Azure Functions) for backend logic.
3. Integrating with various cloud services for databases, authentication, etc.