Where founders rise on merit, not connections.

The last two days were a big step forward for VIVID. I moved VIVID's backend data from local SQLite to Supabase PostgreSQL, making the foundation much more scalable and persistent. What I worked on: 🔹 Migrated existing VIVID data to Supabase 🔹 Connected the backend to Supabase PostgreSQL 🔹 Created Supabase Storage for persistent video uploads 🔹 Tested community example-video uploads 🔹 Fixed PostgreSQL sequence issues after migration 🔹 Tested feature-request creation with Supabase 🔹 Connected video URLs from Storage with feature requests 🔹 Updated the backend for Supabase Storage 🔹 Verified the frontend still builds successfully 🔹 Cleaned up Git tracking with a proper .gitignore 🔹 Committed and pushed the changes to GitHub The next step: redeploying the backend on Northflank and testing everything in production. Slowly building VIVID into a more scalable product. ⚡ www.vividedit.online #VIVID #BuildInPublic #SaaS #Startup #Supabase #PostgreSQL #GitHub #WebDevelopment #IndieHacker

Today I worked on one of the most important parts of VIVID’s infrastructure: moving from temporary local storage toward a proper persistent database system. Here’s what I completed: 🔹 Connected the VIVID backend to Supabase PostgreSQL 🔹 Fixed the database connection and successfully tested it 🔹 Created a complete backup of the existing SQLite database before migration 🔹 Checked and counted the existing VIVID data 🔹 Prepared all major database tables for migration: Feedback Products Users Videos Feature Requests Feature Votes Feature Comments 🔹 Created the corresponding tables in Supabase successfully This means VIVID is now ready for the next step: migrating the existing data and making Supabase the permanent source of truth. The goal is simple: no more losing important VIVID data whenever the backend is redeployed. 💜 VIVID 2.0 is being built step by step. www.vividedit.online #VIVID #BuildInPublic #SaaS #Startup #AI #VideoEditing #Supabase #PostgreSQL #WebDevelopment #IndieHacker