Migrate Lovable and Supabase-based SaaS to AWS

@AwaisChaudhry

Hello, RELAY migration to AWS is a clear path to better control, security, and scalability for your Relay vault. I will map your current Supabase-based Postgres schema and data to Amazon RDS, replace Supabase Auth with Cognito (including migrating users and configuring Google OAuth with a custom domain callback), and port ~8 Deno-based Edge Functions to Node.js Lambda. The storage will shift to S3 and the API will sit behind API Gateway, with CI/CD updated via GitHub Actions or AWS CDK as you prefer. I will ensure 1:1 feature parity where possible, especially around RLS logic, and implement application-level controls to match your current security model. The plan includes a concrete migration timeline, a rollback strategy, and detailed environment variable documentation to keep the new setup clean and maintainable. The final architecture will be described in a lightweight migration plan and a practical day-to-day runbook. 1) What is the current data size and growth rate, plus any sensitive datasets requiring special handling? 2) Do you have existing Cognito user pools and Google OAuth domain approved, or should I set this up from scratch with a custom domain? 3) Are there any non-functional targets (cost ceiling, latency budgets, compliance) I should design for from day one? 4) Do you prefer Terraform, CDK, or console-based provisioning for the AWS stack? Best regards, Muhammad Awais

@techplusintl

Hi, I understand you need to migrate your application from Supabase to AWS, focusing on PostgreSQL, authentication, storage, and serverless functions. I have experience with similar migrations and can ensure a smooth transition without data loss. Could you clarify if you have a preferred method for infrastructure management, like Terraform or AWS CDK? Please share any additional details or access needed to start the project. Thanks!

@OutsourceMan

⭐⭐⭐⭐⭐ RELAY CnELIndia and Raman Ladhani bring extensive experience in Supabase-to-AWS migrations, including Postgres, Cognito, S3, and Lambda implementations. Database Migration: Export Supabase Postgres tables and import into Amazon RDS with zero downtime, ensuring data integrity. Authentication: Migrate existing users to Amazon Cognito and configure Google OAuth with custom domain callback URLs; update frontend AuthContext to use AWS Amplify SDK. Edge Functions: Port 8 Deno-based Edge Functions to Node.js Lambda with equivalent business logic, integrating with API Gateway for routing. Storage Migration: Move Supabase Storage files to Amazon S3 with proper folder structure and access policies. Security Mapping: Recreate Row Level Security using Lambda-level authorization and IAM policies for granular access control. CI/CD: Implement seamless deployment via GitHub Actions or AWS Amplify pipelines. Documentation & Planning: Provide detailed migration plan, architecture diagrams, and environment variable mappings to ensure maintainability and scalability. Timeline & Delivery: Structured phased approach enables completion efficiently while minimizing service disruption.

@iosifpeterfi

RELAY - This is my speciality: migrating complex Supabase-backed apps to AWS with security-first design. Hi, I'm Iosif Peterfi, Senior Systems & Security Engineer with 15 years in cloud migrations, security hardening, and IaC. I'm ready to start as soon as we align on scope. My approach: migrate Postgres to RDS with minimal downtime; replace Supabase Auth with Cognito (migrate users, configure Google OAuth with a custom domain callback); move files to S3; port 8 Deno Edge Functions to Node.js Lambda; expose APIs via API Gateway; update CI/CD to GitHub Actions or AWS CDK; map RLS to app-level checks and enforce least-privilege IAM policies. Relevant qualifications: I've led Supabase-to-AWS-like migrations and other secure cloud migrations (MPDL, ethernity_cloud, Schnellno). See portfolio for examples: https://www.freelancer.com/u/iosifpeterfi Would you prefer Terraform, AWS CDK, or CloudFormation for the IaC, and do you have an existing Google domain for OAuth?

@reedsystems

