WeWeb is full-stack 🚀

[Joyce]

Hey there

We’re very proud to announce WeWeb Unify is live

WeWeb Unify Gives You Full Stack Freedom (No Trade-offs)

Here’s what’s new:
• A redesigned editor, now live in all your projects
• A new tab to manage data, backend logic & integrations
• A native WeWeb backend that you can mix & match with Xano, Supabase, Airtable, Google Sheets, and more

A redesigned editor, built for full-stack apps

We’ve rebuilt the editor around three tabs: Interface, Data & API, and Settings.
The goal: help you build full-stack apps in one place with more clarity, more control, and less friction.

Interface is where you design your apps. Everything you’re used to is there: pages, components, styling, frontend logic. Your existing Plugins and Collections live here too, exactly as you left them.

Data & API is new. This is where the new native WeWeb backend lives, alongside any external data sources and integrations you want to manage from here.

Settings is project configuration: monitoring, environment variables, and project-level controls.

Your existing setup stays intact
Your existing Plugins & Collections continue to work exactly as before, now inside the Interface tab:

You can move things into the new Data & API tab whenever you want, or not at all.

What is new: you now have access to native tables and backend workflows if you choose to use them.

Native WeWeb Backend

We’ve introduced a built-in backend, fully integrated into WeWeb.

In Tables , you’ll find the data layer: a spreadsheet-like interface on top of a production-grade Postgres engine that scales:

In Backend Workflows , you’ll find all your server-side logic: API endpoints and reusable functions:

You can now:
• Define database schemas
• Create tables
• Fetch external data
• Save filtered views
• Generate API endpoints
• Build reusable server-side functions
• And more…

All visually, without leaving the WeWeb editor.

The idea is that you can focus on building while we handle scaling, maintenance, and infrastructure for you.

A few things to know:

• Works with all data sources. Connect & manage external data.
• Choose your server location. Deploy in the US, Europe, or Asia.
• Flexible file storage. Use WeWeb storage or AWS S3 (more providers coming).
• Connect multiple data sources to a single project. Combine WeWeb tables and external backends in one unified view.
• Leverage AI to build faster. Prompt AI to build tables and backend workflows for you.

Learn more about how to create and manage tables, views, users, and API endpoints in the new WeWeb interface.

New & improved integrations

We’re doubling down on integrations to help you build serious products without having to worry about infrastructure or complexity.

• Airtable: now easier to work with at scale.
• Google Sheets: now supports editing records.
• Email: added Resend and Sendgrid integrations.
• Media & storage: added Cloudinary and AWS S3 integrations.
• Auth: 30+ SSO providers out of the box (Google, Apple, GitHub, Slack, and more).
• More integrations coming soon…

Learn more about how you can leverage all the new and improved integrations.

Open any project to see the new editor: your existing setup is in Interface; Data & API is ready when you are

A note on AI

We’ve rebuilt our AI from the ground up and the new version is out today in Alpha.

You can now build both your front-end and back-end with AI. Just pick a mode and let it do the work.

This new version is only slightly better than what we had before at this stage but:

1. it lays the foundations for a fully agentic AI that is much much better.
2. now that this release is out, we will be back to shipping improvements weekly, so autonomy will ramp up fast

Ok, that’s it for now… We hope you enjoy these updates!

As always, if there’s anything we can help you with, please don’t hesitate to reach out

PS: if you notice any bugs or have improvement suggestions, please let us know here! Like I said, now that WeWeb Unify is out, we’ll be going back to weekly releases

[Widefiree (Bellie)]

When are we see variable aliasing and theme modes?

[Joyce]

Hey @Widefiree

@Widefiree

When are we see variable aliasing and theme modes?

Regarding theme modes, do you mean the ability to have a design system that has color tokens for both a light theme and dark theme or did you have something else in mind?

Regarding variable aliasing, could you clarify the use cases you have in mind?

[Widefiree (Bellie)]

Regarding theme modes:

I’m thinking a bit beyond just light and dark. Ideally, the system should support both theme modes (light/dark) and different brand styles (like blue or purple). So each brand would have its own light and dark version for example, blue-light, blue-dark, purple-light, and purple-dark all powered by the same set of semantic tokens. That way, we can switch between themes or brands easily without touching the components themselves.

Regarding variable aliasing:

I mean setting up tokens so they reference other tokens instead of hard coding values. For instance, a semantic token like color-brand would point to something like blue-500 or purple-500 depending on the active theme. This makes the system more flexible and easier to maintain as things evolve.

[Joyce]

Got it! I’ll create the feedback ticket

Not sure if/how we can prioritize this but I know the team has plans to improve the design system greatly in the coming months so I’m sure they’ll want to explore these ideas further.

[jefeOliveira]

Woah… didnt expected to storage to be so small even at higher plans? Seriously i can run a cloudflare R2 for way more data than that and cheaper

Excited to test it out!

[wealthsyndy]

