Reference

Data model reference

Internal map of the 51 application and MCP OAuth tables.

InternalInternal

Table groups

DomainTables
Coreprofiles, videos, analyses, usage_tracking, analysis_chats, analysis_embeddings, analysis_frame_embeddings, retention_accuracy, retention_diagnoses, pre_publish_sessions
Research & DNAcreator_platforms, creator_library, creator_dna, competitor_library, competitor_snapshots, competitor_watchlist, comment_insights, radar_watchlists, youtube_search_cache, gap_finder_searches, trend_match_searches, weekly_missions
Creation & performanceviral_plans, blueprint_tracking, dna_decision_ledger, hook_generations, title_generations, script_analyses, thumbnail_analyses, thumbnail_generations, version_generations, comparisons, content_experiments
Team & integrationsteam_members, team_invitations, integration_connections, webhook_deliveries
Billing & operationsrate_limits, cron_rate_limits, plan_change_log, stripe_webhook_events, revenuecat_webhook_events, signup_fingerprints, video_credits, oauth_transactions, platform_waitlist
MCP OAuthoauth_clients, oauth_authorization_codes, oauth_tokens
Retired mediavideo_generations, voice_clones

Access model

  • User-facing data is protected with RLS and explicit ownership or workspace primitives.
  • Service-only tables and privileged RPCs are revoked from anonymous and authenticated roles.
  • MCP OAuth tables use a locally typed service-role client because the generated database types do not yet contain them.
  • Schema documentation must be regenerated after the deployed migration ledger is reconciled.