RELAY Hi, I recently completed a successful Supabase-to-AWS migration for a similar SaaS application, streamlining the database and enhancing security features while improving scalability and custom branding capabilities. For this project, I propose the following timeline: 1. Data Migration & Setup - 3 days: Export and import data from Supabase to Amazon RDS. 2. Auth Refactoring - 4 days: Migrate user records and configure Google OAuth with a custom domain callback URL using Amazon Cognito. 3. Storage Migration - 2 days: Transfer files from Supabase Storage to S3. 4. Function Porting & Security Mapping - 5 days: Rewrite Deno Edge Functions as Node.js Lambda functions, ensuring RLS logic is mapped correctly. 5. API Gateway Implementation & CI/CD Setup - 3 days: Integrate API Gateway and update the deployment pipeline with GitHub Actions. In terms of infrastructure management, I prefer using AWS Console for its ease-of-use during this phase but can transition to Terraform if needed due to my extensive experience in both. For more details on past projects or a live demo, you can check out my portfolio here: https://www.freelancer.com/u/reedsystems Looking forward to your feedback!

@juanestebana17

Hello, I have extensive experience in migrating applications from Supabase to AWS, including complex data, auth, and serverless logic transfer, ensuring zero data loss and security. I will ensure a smooth migration of your PostgreSQL, auth system, and serverless functions, replicating your current setup with enhanced scalability. What specific security requirements or compliance standards should be prioritized during the migration? Thanks, Juan Aponte

@webperfection123

**"RELAY"** For this migration, I can help with exporting the Supabase data to Amazon RDS, setting up Amazon Cognito for authentication (including Google OAuth), and moving your existing serverless logic to AWS Lambda. I have experience with similar migrations and can ensure that all functionalities are replicated seamlessly. Additionally, I can enhance your CI/CD pipeline using GitHub Actions or AWS Amplify to streamline deployments. With my strong expertise in Node.js, TypeScript, PostgreSQL, and AWS services, I’m confident we can achieve a smooth migration. Let’s connect to discuss your requirements and create a solid plan for the transition! Best Regards, Priyanka

@kumarashish99

RELAY! With extensive experience in developing, deploying, and managing cloud-based infrastructures, I pride myself on my ability to deliver successful and smooth migrations. Having performed numerous AWS migrations including similar ones like Supabase-to-AWS or Firebase-to-AWS, I am confident in migrating your SaaS to AWS effectively and efficiently, with minimal data loss. Moreover, as a backend specialist proficient in Node.js/TypeScript, PostgresSQL, and React paired with AWS expertise that goes beyond the required services - Cognito, RDS, S3, and Lambda - taking down your tasks such as database migration with Amazon RDS (PostgreSQL), replacing Supabase Auth with Amazon Cognito including configuring Google OAuth with a custom domain callback URL , Migrating files to Amazon S3 etc. will be an easy sail for me. In terms of infrastructure management, I prefer using AWS CDK and this would also provide you with an infrastructure that is well-documented. My whole approach resonates around clarity and efficiency. Trust me with your project to get a thoroughly planned migration from the Supabase ecosystem into AWS that meets your requirements while transforming your service into a highly customizable and scalable solution. Let's discuss how I can make this migration a breeze for you!

@ZohaibRoy

⭐⭐⭐⭐⭐ Migrate Supabase SaaS to AWS with Expertise and Precision ❇️ Hi My Friend, I hope you're doing well. I've reviewed your project requirements and see you are looking for a Cloud Migration Specialist. Look no further; Zohaib is here to help you! My team has successfully completed 50+ similar projects for cloud migrations. We will ensure a smooth transition of your application to AWS while maintaining all functionalities. ➡️ Why Me? I can easily manage your migration from Supabase to AWS as I have 5 years of experience in cloud migrations, specializing in PostgreSQL, Node.js, and React. My expertise includes data migration, API integration, and serverless architecture. I also have a strong grip on AWS services like RDS, S3, and Lambda, which will ensure a seamless transition. ➡️ Let's have a quick chat to discuss your project in detail. I can provide samples of my previous work and elaborate on how I will ensure a successful migration. Looking forward to our conversation! ➡️ Skills & Experience: ✅ AWS RDS ✅ Amazon S3 ✅ Amazon Cognito ✅ AWS Lambda ✅ API Gateway ✅ Node.js ✅ TypeScript ✅ PostgreSQL ✅ React ✅ GitHub Actions ✅ Cloud Migration ✅ Serverless Architecture Waiting for your response! Best Regards, Zohaib

@Feriver

RELAY I have extensive experience migrating Supabase-based SaaS platforms to AWS. In a recent project, I moved a React + TypeScript application with Supabase Postgres, Auth, and Edge Functions to RDS, Cognito, S3, Lambda, and API Gateway while preserving user data, OAuth flows, and serverless logic. I refactored Edge Functions to Node.js Lambdas and updated the frontend to use Cognito SDKs seamlessly. For your platform (~10 tables, 8 Edge Functions), I estimate **3–4 weeks** for full migration including data transfer, auth migration with Google OAuth, Lambda function porting, storage migration, API Gateway setup, and CI/CD pipeline update using GitHub Actions. I prefer **AWS CDK** for infrastructure as code to ensure reproducibility and maintainability. All RLS and authorization logic will be mapped to application-level checks in Lambda/IAM policies. Client Clarification Questions: 1. Are all current Supabase RLS policies fully documented, or should I extract and interpret them from the existing functions? 2. Should the migration include live data sync to allow zero-downtime cutover, or is a scheduled maintenance window acceptable? Thanks, Asif

@devendrathakur12

RELAY Hello, Can we discuss about your Relay migration project cause I have worked on moving backend logic from managed platforms into modular AWS services so teams gain full infra control. This stack fits well with RDS, Cognito, Lambda and API Gateway. Timeline looks around 4–6 days with careful auth and function refactor. I usually manage infra with Terraform. Will existing Supabase password hashes be migrated into Cognito or should users reset passwords? Do Lambda functions handle asset encryption with KMS? Is RLS logic heavy across tables? Cognito domain setup often affects Google OAuth redirects early. Best regards, Devendra S.

@Friends4it

Hi, RELAY - I understand you need to migrate your Lovable and Supabase-based SaaS "Relay" to AWS, preserving your PostgreSQL data, auth, storage, serverless logic, and API layer exactly. Your stack includes React (Vite), TypeScript, Tailwind CSS, and Deno edge functions, aiming for full AWS service replacement with Cognito, RDS, Lambda, S3, and API Gateway. I’ve successfully migrated similar SaaS platforms with PostgreSQL, Supabase Auth to Cognito, and Deno functions to Node.js Lambdas, ensuring zero data loss and smooth auth transitions with custom domain OAuth. I use AWS CDK for infrastructure as code to guarantee repeatability and easy updates. I estimate 3 weeks (20 days) for full migration, testing, and documentation. Next step: I’d love to discuss your preferred CI/CD pipeline setup and any particular security concerns For your existing Supabase data and auth, do you have any specific security policies or workflows that must be maintained exactly during migration? Best regards, Muhammad

@johnallenvillan1

Hi RELAY, Migrating a Supabase stack with Deno edge functions, RLS rules, and Google OAuth to a fully de-bundled AWS setup is a path I’ve handled before, most recently for a real‑estate document vault where I moved 14 tables and 11 edge functions into RDS, Cognito, Lambda, and API Gateway with zero downtime. I kept Google OAuth functional via a custom hosted domain and mapped RLS logic into scoped Lambda access layers. On this project, the real complexity sits in translating Supabase Auth and RLS rules into Cognito flows and Lambda‑level authorization without losing the deterministic behavior your React/Vite frontend depends on. The Deno‑to‑Node shift also requires careful handling of crypto methods for asset encryption. I’ll map your existing schema into RDS, migrate assets to S3, re‑implement all 8 edge functions in Node‑based Lambdas, and update your AuthContext to target Cognito via Amplify. CI/CD will be wired through GitHub Actions with isolated staging. Before starting, I need clarity on how you’re currently handling refresh tokens and any custom policies tied to `profiles`. I can begin immediately and deliver a clean migration roadmap. Thanks, John allen.

@TechizeBuilder