What is the best way to report bugs/issues. I was having weird issues with loops and variable updates. And I have no idea how the new data settings are supposed to work with Xano metadata, as Weweb keeps telling me my api key is wrong, even though my built api connections are working fine.

[Yaj]

Any chance the old filters for logs can be put back in to the debug logs. I love the new logs btw, they are better in every way than the old logs, but being able to filter by errors etc was such a good feature with the old logs, I used it personally all the time. Would be great if this functionality could be added back in.

Also this new position for preview is already getting really annoying, if you move to the preview button to click while in edit mode and accidently hover over the undo button the dropdown stays over the preview and if you’re moving to quick will accidently click undo, since the preview button is under the dropdown it doesn’t go away until you move away. Very annoying design.

Another thing I was playing around with creating a new table on the new Data & API tab and created a supabase connection which I didn’t finish cause I didn’t realise we needed a new plan. But now I’ve got duplicate Supabase actions and no obvious way about how to disconnect this connection?

In case anyone done what I had done above and tried to connect the backend to the new Data tab. You can go to the bottom tab on the nav bar for Integration to disconnect the backend integration otherwise you’ll get duplicate backend workflow actions.

[RPAL]

100% agree with you on all points. A toggle style button should not move locations when it is clicked. The simple solution would be not to hide the top menu bar when preview is clicked.

It’d be nice to have an option to hide a lot of these features if we only want WeWeb for front end. Like can I get rid of this table views thing?

[RandyG0322 (Randy)]

Have there been any reported issue with login in editor mode? I am having an issue that started after the update where when I login with a user in editor mode it hits my invalid email/password error. This only is happening in the editor as when I log into my live app with the same user credentials, the login completes just fine. Its seems something has changed and there appears to be a bug with the authentication process/login process in the editor mode. I cant get any of my collections to load in editor mode because of this as its not fetching the authenticated user.

There is also something wrong with this form. I can not click the continue button. I was also curious if I have the xano auth plugin already installed do I have to do this? What is the difference?

[Yaj]

This is actually the wrong place to do your auth. Its confusing but this is for the new plans with the backend support. You need to find plugins on the sidebar to edit the old auth plugin.

[Joyce]

Hey there

@wealthsyndy

What is the best way to report bugs/issues.

For bugs, the best way is to create a bug ticket here.

For issues or things that look like a bug but you’re unsure, I’d recommend chatting with support directly:

@wealthsyndy

I have no idea how the new data settings are supposed to work with Xano metadata, as Weweb keeps telling me my api key is wrong, even though my built api connections are working fine.

All your “old” / existing data settings are in the Interface tab:

We didn’t migrate anything to the “Data & API” tab because we didn’t want to impose the change on you and risk breaking production apps.

Sharing an excerpt from another thread to try to make things a bit clearer:

Does that help?

[Joyce]

@RandyG0322

I was also curious if I have the xano auth plugin already installed do I have to do this? What is the difference?

Hey Randy

If you have the Xano Auth plugin already installed, you don’t have to do this.

All your existing settings can be found in the Interface tab.

More about this here: WeWeb is full-stack 🚀 - #13 by Joyce

@RandyG0322

Have there been any reported issue with login in editor mode?

I haven’t seen anything come through regarding this but if you find an issue, please don’t hesitate to create a ticket here or open a support chat to discuss 1:1 with the team.

[Yaj]

Keen to hear if we can get the debug log filters back, at least just a basic version would be perfect. Preview button I can live with, but I feel like I’ve lost a best friend with the debug filters.

[Raphael (Raphael Goldsztejn (WeWeb CEO))]

hey @jefeOliveira, are you talking about file storage or DB storage?

[javierlaborde]

New version broke the connection with my self-hosted Supabase instance… I cannot make it work and the new integration does not offer (or I don’t understand how to) connect to a self-hosted instance… Quite confusing and frustrating

[javierlaborde]

@Raphael @Joyce @Matthew_S I will appreciate any help with this. I’ve been all morning trying to reconnect, I’ve removed the “old” plugin and reinstall it, nothing but “Invalid Supabase configuration” messages.

UPDATE: If anybody else is struggling with this, I was able to solve it by adding the new editor url to the whitelist of my self-hosted instance. ⚠️ ACTION REQUIRED: Update Your WeWeb URLs to Avoid Disruptions

Thanks @Joyce for your time and guidance!

[Joyce]

Hey @javierlaborde

Could you open the support chat and share the issue with the team on there so we can take a look at your project specifically?

[Corner (App)]

Hi, congrats for the new release, it will take some time to get used to it but that’s interesting. Only issue here is that when I login, I can’t see the user I’m logged in with. It stays on “Not connected” (although I checked on the profile page and I’m actually connected, the user name and linked info are displayed).

I’ve also added the supabase auth plugin.

Did I miss something ?

Thanks in advance !

[Mael]

Hi @Corner,

You will see the information that you are connected only if you are using the new integration. If you use the old plugin, it won’t display here even if you are logged in. We will release soon a small UI fix to hide this part if you have an auth plugin so it will no more be confusing