new-term-radar
Daily radar for new AI terms: names of new models, products and repos, caught on X, Hugging Face, GitHub and sitemaps before keyword tools list them.
The intelligent marketplace connecting brands with world-class creators.
MarketingJavaScript · TypeScriptGitHub @ParrvLuthra22OnlineOwner 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
Loading the full README. The saved excerpt is shown below.
The intelligent marketplace connecting brands with the right creators — by niche, audience, and authenticity. No more cold DMs.
Brands looking for creators to work with are stuck between two bad options: cold-DMing influencers and hoping for a reply, or paying an agency a markup to do the same thing manually. Creators, meanwhile, spend more time chasing brand deals in their inbox than actually creating.
CreatorLyff is a two-sided marketplace that fixes both sides of that problem:Read the full README ↗The intelligent marketplace connecting brands with the right creators — by niche, audience, and authenticity. No more cold DMs.
Brands looking for creators to work with are stuck between two bad options: cold-DMing influencers and hoping for a reply, or paying an agency a markup to do the same thing manually. Creators, meanwhile, spend more time chasing brand deals in their inbox than actually creating.
CreatorLyff is a two-sided marketplace that fixes both sides of that problem:
It's built as a full-stack, production-shaped app — real auth, a real database, real-time messaging, OAuth integrations with six platforms, and a fully custom dark/lime design system with the kind of motion/interaction polish you'd expect from a funded startup's marketing site, not a bootcamp project.
Landing page
How it works
Discover creators
Public creator profile
Brand dashboard
Brand → unlocked creator discovery
Creator dashboard
Creator profile editor
Admin — platform overview
Admin — verification queue
All screenshots above are of the actual running app — a live local backend, a seeded MongoDB database with 20 mock creators and a real signed-up brand/creator/admin account, not mockups.
/c/[handle]) — a full portfolio page per creator: parallax cover hero, real computed stats (combined followers, engagement rate, avg. views, 30-day profile views), platform cards, a masonry showcase with a lightbox (images, video, embedded YouTube), public rate cards, a "trusted by" logo wall sourced from real accepted deals, and a "Send Proposal" CTA that routes brands straight into a pre-filled campaignisAdmin flag, granted only via a seed script — never through the UI)#0a0a0a) + lime (#d4ff4f) visual identity, enforced via CSS custom properties everywhere — no hard-coded colorsprefers-reduced-motion and hides on touch devicesEscape support and role="dialog" semantics on every modalcreatorsync2/
├── frontend/ Next.js 16 (App Router) + React 19 + TypeScript
│ ├── app/ Routes — public pages, dashboards, legal, auth
│ │ ├── dashboard/brand/ Brand dashboard route group
│ │ ├── dashboard/creator/ Creator dashboard route group
│ │ ├── dashboard/admin/ Admin dashboard route group
│ │ └── c/[handle]/ Public creator profile (server component + metadata)
│ ├── components/ UI, section, and dashboard components
│ │ ├── sections/ Landing page sections
│ │ ├── dashboard/ Shared dashboard chrome (sidebars, modals, toasts)
│ │ ├── admin/ Admin-only components
│ │ └── three/ WebGL/shader components (code-split, ssr:false)
│ └── lib/ API client, Zustand auth store, TanStack Query hooks
│
├── backend/ Node.js + Express + TypeScript
│ └── src/
│ ├── routes/ auth, profile, proposals, chat, uploads, admin,
│ │ verification, activity, notifications, instagram,
│ │ youtube, payments (mounted but disabled)
│ ├── models/ User, CreatorProfile, BrandProfile, Proposal,
│ │ Conversation, Message, Notification,
│ │ VerificationRequest, Payment
│ ├── middleware/ JWT auth, admin/cron-secret auth, rate limiting
│ ├── services/ Instagram/YouTube data sync, notification center
│ ├── jobs/ Daily social-stats re-sync (node-cron)
│ └── socket.ts Socket.io real-time chat + notification push
│
└── docs/screenshots/ The images in this README
Frontend: Next.js 16 (App Router, Turbopack), React 19, TypeScript, Tailwind CSS v4 (CSS-variable design tokens, no config file), Zustand, TanStack Query 5, Framer Motion, GSAP, Lenis (smooth scroll, disabled on dashboards), @react-three/fiber + Three.js (hero shader), Recharts, Socket.io client.
Backend: Express, TypeScript, MongoDB + Mongoose, JWT (httpOnly cookies), Passport (Google/Instagram/YouTube/Twitter/LinkedIn/Snapchat OAuth), bcrypt, Socket.io, node-cron, Cloudinary (uploads, with local-disk fallback), Resend (email), PostHog (analytics), Razorpay (integrated, disabled).
Data flow, at a glance: the frontend never talks to MongoDB directly — every request goes through the Express API, which is the single source of truth for auth (JWT cookie, verified per-request), authorization (role checks + a separate isAdmin flag), and rate limiting. Real-time events (new message, new proposal, verification decision) are pushed over the same Socket.io connection the chat UI already holds, and land in the notification center without a page refresh. Social platform data (followers, engagement, recent posts) is pulled once via OAuth, cached on the creator's profile document, and refreshed by a daily cron job — the numbers a brand sees are never live-fetched from Instagram/YouTube on page load.
npm run install:all
cp backend/.env.example backend/.env
backend/.env.example documents every variable the backend reads, with a comment explaining what each is for. At minimum, set MONGODB_URI and JWT_SECRET — everything else (Cloudinary, Resend, PostHog, each OAuth provider, Razorpay) degrades gracefully when unset.
Create frontend/.env.local:
NEXT_PUBLIC_API_URL=http://localhost:5001
mongod
npm run dev
This starts both the frontend (:3000) and backend (:5001) concurrently.
cd backend
npm run seed:mock-creators # 20 realistic mock creator profiles
npm run seed:admin # grants admin access to accounts listed in ADMIN_EMAILS
/dashboard/admin/setup in the running app documents the same admin-seeding steps with copyable commands.
All routes are mounted under /api on the backend. Full request/response shapes live in the route files under backend/src/routes/.
| Resource | Base path | Covers |
|---|---|---|
| Auth | /api/auth | signup, login, logout, /me, password reset, email verification, OAuth callbacks |
| Profile | /api/profile | brand/creator profile CRUD, public creator directory, public creator-by-handle |
| Proposals | /api/proposals | create, list, accept/decline, deal-stage updates |
| Chat | /api/chat | conversations, message history, attachment uploads |
| Uploads | /api/uploads | Cloudinary (or local-disk) file uploads |
| Verification | /api/verification | request, approve, reject, auto-flag cron endpoint |
| Notifications | /api/notifications | list, mark-read |
| Activity | /api/activity | unified activity feed (proposals, messages, verification) |
| Admin | /api/admin | user management, platform stats, verification queue |
| Instagram / YouTube | /api/instagram, /api/youtube | OAuth connect + data sync |
SameSite cookies (no tokens in localStorage)isAdmin flag, granted only via a seed scriptMIT