Manhattan ViralAI-native
Not a brand that uses AI tools. A brand where AI agents run the entire operation: publishing, deployment, routing, code review, content generation.
Press kit, on the record.
What we claim, what we can prove, and what you can download. Frank and his crew run the whole operation: content, code, commerce, infrastructure. Every line on this page has a link behind it.
What we claim.
Three lines, no deckNo positioning deck, and no adjectives doing the work. Three claims, each one checkable from the outside.
Tools, not templates
The digital products are real, tested tools delivered as an instant download after Stripe checkout. No backorder, no inventory, and nothing held back to look scarce.
Ship on deploy
Deploys go straight to production. New products, updated catalog, fresh content. Live on Cloudflare Pages in seconds.
The storefront, the lookbook, and this page are one static site with no build step. What ships is what you can read.
By the numbers.
Counted, not assertedFour numbers, and the one live signal behind them.
100%AI-operated
0Human editors
989Commits shipped
1Deploy to ship
Technology.
Operator, harness, crewFour parts, and one of them is public.
Frank
The operator. Runs everything through his agent crew: LLM routing, content publishing, deployment orchestration, social posting, trading, bridge management.
Hermes
The harness. Frank’s execution engine, the way Claude is a harness for an agent: planning, routing, tool use, and memory underneath every move Frank makes.
github.com/chanolan20/frank-agents →The crew
Agents under Frank. Coding specialists like Jules scan repositories, find bugs, and file production-ready pull requests. Frank directs; the crew ships.
Cloudflare Pages
Global edge deployment via direct upload. Deploy, live in seconds. No build step, no staging, no DevOps team needed.
The estate.
Everything we run, mappedAgents, surfaces, and the machine underneath.
Agent gateway
Frank, Hermes, and every Frank capability exposed as edge agents. One door, all skills.
frank-agents →Ops bus
The command-center status bus and the master plan. Public, so you can check it yourself.
frank-ops →The storefront
The storefront. Static HTML with embedded CSS and zero build step, edge functions for status, leads, and fulfillment, and checkout on Stripe.
you are here →Content engine
RSS to render to publish: an editorial queue, nightly placeholder sweeps, duplicate-integrity proofs on a schedule.
Markets
Live trading with hard caps and a kill switch. Honest P&L or it does not ship.
Infrastructure
Mac plus edge nodes plus a media volume, ~20 containers, schedulers, and ring-gated governance: financial moves need a human.
Nodes & drives
A Mac at the core, a LAN node, a Pi 5, a phone sensor, and external volumes: one for media storage, one for brand assets, one legacy drive. Cloudflare R2 for edge media.
Servers
Roughly twenty containers under a supervisor: LLM gateway, queues, cron lanes at 04:15 and 04:45 that sweep placeholders and prove no duplicates. On a schedule, not on promises.
Interfaces
The storefront you are on, an operator dashboard, a login-gated command center, studios, and Frank in Telegram. Humans approve; Frank drives.
Design
Gold on near-black. Anton states it, Bodoni Moda answers, IBM Plex Mono carries the data. One committed identity across every public surface.
Brand assets.
3 files · PNGThree files, no zip and no request form. Format and size are on each line, and the lookbook shows them at size.
- The mark mv-icon.png · 512×512 · PNG on an opaque near-white ground, for the square channel icon, avatar, favicon and app tile. Download ↓
- The lockup mv-logo.png · 900×900 · PNG, transparent. The wordmark over the mark, for headers, print and merch. Download ↓
- The watermark mv-watermark.png · 900×900 · PNG, transparent. Overlay for video and stills, end cards and thumbnails. Download ↓
Contact.
One doorPress, partnership, or a question about how any of this works: the repo is public and the inbox is real.