Can Vernigo be vibe coded?
Find outlier YouTube videos, unsaturated niches, and proven ideas from a continuously updated video database
You can build filters, bookmarks, and an outlier score over a small set of YouTube channels, but Vernigo's product is the continuously refreshed corpus: millions of videos, channel baselines, niche-level supply and demand signals, and ranking data improved by how thousands of users interact with the library. A one-shot app can reproduce the interface and formula, not the dataset that makes the results useful.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
high editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Track a curated list of YouTube channels, compare each video's views with that channel's recent average, and browse the resulting outliers with filters and bookmark folders.
- Ingest a known data source, calculate a focused metric set, and render a useful dashboard.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- the 10M-video historical and continuously updating database
- broad discovery beyond channels you already know
- unsaturated niche rankings across the wider YouTube market
- community interaction signals from more than 2,000 users
- The useful dataset is owned, accumulated, or expensive to reproduce.
- The value comes from the people already using it.
Why people still pay
The useful result is not calculating views divided by a channel average. It is having enough current video and channel history to discover outliers and undersupplied niches before you already know where to look. Building the dashboard is straightforward; collecting, refreshing, and ranking that market-wide dataset is the product.
The useful dataset is owned, accumulated, or expensive to reproduce.
The value comes from the people already using it.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Vernigo
Context
**Vernigo** — Find outlier YouTube videos, unsaturated niches, and proven ideas from a continuously updated video database. It currently costs $39/mo.
You can build filters, bookmarks, and an outlier score over a small set of YouTube channels, but Vernigo's product is the continuously refreshed corpus: millions of videos, channel baselines, niche-level supply and demand signals, and ranking data improved by how thousands of users interact with the library. A one-shot app can reproduce the interface and formula, not the dataset that makes the results useful.
This brief describes a focused, single-operator replacement for the part of Vernigo that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Track a curated list of YouTube channels, compare each video's views with that channel's recent average, and browse the resulting outliers with filters and bookmark folders.
Ingest a known data source, calculate a focused metric set, and render a useful dashboard.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Curated channel seed list.
Scheduled data collection.
Database.
Always-on box for refresh jobs.
Data and integrations
YouTube Data API key.
Each of these needs a real account, credential, or quota. Set them up before writing feature code.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build me a personal YouTube outlier research tool inspired by Vernigo. Requirements:
Django + PostgreSQL, one self-hosted web app; Google login is out of scope,
use a single admin password from .env.
Let me add YouTube channel IDs manually or import them from a CSV seed list.
Pull each channel's recent videos through the official YouTube Data API and
store title, thumbnail, views, duration, publish date, and channel stats.
Calculate an outlier multiplier as video views divided by the average views
of that channel's previous five videos available in the database.
A searchable video grid with filters for multiplier, views, subscribers,
duration, publish date, category, and channel age; sortable by multiplier,
views, or newest.
Bookmark folders: create, rename, and delete folders, and save or remove
videos without duplicating them.
A niche page that groups imported channels by a manually assigned niche and
ranks niches using median views per video divided by videos published.
Run refresh jobs with Celery + Redis once per day, respect API quota errors,
and show the last successful refresh time for every channel.
Store all secrets in .env; include Docker Compose for Django, PostgreSQL,
Redis, Celery worker, and scheduler.
Out of scope: crawling all of YouTube, a 10M-video corpus, community ranking
signals, automatic niche classification, and claims that this finds the
best opportunities market-wide. It only analyzes the channels I seed.
README: YouTube API setup, quota limits, CSV format, calculation details,
backup steps, and the limits of a small personal dataset.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
The 10M-video historical and continuously updating database.
Broad discovery beyond channels you already know.
Unsaturated niche rankings across the wider YouTube market.
Community interaction signals from more than 2,000 users.
The useful dataset is owned, accumulated, or expensive to reproduce.
The value comes from the people already using it.
What you still own after launch
Secure credentials, rotate secrets, and handle provider rate limits.
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Risk
**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.
Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/vernigo
You still own the product
- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
Before you start
Can Vernigo be vibe coded?
Not faithfully. You can build filters, bookmarks, and an outlier score over a small set of YouTube channels, but Vernigo's product is the continuously refreshed corpus: millions of videos, channel baselines, niche-level supply and demand signals, and ranking data improved by how thousands of users interact with the library. A one-shot app can reproduce the interface and formula, not the dataset that makes the results useful.
What can an AI coding agent reproduce from Vernigo?
Track a curated list of YouTube channels, compare each video's views with that channel's recent average, and browse the resulting outliers with filters and bookmark folders. Ingest a known data source, calculate a focused metric set, and render a useful dashboard. A responsive interface with real empty, loading, success, and error states.
What will a DIY Vernigo replacement still be missing?
the 10M-video historical and continuously updating database; broad discovery beyond channels you already know; unsaturated niche rankings across the wider YouTube market; community interaction signals from more than 2,000 users; The useful dataset is owned, accumulated, or expensive to reproduce.; The value comes from the people already using it.
What do I still own after building a Vernigo alternative?
Secure credentials, rotate secrets, and handle provider rate limits. Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss.