Creator-approved AI fan chat with safer topics and optional monetization.
SocialTypeScript · CSSGitHub @ChiragSaini007OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
AI Persona for Creators
Translation pending
Taken from the repository README
Loading the full README.
Read the full README ↗Two products on one codebase, live at https://persona-studio-ai-three.vercel.app
/creator, /p/[handle]): creators and public figures sign up themselves, create any number of AI avatars, approve them, and share a fan link./admin): only the Ops team signs in. They build avatars on behalf of creators and celebrities whose agreements are handled outside the tool. Scope is the AI avatar only.Channels, in priority order: text, voice replies, real-time voice, video, real-time video. Markets: India and US.
Next.js 16 (App Router) · Supabase (Postgres, Auth, Storage, RLS) · OpenAI (chat, TTS, transcription, Realtime voice) · HeyGen (recorded video, wallet connected, not generating yet) · LiveAvatar (real-time video, sandbox tested) · Vercel.
PM documentation/ product scope, roadmap, statusEM documentation/ architecture, tech decisions, change log, runbookTest documentation/ strategy, test report, acceptance checklistsupabase/migrations/ run in order (001 to 006) in the Supabase SQL editornpm install, copy env names from EM documentation/Environment and Secrets.md, npm run dev. Always run npx next build before deploying.