The founder suite
One backend.
Three surfaces.
Viralr is the socials and paid-ads surface of a three-product suite. All three run on one backend on Hetzner. One install arms all three. The same voice profile, topic engine, and audience signals route across every surface. Your presence sounds like one person, because it is.
Marketed standalone. Sold standalone. But when you run npx viralr init, a single /connect arms organic socials, paid ads, SEO articles, and email outreach under the same API key. Three domains. One operating layer.
Each is sold standalone. All three run together.
Each surface has its own domain, its own landing page, its own pricing page. But the engine behind them is shared. Voice learned once, used everywhere. Topic engine run weekly, pipes into every surface. Audience signals compound across the three.
Platform-native threads, scheduled posts, short-form clips, paid-ad creative on Meta, X, LinkedIn, TikTok, Reddit, Google. One thread reshaped for every feed. Engagement signals pipe back to the topic engine.
Research-backed articles, platform authority, cross-site shaping, GSC-driven auto-heal. The hub of the suite. Docs, billing, and legal live here.
Newsletters, transactional reach-outs, sequenced outreach. Inbox warming, voice-matched drip sequences, reply routing. Email surface of the same engine.
Every signal on one surface sharpens the other two.
Buying three separate tools gets you three separate silos. Everything you learn on one is lost to the others. The founder suite is one backend, so every signal compounds. Here is how, specifically.
The threads that land on X and LinkedIn this week seed networkr's next SEO article on the same topic. You don't pick what to write about. The audience already told you.
Keywords winning on Google feed viralr's topic selection. If a networkr article is ranking for 'Postgres session state', viralr writes a thread from the same angle, shaped for X, LinkedIn, Threads.
Engaged social followers flow into outboxr's newsletter list automatically. Not scraped. Opt-in through a viralr bio link, deduped, tagged with the platform they followed from.
Newsletter open-rates and click-throughs tell viralr which threads to re-amplify and which ad creative to push harder. If an email hook gets 40% opens, the same hook gets paid-ad budget.
Paid ads re-engage readers who bounced off SEO. Networkr knows which pages got traffic but no conversion. Viralr-ads runs retargeting creative to bring those readers back.
Cornerstone articles become the backbone of outboxr's welcome sequence. New subscribers get the best of your existing research as a seven-day drip, shaped in the same voice.
None of this is bolt-on integration. There is no Zapier step, no webhook to wire up, no API token to copy. One backend. The data already lives together. The signals route themselves.
One /connect arms all three.
You do not install three products. You install one. The CLI and the brief both route through the same /connect endpoint, which arms whichever surfaces you opted into. Default: all three.
Email: you@company.com
Surfaces: viralr, viralr-ads, networkr, outboxr
Platforms: x, linkedin, threads, bluesky
Ad networks: meta, linkedin
(stored once, never shown again)
Each surface can be disabled independently. The surfaces array in /api/connect selects what is armed. Default is all four. Drop any one and the others keep running.
Billing, legal, voice: all shared.
Pro on any surface unlocks Pro on the whole suite. Stripe customer and invoices live on networkr.dev, the billing hub. $2–8 per site depending on volume.
The same Terms, Privacy Policy, and Acceptable Use Policy apply across viralr, networkr, and outboxr. Mirrored on each domain; all three update together. Operated by Heimlandr (Sweden).
The voice profile you tune once (persona, tone, banned words) shapes every thread on viralr, every article on networkr, every email on outboxr. Your presence sounds like one person, because the engine is one engine.
Three products. One install.
Connect once. Socials, paid ads, SEO, and email run themselves on the same backend.