Nightcap Media, social content operations with source-backed proof.

Nightcap Media is documented as a full-stack social media management platform: campaign briefs, AI-assisted content, scheduling, multi-account handling, analytics, review management, and a separate Nightcap outreach identity for social-media-focused prospecting.

11API route groups
13database migrations
4social targets
6AI models supported

Break Room portfolio Nightcap Media case study page showing Nightcap Media title, social media management platform subtitle, and hero image

Proof Surfaces

The page now shows Nightcap itself, the source case card, and a cleaned system map.

These artifacts come from the local Break Room portfolio source and the Nightcap-specific outreach configuration. The old unsupported account, platform, test-count, and client-portal claims were removed, and the low-resolution work-card crop has been replaced with a crisp expandable proof card.

Nightcap Media case study screenshot from the Break Room portfolio — Source case study The source page positions Nightcap as a social media management platform, not a borrowed or generic proof image.

Nightcap Media work card proof showing full-stack SaaS build, campaign scheduling, content calendars, publishing, analytics, and case-study scope — Portfolio work card The work index proof is now a sharp public-safe card: complete social media platform, campaign scheduling, calendars, publishing, analytics, SaaS platform, and full-stack build.

Nightcap Media system map showing campaign briefs, AI production, scheduler, publishing targets, analytics, review management, and outreach identity — System map The architecture view was rebuilt around verified source lanes: briefs, AI production, scheduling, publishing, analytics, reviews, and outreach identity.

Platform Scope

Campaign planning, content production, publishing, and measurement stay in one product loop.

The source case study describes a full-stack build rather than a thin marketing wrapper: backend routes, migrations, account isolation, campaign workflows, social APIs, and a public Next.js surface.

Campaign engine

Express API server backed by SQLite and 13 recorded database migrations.
Campaign briefs drive content planning before posts move into scheduling or publishing.
Multi-account management keeps credential handling and client context separated.
Cron-based scheduling uses analytics-informed timing with documented fallback behavior.

AI content pipeline

Gemini-backed generation covers text, image, and video in the source case study.
Per-model cost tracking is part of the platform scope, so output cost remains inspectable.
Brand voice, industry, and account context shape generated captions and creative direction.
The public page avoids unsupported exact model-version claims.

Publishing and analytics

Publishing support is documented for Facebook, Instagram, Twitter, and Stories.
Analytics use Meta Graph API and Twitter API v2 for engagement, reach, impressions, and timing feedback.
Review management includes local sentiment analysis, ratings, source filters, and featured-review flags.

Outreach Identity

Nightcap also exists as a social-media-focused client lane in the outreach engine.

Nightcap project config

The multi-client outreach system supports --ai-project nightcap for Nightcap-specific prompts.
The qualifier focuses on businesses with missing, inactive, or weak social media presence.
Email, form-message, and follow-up prompts are written in the Nightcap voice rather than Break Room's website-audit voice.
Private sender details and the placeholder business address stay out of the public proof page.

Shared controls

Client configs live under clients/{slug}/config.json with separate identity, prompts, and branding.
Campaign records define project slug, search query, schedule type, day, hour, and enabled state.
The scheduler checks for due campaigns every 60 seconds and queues pipeline jobs with concurrency guards.
Nightcap parity docs mark Places source, preflight, Lighthouse, CLI/API/queue, and test paths complete.

Public Claim Boundary

What changed: the page no longer repeats unsupported operating claims.

The old page overreached. This pass keeps the source-backed platform shape and removes claims that were not confirmed in the local Nightcap source scan.

Removed

No managed-account count is published without source confirmation.
No speed claim is made for a complete monthly calendar.
No platform test-count claim is presented as Nightcap proof.
No affiliate network, TikTok, LinkedIn, or private account list as current proof.

Reframed

The source case count supports 11 API route groups and 13 migrations.
The 4 social-target and 6 AI-model numbers are treated as case-study scope, not live account claims.
Review and sentiment management are described from the source case study, not as an unsupported client-portal claim.

Kept private

Nightcap sender addresses and unsubscribe addresses are not published here.
The placeholder Louisville street address in the config is not treated as a real public business location.
Social account setup todo items are not presented as completed external account operations.

Stack

Express, SQLite, Gemini, Meta Graph API, Twitter API v2, and Next.js.

Express 5
SQLite
Node-cron
Gemini AI
Meta Graph API
Twitter API v2

Google Cloud Storage
Helmet
Rate limiting
Next.js
React
Vercel

Need a content system with claims that survive source review?

That takes more than a prompt: campaign state, account boundaries, publishing rails, analytics feedback, and public proof all have to line up.

Email Rarity Index