@raphgoldzi
iAccount based inFrance
About this account
- Account based in
- France
- Connected via
- France App Store
Account-level information from X, not a live location or the device used for a specific post.
Pinned Tweet
We just released WeWeb 3.0 (Beta) and put AI at the core of our no-code builder. ๐คโค๏ธโ๐ฅ
This AI can generate entire web pages in an environment non-programmers can trust and control; it is a revolution and I am very excited for you to try it!
Read on ๐
we are shipping new integrations like crazy. This week's is @HubSpot!
Raphael Goldsztejn retweeted
WeWeb.io: The best AI app builder for non-coders with big ideas by @joycekettering, @raphgoldz, @, and more producthunt.com/products/wewโฆ
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 ๐
no strings attached with @weweb_io!
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 (accommodations-map.jptrinh.cโฆ). 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!
New WeWeb integration just dropped!
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:
I updated my signature pad component I made for @weweb_io
Instead of showcasing it as a simple white box I wanted to do something a bit different. So I built a photo annotation tool on top of it. Users can take a picture, draw on it and the annotation is saved onto the image.
The toolbar, colors, stroke and logic can be adapted to match your worfklows and design.
๐บ Full demo and breakthrough on Youtube in the comments!
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.
They need a different building environment.
You shouldnโt need to understand every line of code.
But you SHOULD understand your app.
โ What data it touches
โ What workflows run
โ What the AI can change
And you SHOULD be able to step in when you need to.
๐ฅ๐ฒ๐๐ถ๐ฒ๐ ๐ถ๐.
๐๐ต๐ฎ๐ป๐ด๐ฒ ๐ถ๐.
๐๐ฒ๐ฒ๐ฝ ๐ฏ๐๐ถ๐น๐ฑ๐ถ๐ป๐ด.
Thatโs a big part of the bet weโre making with @weweb_io
---
Some customer love that makes us think weโre onto something:
โ๐๐ฉ๐ฆ ๐ท๐ช๐ด๐ถ๐ข๐ญ ๐ฆ๐ฅ๐ช๐ต๐ฐ๐ณ, ๐ง๐ญ๐ฆ๐น๐ช๐ฃ๐ช๐ญ๐ช๐ต๐บ, ๐ข๐ฏ๐ฅ ๐ฆ๐ด๐ฑ๐ฆ๐ค๐ช๐ข๐ญ๐ญ๐บ ๐ต๐ฉ๐ฆ ๐๐๐ ๐ธ๐ฐ๐ณ๐ฌ๐ง๐ญ๐ฐ๐ธ ๐ฉ๐ข๐ท๐ฆ ๐ฎ๐ข๐ฅ๐ฆ ๐ถ๐ด ๐ธ๐ข๐ฏ๐ต ๐ต๐ฐ ๐ฃ๐ถ๐ช๐ญ๐ฅ ๐ฐ๐ถ๐ณ ๐ธ๐ฉ๐ฐ๐ญ๐ฆ ๐ด๐บ๐ด๐ต๐ฆ๐ฎ ๐ฐ๐ฏ ๐๐ฆ๐๐ฆ๐ฃ ๐ช๐ฏ๐ด๐ต๐ฆ๐ข๐ฅ ๐ฐ๐ง ๐ฎ๐ฐ๐ท๐ช๐ฏ๐จ ๐ฆ๐ญ๐ด๐ฆ๐ธ๐ฉ๐ฆ๐ณ๐ฆ.โ
โ๐๐ฐ๐ท๐ข๐ฃ๐ญ๐ฆ ๐ช๐ด ๐ช๐ฏ๐ค๐ณ๐ฆ๐ฅ๐ช๐ฃ๐ญ๐ฆ ๐ง๐ฐ๐ณ ๐ช๐ฎ๐ฑ๐ญ๐ฆ๐ฎ๐ฆ๐ฏ๐ต๐ช๐ฏ๐จ ๐ต๐ฉ๐ช๐ฏ๐จ๐ด ๐ง๐ข๐ด๐ต ๐ข๐ฏ๐ฅ ๐ค๐ฉ๐ฆ๐ข๐ฑ๐ญ๐บ ๐ธ๐ช๐ต๐ฉ ๐ซ๐ถ๐ด๐ต ๐ข ๐ง๐ฆ๐ธ ๐ฑ๐ณ๐ฐ๐ฎ๐ฑ๐ต๐ด, ๐ฃ๐ถ๐ต ๐บ๐ฐ๐ถ ๐ฅ๐ฐ๐ฏโ๐ต ๐จ๐ฆ๐ต ๐ต๐ฉ๐ฆ ๐ค๐ฐ๐ฏ๐ต๐ณ๐ฐ๐ญ ๐ข๐ฏ๐ฅ ๐ณ๐ฆ๐ข๐ฅ๐ข๐ฃ๐ช๐ญ๐ช๐ต๐บ ๐๐ฆ๐๐ฆ๐ฃ ๐ฉ๐ข๐ด.โ
"๐ ๐ญ๐ฐ๐ท๐ฆ ๐๐ฆ๐๐ฆ๐ฃ. ๐๐ฉ๐ช๐ฑ๐ฑ๐ฆ๐ฅ ๐ข ๐ง๐ฆ๐ธ ๐ด๐ฎ๐ข๐ญ๐ญ ๐ธ๐ฆ๐ฃ๐ด๐ช๐ต๐ฆ ๐ณ๐ฆ๐ง๐ณ๐ฆ๐ด๐ฉ๐ฆ๐ด ๐ข๐ฏ๐ฅ ๐ฃ๐ถ๐ช๐ญ๐ฅ๐ช๐ฏ๐จ ๐ฎ๐บ ๐ง๐ช๐ณ๐ด๐ต ๐ง๐ถ๐ญ๐ญ ๐ง๐ญ๐ฆ๐ฅ๐จ๐ฆ๐ฅ ๐ธ๐ฆ๐ฃ๐ข๐ฑ๐ฑ ๐ฏ๐ฐ๐ธ. ๐๐ช๐ต๐ฉ๐ฐ๐ถ๐ต ๐บ๐ฐ๐ถ ๐ช๐ต ๐ธ๐ฐ๐ถ๐ญ๐ฅ๐ฏ'๐ต ๐ฃ๐ฆ ๐ฑ๐ฐ๐ด๐ด๐ช๐ฃ๐ญ๐ฆ ๐ง๐ฐ๐ณ ๐ฎ๐ฆ.โ
๐จโ๐ป 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. ๐
Popups are everywhere in an app: confirming an action, showing product details, presenting a sign-in form... And you don't need to rebuild them from scratch every time. In this tutorial I go through the 3 features that turn popups into reusable building blocks in @weweb_io
๐บ Link in the comments
WeWeb is now a verified @claudeai Connector! ๐
Coding agents are democratizing the power to build across teams.
Thatโs great... until IT is left worrying about the security and maintainability of what gets shipped.
Thatโs where WeWeb MCP comes in ๐
Claude can build secure, role-aware apps on top of your data directly inside WeWeb.
And unlike a black-box build, everything stays visible in the no-code editor.
Inspect every pixel, data model, workflow, role, permission, and integration.
Change it visually. Hand it over. Or keep building with your agent.
That's how you ๐ซต vibe code ๐งโ๐ป with the safety net ๐ฅ
of a visual editor.
No AI black box.
No throwaway prototype with security leaks.
No spaghetti codebase that turns into an IT problem six months later.
Connect WeWeb to Claude:
claude.ai/directory/weweb
I made a Calendar component for @weweb_io ๐
WeWeb as one you can use out of the box, but styling it the way I wanted was hard. So I built my own, based on shadcn.
Drop it flat on the page, behind a dropdown, or inside a popup. It allows for full customization of the behavior and the style to match your design system.
Link to the full video and to the demo in the comments
WeWeb released pre-rendering for pages. It makes building static pages relevant in WeWeb now that they can be properly indexed by search engines. In this video, I'm building a marketing page to see how WeWeb handles it. And I'm reviewing what Claude and the WeWeb MCP managed to build in one pass.
๐บ Link to the full video in the comments
RT @weweb_io: Every team has one: the โtemporaryโ workaround that quietly becomes critical infrastructure.
For Aaron Townsend, it was a duโฆ
Replying to @weweb_io
@weweb_io released pre-rendering for pages. It makes building static pages relevant in WeWeb now that they can be properly indexed by search engines. In this video, I'm building a marketing page to see how WeWeb handles it. And I'm reviewing what Claude and the WeWeb MCP managed to build in one pass.
๐บ Link to the full video in the comments
WeWeb X @Intercom X @Telegram ๐งฉ
Customer data โ conversations โ workflows, all in one app.
With Intercom, bring your companies, leads, and users directly into the apps you build.
With Telegram, turn a bot into a two-way channel for your workflows: send messages, files, updates, and react to what your users do.
Just ask AI to add Intercom or Telegram to your WeWeb app and start building right away ๐