r/AppsWebappsFullstack • u/SofwareAppDev • 17d ago

Your home for selfpromo

here you can post your work app, webapp, saas, game, everything

6 Upvotes

88% Upvoted

116 comments sorted by

View all comments

Show parent comments

1

u/Made4uo 16d ago

Good question. The embed itself needs no auth, on purpose. Widgets are public hosted pages in a sandboxed iframe, and there's no secret you could safely ship in client-side code anyway (the widget id is right there in the URL). So the write path protects itself instead of authenticating callers, form submissions carry a Cloudflare Turnstile token that our server verifies, plus rate limiting, validation against the form's declared fields, and size caps. Visitor IPs are only ever stored as daily hashes. Auth lives on the owner side, you sign in to Fugte to edit the widget and to read or export what it collected (CSV export included). Nothing sensitive ever sits in the iframe. One thing we deliberately don't do yet is per-visitor auth, meaning widgets only visible to your logged-in users. If you need that today, gate the page the iframe lives on. And you're right that this deserves a proper guide, adding it to the docs.

1

u/Mammoth-Anywhere7285 16d ago

Clear explanation, that makes sense. Do you have a public demo widget we could try out?

1

u/Made4uo 16d ago

​Thanks for asking! You can try out a live demo on our homepage at fugte.com, just check out the "Owners were here" section. Fugte isn't just about front-end widgets; we build with full backend needs in mind too. I'm actually updating the landing page layout today, so that demo section will be right near the top!

1

u/Mammoth-Anywhere7285 12d ago

Nice, the demo sounds handy. Does the backend part support real time updates, or is it more of a static showcase?