weweb.io

(YC W21) is an AI-powered no-code web-app builder that helps you build production-grade applications 100x faster with no vendor lock-in.

[weweb.io @weweb_io]

Introducing WeWeb Unify: a brand new, full-stack version of WeWeb ✨

With WeWeb Unify, you can now combine AI & a drag-and-drop editor to design your interface, manage data, build backend logic, and publish production apps. All in one platform.

We'd love to hear what you think 👇

[weweb.io @weweb_io]

⏰ Monday updates. Daily digests. Monthly cleanups.

Scheduled tasks are here in WeWeb 🥳
No extra automation tool needed.

Here’s how to set up your first cron job 👇

[weweb.io @weweb_io]

cron jobs are coming to WeWeb
time to make a list 👀

[weweb.io @weweb_io]

A picture is worth a thousand words.
Or at least one very long prompt 🖼️

Have a reference in mind? Show WeWeb AI instead of trying to put it all into words.

Drag an image, PDF, or text file straight into the chat 👇

[weweb.io @weweb_io]

Me: connects WeWeb MCP
Claude:

[weweb.io @weweb_io]

vibe coded an internal tool?

before IT says "absolutely not", you just have to
- click every button
- fill every form
- log in as every role
- uncover data & acess leaks
- retest after every prompt

...or let WeWeb AI run the tests
show IT the receipts

[weweb.io @weweb_io]

Vibe coding is fun..

But what about vibe TESTING? 👀

Now WeWeb AI can QA your app in preview.

> Clicks through your app
> Fills in and submits forms
> Tests different flows

Just like a real user would.

Watch it test. Stop it anytime. Take over whenever you want.

Here’s WeWeb AI testing a task planning app 👇

[weweb.io @weweb_io]

@googledrive & @googledocs are live in WeWeb 🚀

Pull in Drive files. Create and update Docs. All from your WeWeb workflows.

Big shoutout to Aneeq for shipping this one 🔥 And yep, he’s already working on more Google integrations...

Which Google integration are you waiting for? Comment below and let Aneeq know 👇

[weweb.io @weweb_io]

@HubSpot fans, we have news 👀
You can now connect HubSpot natively to WeWeb!

✨ And yes, WeWeb AI can build with your HubSpot data too.

Give it a brief and start building the dashboards, portals, and internal tools your team needs:

[weweb.io @weweb_io]

Now do more with @Stripe in WeWeb. A lot more 💳

Sell a subscription → send an invoice → issue a refund → build a billing dashboard... and more!

Try it out and tell us what's still missing 👀

Here’s what you could do before vs. what you can do now 👇

[weweb.io @weweb_io]

coming soon 👀

[weweb.io @weweb_io]

Prompts tell AI what to do.
Taste is knowing when to say NO 🚫

Now you can protect the parts of your WeWeb project AI shouldn’t change:
Pages, workflows, components, tables, APIs, variables, and more 🔒

Set your AI guardrails today:

[jp trinh @jptrinhh]

I was experimenting with self-hosting a fullstack WeWeb app: Cloudflare for the frontend and Coolify on a Hetzner server for the backend.

It works great (https://t.co/RRYcBuPjjD). So i wanted to push it further and it sparked an idea: a map of places I go to that are worth documenting.

This is the current starting point, an Airbnb-style layout and my MapLibre component. It's a place where I'll break things and design something personal!

[weweb.io @weweb_io]

ICYMI, we launched our @mondaydotcom integration last week 🎉

So this Monday, beat the blues. Build instead.
Build that client portal. Automate that team workflow.

✨ Connect monday to WeWeb → Ask AI to build on top of your boards:

[weweb.io @weweb_io]

🚨 New Stripe update: bring your customer data into your WeWeb apps.

No more giving your whole team access to the Stripe dashboard:

[Raphael Goldsztejn @raphgoldz]

Everyone talks about powering the next billion builders.
But will the next billion build like the last million coders?

Most of them won’t be coders.
Yet we keep putting them inside coding environments designed for agents + developers.

Then, when what they build becomes a black box, we blame AI.
Or worse, we blame the citizen developer.

That’s backwards.

[ICONIC @the_icon_x]

new yap session on YouTube
stress testing the @weweb_io backend by building a community app with it. just seeing how far I can actually push it
https://t.co/MXOeXyippM

[weweb.io @weweb_io]

Full guide → https://t.co/qyG3rPXOjF

🤖 Pro tip: Give this checklist to your AI coding agent and ask: “Audit my app against every item and generate a security report with what passes, what fails, and what I should fix.”

[weweb.io @weweb_io]

👨‍💻 Vibe coding your app? Before you ship it, run this security checklist:

🔐 AUTH & ACCESS
Test like a hacker.

☐ Create two test users. Copy one user's read request as cURL, replay it in Postman with the other user's record ID. Do you get their data?

☐ Replay the same request as an update. Does their record change?

☐ Replay it as a delete action. Is their record gone?

☐ As a normal user, call an admin or privileged endpoint directly. Does the backend reject you?

☐ Change fields like `role`, `owner_id`, `user_id` or `workspace_id` in a request. Can you give yourself access you shouldn’t have?

☐ Sign out completely. Replay a write request with the authorization header removed. Does the backend accept it?

🗄️ DATA & SECRETS
Consider it public until you test it.

☐ Open DevTools → Network and reload every sensitive page. Do any responses contain records or fields the current user shouldn’t receive?

☐ Inspect request headers, payloads, frontend bundles and browser storage. Can you find any private API key, service credential or secret?

☐ Are you storing sensitive data you don’t actually need?

🧹 INPUT & INTEGRATIONS
Never trust user input.

☐ Replay a request without using the UI. Send missing fields, extra fields, invalid values and oversized input. Does the backend reject them safely?

☐ Upload an invalid or oversized file. Does the backend enforce the same rules as the frontend?

☐ Make a third-party integration fail or timeout in staging. Does your workflow fail safely without leaking internal details?

🚦 ABUSE PROTECTION
Never assume the user “won’t find out".

☐ Repeat a harmless action several times in staging. Do login, AI, email, upload and export actions eventually hit an appropriate limit?

☐ Retry an action that should only happen once. Can it accidentally send two emails, create two payments or run twice?

🔎 LOGGING & RETESTING
No app is 100% secure. Keep testing.

☐ Trigger a failed login or denied request. Can you find the event in your backend logs without passwords, tokens or secrets being logged?

☐ Change a role, workflow or data model, then rerun the permission tests. Do the same security rules still hold?

💡 And one worth remembering:

Hiding a button, field or page in the frontend is UX.
It is NOT security.

Save this before your next launch. 🔖

[weweb.io @weweb_io]

💬 @WhatsApp 🤝 WeWeb

Natively connect your WhatsApp Business account to WeWeb. Send and receive messages directly from your workflows.

Build support flows, order updates, automated reminders, and more. No middleware needed.

✨ Ask AI to build your first WhatsApp automation: