trendradar DB
LIVE DATABASE VIEW

Creator intelligence
wired to your current data

The homepage now renders from your tables instead of frontend mock data: featured creator, trending shorts, categories, and plans are pulled from the application layer.

TikTok Reels Shorts
Using current application tables with automatic source fallback.
Actual creator metrics
Source-aware trending feed
Categories from your taxonomy

Current footprint

2.3M+

videos tracked

180K+

creators indexed

3

platforms covered

Live preview

Current featured creator resolved from canonical tables first, then from source tables.

Instagram Reels

Who is it for

Marketers
Agencies
E-commerce
Trend researchers
Creator managers

Why this is better than frontend mockups

Real source coverage

Cards render from actual app and source tables

Platform-aware fallback

Canonical data first, source tables second

Category reuse

Homepage sections read your taxonomy

DB-backed metrics

Views, creators, plans and previews stay aligned with data

Trending now

Explore by category

How it works now

1. Query creator

Search on `/` resolves a featured creator from available tables

2. Apply fallback chain

Canonical `bloggers/videos` first, then source-specific tables

3. Render real blocks

Homepage sections stay aligned with the data you already ingest

Plans from database

Rendering active rows from the `plans` table when available

Explorer

$29/mo

Starter access for category scans

FEATURED

Pro Scout

$99/mo

Faster research with broader coverage

Unlimited

$299/mo

Deep research and team usage

Frequently asked questions

What data powers this page?
The homepage reads from `bloggers`, `videos`, `categories`, and `plans`, with source-table fallbacks for Instagram, TikTok, and YouTube when canonical rows are not available.
Will it break if canonical tables are still empty?
No. The controller falls back to source-specific tables and then to a small static dataset so the page still loads.
Does search call a new API?
No. The search box currently submits `GET /?q=...` and the controller resolves the featured creator server-side.
Can this be extended to detail pages next?
Yes. The same mapping layer can be reused for profile pages, category pages, and JSON endpoints without changing the current homepage structure.

Use the existing database as the front page source