Next.js + Supabase SaaS Chatbot Update (Vercel Chat) & Development few things
Budget: $30 – $250 USD
Hello everyone,
I have a SaaS project built with Next.js and Supabase. It currently uses an older version of Vercel’s chat module, and I’d like to remove it in favor of a newer version. The previous freelancer also added two separate “Chat UI” interfaces, which I want to get rid of entirely.
There’s also a “prompt archive” section in the admin panel (connected to Supabase) displaying added prompts. I want this section, along with its related code and Supabase integration, completely removed.
Tasks & Requirements
Remove Existing Chat Modules / Integrate New Chat
Delete the old Vercel chat module.
Remove the two additional “Chat UI” interfaces that were previously implemented.
Integrate the new chat version in its place.
Eliminate “Prompt Archive” and Associated Supabase Code
Fully remove the “prompt archive” section.
Delete any related tables, records, or references in Supabase.
Add Daily User Limits in Admin Panel
Implement daily conversation limits for both free and premium users.
Create a new section or settings option in the admin panel to manage these limits.
Once the old chat and RAG (Retrieval Augmented Generation) features are removed, ensure any auto-uploaded file processes and their database references are also cleaned up.
Migrate API Credentials from .env to Supabase
Move existing API keys (currently stored in .env) into Supabase.
Add an admin panel section to configure the “Target Provider URL,” “API Key,” and “Model Names.”
The chatbot interface should allow users to select from the models specified in the admin panel.
Model-Based Daily Limit Feature
In the admin panel, include a checkbox option for each model to enforce a special daily limit.
For example, free users might typically have 10 messages/day, and premium users 100. But if the checkbox is selected for a particular model, it might only allow, say, 10 messages/day on that model—even if the overall limit is higher.
Each message sent should still deduct from the user’s overall daily allowance.
Expectations
Clean, well-documented, and maintainable code.
Expert-level understanding of Next.js and Supabase integrations.
All features and configurations must be easily managed from the admin panel.
Be prepared to make minor UI adjustments as needed.
Dont forget guys my budget is 80$ and time is one week
I have a SaaS project built with Next.js and Supabase. It currently uses an older version of Vercel’s chat module, and I’d like to remove it in favor of a newer version. The previous freelancer also added two separate “Chat UI” interfaces, which I want to get rid of entirely.
There’s also a “prompt archive” section in the admin panel (connected to Supabase) displaying added prompts. I want this section, along with its related code and Supabase integration, completely removed.
Tasks & Requirements
Remove Existing Chat Modules / Integrate New Chat
Delete the old Vercel chat module.
Remove the two additional “Chat UI” interfaces that were previously implemented.
Integrate the new chat version in its place.
Eliminate “Prompt Archive” and Associated Supabase Code
Fully remove the “prompt archive” section.
Delete any related tables, records, or references in Supabase.
Add Daily User Limits in Admin Panel
Implement daily conversation limits for both free and premium users.
Create a new section or settings option in the admin panel to manage these limits.
Once the old chat and RAG (Retrieval Augmented Generation) features are removed, ensure any auto-uploaded file processes and their database references are also cleaned up.
Migrate API Credentials from .env to Supabase
Move existing API keys (currently stored in .env) into Supabase.
Add an admin panel section to configure the “Target Provider URL,” “API Key,” and “Model Names.”
The chatbot interface should allow users to select from the models specified in the admin panel.
Model-Based Daily Limit Feature
In the admin panel, include a checkbox option for each model to enforce a special daily limit.
For example, free users might typically have 10 messages/day, and premium users 100. But if the checkbox is selected for a particular model, it might only allow, say, 10 messages/day on that model—even if the overall limit is higher.
Each message sent should still deduct from the user’s overall daily allowance.
Expectations
Clean, well-documented, and maintainable code.
Expert-level understanding of Next.js and Supabase integrations.
All features and configurations must be easily managed from the admin panel.
Be prepared to make minor UI adjustments as needed.
Dont forget guys my budget is 80$ and time is one week