Fotelya

Hi Fazier! I'm Jo, solo maker. Fotelya was born from my brother's wedding: I wanted his guests' photos to land on a live wall at the party, not to die in group chats. So I built it: guests scan a QR code, add photos from the browser (no app, no account), and the venue screen fills up in real time. Everything is EU-hosted, GDPR by design, and photos are never used to train AI. We are also live on Product Hunt today. Happy to answer anything!

Love the privacy-first approach for sharing event photos. Making it easy for guests to access memories without sacrificing data protection is a strong value proposition. Wishing you a successful launch!

Thank you Iryna! That balance was the whole challenge: privacy usually adds friction, and events are exactly where friction kills participation (grandparents included). So every privacy choice had to stay invisible for guests: scan, share, done. Thanks for the kind words and have a great day!

Nice work! This solves a real problem in a simple way. I hope you continue improving it with more useful updates.

Thank you! Simple was the hard part: everything has to work for a guest who scanned a QR code three seconds ago, so every update gets tested against that bar. If you ever think of something that would make it more useful for your events, I am all ears!

Fotelya is a great idea for making event memories easy to capture and share in real time

Event photo capture friction solved completely. Wedding and event organizers usually watch memories scatter - guests text blurry phone photos, some share to private Instagram DMs, half the candid moments vanish forever. Fotelya eliminates that fragmentation entirely. QR code setup means zero friction entry for guests - no app download, no account creation, just scan and shoot. Photos accumulate in one shared album instead of spilling across devices and cloud accounts. The live wall display changes the energy too - guests see themselves immortalized real-time, creating this shared moment energy that phone photography doesn't naturally produce. Privacy-first approach matters for events - your guest photos stay yours, never datafeed for marketing. Real win for event moments that deserve better than the chaos of group chat photo archaeology.

Wall displays is brilliant, how do you stop something embarrassing from being shared?

Thank you! Real time is really where the magic is: the wall fills up during the event and suddenly everyone wants to add their photos. Thanks for stopping by!

Wow, thank you Gal, you basically wrote a better pitch than mine. "Group chat photo archaeology" is exactly the problem, I might steal that phrase. And you nailed the live wall effect: seeing your photo appear on the big screen ten seconds after taking it is what turns passive guests into contributors. Appreciate you taking the time to look at it properly!

Answering We Got You 1776 on embarrassing uploads: it's the first thing venues ask too. Three layers. AI moderation (EU-hosted models) reviews every upload and anything flagged stays off the wall. Organizers choose how strict it should be (off, standard, strict) depending on the crowd. And if something slips through anyway, they can remove it from the wall in one tap. Weddings taught us to plan for uncle Bob at 1am.

The real-time display on the live wall is brilliant for engagement - guests actually want to contribute when they see their photos appear instantly. How are you handling the experience for users on older devices or slower network speeds at events?

Great question Omri, that constraint shaped most of the architecture. Uploads are resumable with an offline queue in IndexedDB: when the venue wifi drops (it always does), photos wait on the device and retry when the connection comes back, without the guest doing anything. The guest side is a plain lightweight web page, no app to download, so it stays usable on a five-year-old Android with one bar of 3G. And the live wall runs on the venue screen, not on guest devices, so their phones only ever upload. Concrete wedding venues were basically our QA lab.

Would love to know about the max storage per user can use and per media file limit you guys use from an engineering point of view, to manage your storage pricing.

Very useful approach, thanks for creating this one.

Answering Rohit on storage: great engineering question. Per media file we cap at 40 MB today (photos and videos, originals preserved). We deliberately do not meter storage per user: pricing is per event, uploads unlimited on paid plans. It works because of two choices: object storage with zero egress fees keeps marginal cost low, and albums auto-delete after the event, so storage per event is bounded in time instead of accumulating forever. The free tier has limited retention, which also keeps the abuse surface small. Happy to go deeper if useful!

Thank you Zygimantas, glad the approach resonates! It came from watching real events hit the same three walls: app installs, account creation, and photos that never get shared. Appreciate the kind words!

This is so useful for large scale events.

Thank you Styla team! Large events are exactly where it shines: the more guests, the more angles of the same moment you collect. The live wall handles hundreds of guests uploading at once, we load tested it well beyond a typical wedding. Appreciate the support!

The no-app QR flow and the stance that privacy must stay invisible for guests feel right for events. I also like that moderation has both AI filtering and one-tap removal instead of assuming the model catches everything. For organizers choosing a plan, a simple capacity guide would be valuable: typical upload limits, expected gallery retention, and what happens when a large event’s Wi-Fi fails. Those details would make the first event easier to plan with confidence.