Hi, I came across your project " Migrate Lovable and Supabase-based SaaS to AWS " and I'm confident I can help you with it. About Me: I'm a agency owner with over 8+ years of experience in Node.js, PostgreSQL, Linux, Amazon Web Services, Frontend Development, AWS Lambda. , and I understand exactly what’s needed to deliver high-quality results on time. Why Choose Me? - ✅ Expertise in required Technologies and 1 year post deployment free support - ✅ On-time delivery and excellent communication - ✅ 100% satisfaction guarantee Let’s discuss your project in more detail. I’m available to start immediately and would love to hear more about your goals. Looking forward to working with you! Best regards, Deepak

@koolvishruth

RELAY Hi, I have prior experience in Building application from Lovable and also having migration experience.I have 7 years of experience in software engineering and worked with 116+ clients. Let’s connect

@elishadiah326

RELAY Hi, Thank you for posting this well-defined migration project! I clearly understand your goal: de-bundle Supabase Cloud into a fully self-managed AWS architecture while preserving existing functionality across PostgreSQL data, authentication, storage, and serverless logic for your React/TypeScript SaaS platform. I have strong experience migrating Supabase/Firebase-style backends to AWS, including moving Postgres workloads to Amazon RDS, replacing platform auth with Amazon Cognito, and porting serverless logic to Lambda + API Gateway. For this migration I would implement: RDS PostgreSQL for the existing schema, Cognito (with hosted UI + custom domain) for Email/Google OAuth, S3 for asset storage, and Lambda (Node.js/TypeScript) behind API Gateway to replace the Deno Edge Functions. I prefer Terraform or AWS CDK for infrastructure to ensure the environment is reproducible and version-controlled. My approach would be: export Supabase schema/data with pg_dump, migrate to RDS, port Edge Functions to Node Lambda handlers, replicate RLS rules through JWT-based auth + application-level authorization, and refactor the React AuthContext to use AWS Amplify/Cognito SDK. Estimated timeline: 2~3 weeks Quick question: do the current Supabase Edge Functions rely on Supabase client libraries, or are they mostly pure TypeScript logic? Best regards, Diah

@TomaK01

RELAY Hello, I've been coding since I was young, and I’m a full-stack software developer with +8 yrs of professional experience. I recently worked on a similar project and am genuinely excited about this opportunity. I’d love to share my ideas and discuss how my experience can help deliver the best solution for your project. Let’s connect in a private chat to go over the details and make sure my approach aligns with your goals. Thank you, Toma K.

@SmartCodeDev

RELAY Hi, I have experience migrating SaaS applications from managed platforms like Supabase and Firebase to AWS-based infrastructures. I’ve handled migrations involving PostgreSQL databases, authentication systems, serverless functions, and cloud storage while maintaining feature parity and minimizing downtime. For your Relay platform, I would migrate the Supabase Postgres database to Amazon RDS, move files from Supabase Storage to Amazon S3, and replace Supabase Auth with Amazon Cognito including Google OAuth with a custom domain callback. The existing Deno Edge Functions would be ported to Node.js AWS Lambda functions and exposed through API Gateway. I would also update the React frontend to use AWS Amplify or Cognito SDK for authentication and API access. Supabase RLS policies can be mapped to application-level authorization within Lambda and IAM roles to maintain secure access control. For a project of this size (around 10 tables and 8 functions), the migration and testing would typically take about 2–3 weeks. I prefer using Terraform or AWS CDK so the infrastructure remains version-controlled and easy to maintain. Thank you.

@abdulhamidh2

**RELAY** I recently completed a project where I migrated a SaaS application from Supabase to AWS, successfully replicating all backend features and ensuring a seamless user experience. This experience directly aligns with your need to transition your digital vault and asset management platform from Supabase Cloud to AWS infrastructure. My primary focus will be on ensuring a smooth database migration to Amazon RDS while securely transitioning your authentication system to Amazon Cognito. Additionally, I will ensure that all edge functions are effectively ported to AWS Lambda, maintaining the integrity of your existing logic. With proven expertise in Node.js, TypeScript, PostgreSQL, and a strong understanding of AWS services such as Cognito, RDS, S3, and Lambda, I am confident I can complete this project efficiently. I am ready to begin work immediately and would like to discuss the details further. Thank you for reviewing my proposal. Abudulhamid