Full-Stack Developer for SaaS Platform

# Full-Stack Developer / Development Team — Event Photo & Memory Sharing SaaS Platform ## PROJECT OVERVIEW I am looking for an experienced senior full-stack developer or development team to design, develop, brand and launch a professional event photo, video and memory-sharing platform. The concept is a modern platform where guests at an event scan a QR code and can immediately upload photos, videos and memories from their phones — without needing to download an app. The platform will initially target the Malta market, with the intention of expanding internationally. The platform will cater for: * Weddings * Funerals / memorials * Baptisms * Birthdays * Parties * Engagements * Anniversaries * Graduations * Corporate events * Holidays / group trips * Family events * Other private events This is intended to become a real commercial SaaS business, not a simple website or one-off project. I want a developer/team who can work with me from the initial concept through branding, UX/UI, development, testing, deployment and final handover. --- # IMPORTANT — I WANT TO OWN THE ENTIRE PLATFORM The final platform must be fully owned and controlled by me/my company. I require: * Full source code * Full Git repository * Database * Database schema * API * Frontend * Backend * Admin dashboard * Organiser dashboard * Deployment configuration * Infrastructure configuration * Documentation * Design files * Branding files * Deployment scripts * Tests * Technical documentation The system must be deployable to my own infrastructure/accounts. The developer must not retain exclusive control of: * Domain * Hosting * Cloud account * Database * Storage * GitHub/GitLab repository * DNS * Email provider * Payment accounts * API keys * Production infrastructure Where possible, all accounts should be created under my company ownership from the beginning. --- # MALTA COMMERCIAL EXCLUSIVITY The platform will initially be launched in Malta. I require commercial exclusivity for Malta for the custom Work Product developed specifically for this project. The developer/team must agree not to: * Resell the custom platform to a competing Malta business * Clone the commissioned platform for a direct Malta competitor * Reuse my branding * Reuse my custom UI/UX * Reuse my proprietary business logic * Use my brand/domain * Represent themselves as the owner of my platform Any pre-existing technology, templates, code, frameworks, plugins or proprietary components that the developer intends to use must be disclosed before development. The contract should clearly distinguish between: 1. My commissioned Work Product 2. Developer's pre-existing/background technology 3. Third-party/open-source technology --- # BRANDING & DESIGN I require the project to include professional branding and UI/UX design. This should include: * Logo * Logo variations * Favicon * Colour palette * Typography * Brand guidelines * UI design system * Buttons * Icons * Forms * Cards * Landing page * Event pages * Guest interface * Organiser dashboard * Admin dashboard * Mobile interface * Email templates * QR-code experience The design should feel: **Premium, modern, elegant, emotional, trustworthy and extremely easy to use.** It should work equally well for a wedding and for more sensitive occasions such as funerals/memorials. I do not want a generic template that looks like dozens of existing SaaS platforms. --- # CORE GUEST EXPERIENCE The main guest journey should be extremely simple: SCAN QR CODE ↓ OPEN EVENT ↓ NO APP REQUIRED ↓ UPLOAD PHOTOS / VIDEOS ↓ OPTIONALLY ADD NAME / MESSAGE ↓ SUBMIT The guest should not be forced to create an account unless necessary. The platform must be primarily designed for mobile use. --- # EVENT CREATION Organisers should be able to create events with: * Event name * Event type * Date/time * Location * Cover image * Description * Custom branding * Privacy settings * Guest permissions * Storage allowance * Event expiry * Password/PIN if required * Unique QR code * Unique event URL Example: `platform.com/event/john-and-mary` --- # EVENT TYPES The system should support different event experiences. ### WEDDINGS * Couple names * Wedding date * Venue * Guest photos * Videos * Messages * Speeches * Live gallery * Highlight memories * Event timeline ### FUNERALS / MEMORIALS * Person's name * Family information * Photos * Memories * Condolence messages * Videos * Private family access * Elegant/private design ### BAPTISMS * Child's name * Parents * Godparents * Date * Guest photos * Messages * Videos ### PARTIES * Host * Event name * Date * Location * Guest uploads * Live gallery ### HOLIDAYS / TRAVEL * Trip name * Dates * Participants * Locations * Shared photos/videos * Timeline The architecture must allow additional event types to be added later. --- # QR CODE SYSTEM Every event should automatically receive a unique QR code. Organisers should be able to: * Download QR as PNG * Download QR as SVG * Download print-ready version * Use branded QR design * Regenerate QR * Download QR cards/signage where applicable The QR code must link directly to the event. --- # PHOTO & VIDEO UPLOAD Guests should be able to upload: * JPG * JPEG * PNG * HEIC where feasible * MP4 * MOV where feasible Features should include: * Multiple uploads * Drag & drop desktop * Mobile camera access * Upload progress * Retry failed uploads * Image optimisation * Thumbnail generation * File-size limits * Storage limits * Duplicate handling where practical * Upload moderation Original files should be preserved according to the selected storage plan. --- # VERY IMPORTANT — 100+ SIMULTANEOUS GUESTS This is one of the most important technical requirements. At an event such as a wedding, 70 or more guests may be using the platform at the same time. For example: * 100 guests scanning the QR code * 50–100 guests uploading photos simultaneously * Multiple guests uploading videos * Other guests viewing the gallery * The organiser monitoring the dashboard * Photos being processed simultaneously The system must be designed so this does NOT cause: * Crashes * Major slowdowns * Upload failures * Database overload * Gallery failure * Server overload The developer must specifically design for high-concurrency event spikes. I expect the architecture to consider technologies such as: * Direct-to-object-storage uploads * Presigned upload URLs * Background processing * Queue/job systems * CDN * Image optimisation * Video processing * Caching * Database optimisation * Horizontal scaling where appropriate The application server should not unnecessarily process every large media file if a more scalable architecture can be used. --- # LOAD & PERFORMANCE TESTING Before final launch, the platform must be tested under realistic conditions. At minimum, test: ### Test 1 100 concurrent guests uploading photos. ### Test 2 100+ concurrent users uploading photos/videos while other users view the gallery. ### Test 3 200+ concurrent users accessing the same event. ### Test 4 Large event containing hundreds/thousands of media files. I want documented results including: * Response times * Upload success rate * Failed uploads * Server load * Database load * Storage performance * Queue performance * Recovery from failed uploads --- # LIVE EVENT GALLERY Organisers should be able to activate a live gallery. Approved photos should appear automatically. Features: * Grid/masonry layout * Full-screen viewer * Video playback * Latest uploads * Featured photos * Filtering * Sorting * Hide/delete * Moderation * Report inappropriate content The gallery should work on: * Phones * Tablets * Desktop * Large TV/projector screens --- # "FIND ME" — KEY DIFFERENTIATOR One of the main features I want to explore is an AI-powered **"Find Me"** function. Example: A guest takes a selfie. The system searches the event photos and says: "We found 37 photos of you." The guest can then view/download their photos. This feature must be designed carefully around privacy, consent and GDPR requirements. The developer must clearly explain: * AI technology * Facial-recognition technology * Where processing occurs * Whether third-party services are involved * Data retention * Consent * Data deletion * Security No undisclosed third-party facial-recognition system should be used. --- # AI EVENT HIGHLIGHTS The platform should support AI-assisted creation of: * Event highlights * Favourite photos * Memory collections * Short recap videos/slideshows The architecture should allow AI providers/models to be changed in the future. --- # MESSAGES & MEMORIES Guests should be able to leave: * Text messages * Congratulations * Condolences * Memories * Video messages * Voice messages Organisers should be able to: * Approve * Reject * Hide * Delete * Feature --- # EVENT TIMELINE Events should optionally have a timeline. Example: 18:00 — Guests arrive 19:00 — Ceremony 20:00 — Dinner 21:00 — Speeches 22:00 — Dancing Photos/videos can optionally be associated with different sections. --- # ZIP DOWNLOADS This is a **mandatory feature**. Organisers must be able to download: * All photos * All videos * All media * Original files where applicable The platform must be capable of generating large ZIP files using background processing. Example: `EVENT NAME /` `Photos /` `Videos /` `Messages /` `Originals /` `Processed /` Large ZIP files should not cause the website to freeze. The organiser should receive a notification when a ZIP is ready. --- # ADMIN DASHBOARD I require a complete Super Admin dashboard showing: * Total users * Total organisers * Total events * Active events * Completed events * Total uploads * Total photos * Total videos * Storage usage * Revenue * Subscriptions * Reports * Failed uploads * System alerts * Activity * Support issues --- # ORGANISER DASHBOARD Organisers should have their own dashboard with: * Event details * Guest count * Upload count * Storage usage * Photos * Videos * Messages * Moderation * QR code * Event URL * Analytics * Downloads * Branding * Settings * Event expiry * Subscription/plan --- # USER / GUEST MANAGEMENT The platform should include appropriate user and guest management. Roles may include: * Super Admin * Admin * Organiser * Guest Permissions must be handled securely at backend/API level. --- # EVENT SECURITY & ISOLATION Each event must be securely isolated. Guests from Event A must never be able to access: * Event B photos * Event B videos * Event B messages * Event B guest information * Event B downloads unless explicitly authorised. --- # STORAGE & INFRASTRUCTURE I want professional cloud architecture capable of handling large numbers of photos/videos. The developer must recommend: * Cloud provider * Object storage * Database * CDN * Image processing * Video processing * Backup * Disaster recovery * Monitoring * Logging The architecture must allow future migration to another provider. I do not want to be permanently locked into the developer's infrastructure. --- # MY OWN INFRASTRUCTURE The final production platform must run on infrastructure/accounts controlled by me/my company. I must own/control: * Domain * Cloud account * Hosting * Database * Storage * Git repository * DNS * Email * Payment provider * API accounts The developer receives access for development but must not retain exclusive control. --- # FULL SOURCE CODE OWNERSHIP I require complete source-code delivery. This includes: * Frontend * Backend * Database * API * Admin dashboard * Organiser dashboard * Infrastructure code * Deployment scripts * Tests * Documentation * CI/CD configuration where applicable No compiled-only delivery. No locked platform. No requirement to continue paying the original developer simply to operate the platform. --- # GITHUB / VERSION CONTROL The source repository should preferably be created under my company's GitHub/GitLab/Bitbucket account. I require: * Full repository access * Commit history * Branches * Documentation * Deployment instructions * Environment documentation --- # THIRD-PARTY SERVICES Before development starts, provide a complete list of every: * Framework * Library * API * Plugin * AI service * SaaS service * Open-source component * Commercial component For significant dependencies provide: * Licence * Cost * Purpose * Vendor lock-in risk * Replacement options No undisclosed proprietary dependency should be included. --- # FULL COST TRANSPARENCY — NO HIDDEN COSTS This is extremely important. I require a complete detailed breakdown of ALL costs required to build, launch and operate the platform. The proposal must clearly separate: ### A. ONE-TIME DEVELOPMENT COSTS * Design * Branding * Frontend * Backend * Dashboards * Testing * Deployment * Documentation * Other development costs ### B. ONE-TIME LAUNCH COSTS * Domain * Setup * Infrastructure * Configuration * Other launch costs ### C. MONTHLY COSTS * Hosting * Database * Storage * CDN * Email * Monitoring * Backups * AI * Other services ### D. USAGE-BASED COSTS * Storage * Bandwidth * Video processing * AI * Image processing * API usage * Other variable costs ### E. OPTIONAL COSTS Clearly identify anything that is optional. ### F. FUTURE DEVELOPMENT Clearly separate future features from the initial project. For every third-party service, I want: * Name * Purpose * Initial cost * Monthly cost * Annual cost * Usage charges * Estimated cost for 100 users * Estimated cost for 1,000 users * Estimated cost for 10,000 users * What causes the cost to increase * Whether it is mandatory or optional * Alternative options **I do not want hidden costs.** If a new mandatory cost is discovered during development, it must be communicated to me and approved before it is incurred. Please do not quote only the development price while leaving the infrastructure and third-party operating costs unclear. --- # ESTIMATED OPERATING COSTS Please provide estimated monthly operating costs at: * 10 events/month * 50 events/month * 100 events/month * 500 events/month * 1,000 events/month Please consider: * Storage * Bandwidth * CDN * Database * Image processing * Video processing * AI * Email * Backups * Monitoring * Other mandatory services I understand these are estimates and actual costs will depend on usage. --- # SECURITY Security is a major requirement. The platform should include appropriate: * HTTPS * Secure authentication * Password hashing * Role-based access * Secure uploads * File validation * Rate limiting * API security * Admin 2FA * Session security * Access-controlled media * Audit logs * Backups * Monitoring * Protection against common web vulnerabilities --- # GDPR / PRIVACY The platform will initially operate in Malta/EU, so GDPR/privacy must be considered from the beginning. The system should support: * Consent * Data deletion * Event deletion * User deletion * Data retention * Privacy settings * Data export where applicable * Access controls * Third-party processor considerations * Children's data considerations * Facial-recognition/biometric considerations The developer is not expected to provide legal advice, but the platform must be technically capable of implementing requirements from my legal/privacy adviser. --- # PAYMENTS & SUBSCRIPTIONS The platform should be designed to support monetisation. Potential plans: * Free * Paid Event * Premium * Subscription * Storage upgrades * Extended retention * Additional features Payment provider integration should be discussed. --- # ANALYTICS Organisers should be able to see: * Guests * Uploads * Photos * Videos * Messages * QR scans * Visitors where appropriate * Downloads * Activity Super Admin should have platform-level analytics. --- # EMAIL / NOTIFICATIONS The system should support: * Welcome emails * Event invitations * Password reset * Upload notifications * Event expiry notifications * Subscription notifications * Download-ready notifications * System notifications --- # MOBILE RESPONSIVENESS The platform must work properly on: * iPhone * Android * Tablets * Desktop The guest experience must be mobile-first. --- # PERFORMANCE & SCALABILITY The platform must be built to grow. The architecture should support progression from: **1 event → 10 events → 100 events → 1,000+ events** and potentially: **1,000 users → 10,000 users → 100,000+ users** without requiring a complete rebuild. The developer must explain how the system will scale. --- # BACKUPS & DISASTER RECOVERY I require documented procedures for: * Database backups * Media backups * Source-code backups * Configuration backups * Restoration * Disaster recovery --- # TESTING Before final acceptance, testing must cover: * Registration * Login * Event creation * QR codes * Photo upload * Video upload * Large files * Multiple simultaneous uploads * 100+ concurrent users * Gallery * Live gallery * ZIP downloads * Admin dashboard * Organiser dashboard * Permissions * Payments * Mobile responsiveness * Security * Error handling * Performance --- # DOCUMENTATION & HANDOVER At completion I require: * Complete source code * Git repository * Database * Database schema * API documentation * Infrastructure documentation * Deployment documentation * Design files * Brand files * Third-party dependency list * Licences * Backup documentation * Admin documentation * User documentation * Technical handover A competent developer should be able to take over the project without needing the original developer. --- # DEVELOPMENT MILESTONES I expect the project to be broken into milestones. Suggested structure: ### Milestone 1 — Discovery & Architecture Requirements, architecture, database, infrastructure and technical plan. ### Milestone 2 — Branding & UI/UX Brand identity, wireframes, UI/UX and responsive designs. ### Milestone 3 — Core Platform Users, events, QR codes, guest access, uploads and galleries. ### Milestone 4 — Dashboards Super Admin, Organiser dashboard, analytics and moderation. ### Milestone 5 — Advanced Features ZIP downloads, video, messages, AI, Find Me and highlights. ### Milestone 6 — Monetisation Plans, payments, subscriptions and storage limits. ### Milestone 7 — Testing QA, security, performance and concurrency testing. ### Milestone 8 — Deployment & Handover Production deployment, infrastructure transfer, source-code transfer, documentation and training. The exact milestones can be agreed during the discovery stage. --- # ACCEPTANCE CRITERIA Each milestone must have clear acceptance criteria. A milestone should not be considered complete simply because screenshots or a partially functioning demo have been provided. The functionality must be working according to the agreed specification. --- # POST-LAUNCH SUPPORT Please quote separately for: * 30-day support * 60-day support * 90-day support * Monthly maintenance * Emergency support * Future feature development Please distinguish between bug fixing and new feature development. --- # WHO I AM LOOKING FOR I am looking for a developer/team who thinks like a **long-term technical partner**, not simply someone who writes code. Experience with the following is highly desirable: * SaaS * Event platforms * Photo/video platforms * Large file uploads * Cloud infrastructure * Object storage * CDN * Image processing * Video processing * AI * Computer vision * Facial recognition * Payment systems * Admin dashboards * Multi-tenant systems * APIs * Secure authentication * GDPR/privacy-aware systems --- # PLEASE ANSWER THESE QUESTIONS IN YOUR APPLICATION Please do NOT send a generic proposal saying: **"I can build this for you."** I want to know that you have actually understood the project. Please answer: 1. Have you built a similar platform? Provide examples. 2. What technology stack do you recommend and why? 3. How would you handle 100+ guests uploading photos/videos simultaneously? 4. How would you architect the storage system? 5. How would you implement large ZIP downloads? 6. How would you implement "Find Me"? 7. What AI/facial-recognition technology would you recommend? 8. How would you approach GDPR/privacy? 9. How would you prevent vendor lock-in? 10. How will I own and control the infrastructure? 11. Will the Git repository be under my company account? 12. Will I receive 100% of the source code? 13. What third-party services would you use? 14. Please provide the complete expected costs and recurring costs. 15. What would you estimate the monthly infrastructure cost to be for 10, 50, 100 and 1,000 events? 16. What is your estimated development timeline? 17. What is your total development price? 18. Who will actually work on the project? 19. Are you an individual developer or agency? 20. Are you willing to provide Malta commercial exclusivity for the commissioned Work Product? 21. What pre-existing/background technology will you use? 22. How will you load-test the platform? 23. What happens if 100–200 guests use the same event simultaneously? 24. What post-launch support do you offer? 25. Please provide your proposed milestone structure. --- # FINAL GOAL The goal is to create a **premium, scalable event-memory platform** that people genuinely enjoy using. I want the platform to become more than simply: **"Scan a QR code and upload photos."** I want to build a complete memory platform that can eventually include: * Event photo sharing * Video sharing * Guest messages * AI photo organisation * "Find Me" * AI highlight videos * Live event walls * Digital memory timelines * Private family memory vaults * Photo books * Printed products * Subscriptions * Corporate events * Holiday/travel albums * Future mobile applications * International expansion The initial launch will focus on **Malta**, but the architecture must be capable of international expansion. I am looking for the right developer/team for a **long-term relationship**, with the initial project being the first stage of a larger commercial platform. **Please provide a serious, detailed proposal addressing the technical, design, commercial, scalability, ownership and infrastructure requirements above.**