Self-hosted Content Distribution Engine that runs two live production sites. One admin spans blog, podcast, events, portfolio, courses, books, downloads, microblog — with persona-decoupled identity, ten composable access gates, and a three-tier agent architecture for automated content pipelines.
Publishing across blog, portfolio, podcast, events, books, courses, and downloads usually means stacking three to five SaaS subscriptions, each with its own admin, its own billing meter, and its own audience silo. Arcturus collapses all of it into one self-hosted engine — one database, one admin, one infrastructure bill — and ships content out through twelve external channels automatically. Two production sites have been running on it for ten weeks across five validated wipe-and-redeploy cycles; the same codebase powers both.
Operators who publish in more than two formats — blog posts plus a podcast, or a project portfolio plus a course catalog — quickly discover that no hosted platform covers all of it. Substack handles a newsletter but not a portfolio. Ghost handles a blog but cannot run an event calendar with recurring occurrences modeled as one canonical URL. Medium owns the audience and forbids agentic publishing. WordPress runs everything if you accept a plugin marketplace, generic templates, and a maintenance tax that compounds with every plugin update.
Add a credible cybersecurity, OSINT, or trading-research output and the problem hardens. Provocative content gets flagged on hosted platforms; agentic ingestion (an AI agent posting market analyses on a schedule) is unsupported or rate-throttled; audience data is owned by the platform and cannot be exported as anything richer than an email list. The realistic alternative — a custom build per surface — costs $40,000 to $120,000 per deployment and rebuilds the same admin panel from scratch each time. A solo operator publishing across four surfaces is looking at $160,000 to $480,000 of duplicated build cost plus ongoing maintenance, or a stack of SaaS subscriptions that locks them out of the data their own content generates.
The moment this hurts: the third time in a week an operator opens four browser tabs to publish one piece of content across blog, podcast feed, event calendar, and social, and realizes the same admin panel could have done all of it.
Arcturus is a single web application that handles every kind of publishing under one roof. One admin panel writes a blog post, schedules a podcast episode, adds a recurring event, drops a project to the portfolio, ships a course, hosts a download with email gating, or fires off a short microblog "thought" — and the same engine pushes that content out to RSS, sitemap, Telegram, Mastodon, Bluesky, social-image Open Graph renderers, webhook subscribers, and any agentic listener wired in via API key.
The operator owns the database, the domain, the SSL certificate, and every reader email. A Persona layer decouples the public byline from the login account, so a single architect can publish under several distinct identities without exposing the real-name brand to any one of them. Ten composable access gates — public, readers, PRO, password, scheduled, early-access, geo-restricted, reader-drop, time-expiring, reader-group — sit orthogonal to the content type, so a podcast episode and a research download and an event can each carry the same gate semantics. An admin-managed kanban board lives in the same interface for bug and idea tracking; the operator never context-switches into a separate tool to record what shipped.
It fits into existing infrastructure without forcing a rewrite. The engine sits behind a host-level nginx and certbot setup that fronts unlimited domains on one VPS — adding a new site is one config block and a DNS record, not a new server. Operators already running a portfolio and a research blog as two separate SaaS subscriptions can consolidate both onto one deployment without losing any feature they paid for.
config.ini, run ./deploy.sh --ssl, point DNS. Same engine, fully distinct visual identity, isolated database per tenant.Arcturus lands hardest in three contexts. First, solo systems architects publishing across four to six output surfaces — the operator who would otherwise pay for and context-switch between five SaaS dashboards. Second, small product shops running multi-client publishing pipelines — each tenant gets a deployment that feels custom because the theme system and Master Page primitives genuinely make it custom, while the shop maintains one codebase across all of them. Third, research and intelligence operators with agentic content pipelines — cybersecurity, OSINT, and trading-research desks that need a permanent, owned publishing surface for outputs hosted platforms will eventually flag or throttle, plus a credentialed API for the agents that actually generate the content. The common thread: situations where a publishing surface has to last five years, survive policy changes that are out of the operator's hands, and consume content from machines as well as people.
/men-circle-bkk is permanent; past and future occurrences compute at render time from a recurrence pattern. No duplicate-content SEO penalty, no per-occurrence cleanup, links stay safe to share forever./welcome, /money, /research-xyz) as a real React component committed to the repo, with optional bottom-of-page filtered blog feed and full chrome control. Mirrors the outbound-agent plugin pattern; every new template is PR-gated.The foundations are deliberately boring. Next.js 15 with the App Router, React 19, TypeScript, Prisma 6 against PostgreSQL 16, Docker Compose, system nginx, Let's Encrypt. Every secret lives in one config file; every container binds to localhost; one nginx routes by Host header to as many domains as the operator wires up. The whole stack runs on a single VPS, an on-premise box, or an air-gapped environment with no SaaS dependency for any critical path. Twenty-eight build sessions in, the codebase compiles with zero TypeScript errors and ships with 781 jest tests across 63 suites — sized to be audited by one architect in an afternoon, not maintained by a team.
Arcturus is in active production. Two live deployments — rist.sh and ristmind.com — have been running on the same codebase for ten weeks across five validated wipe-and-redeploy cycles. Build marker session-28-validated is live on both as of 2026-05-22. The engine carries roughly 565 features across 28 build sessions starting from early March 2026, with 90,000 lines of TypeScript and TSX, a 1,400-line Prisma schema covering 48 models, and 781 jest tests across 63 suites green on every recent run. Three items remain explicitly deferred and called out as such: a transactional-email provider (Resend / Postmark / SES — the missing piece for email-side lead-magnet delivery), Stripe-backed PRO subscriptions (the Reader.isPro flag is currently a manual toggle), and a multi-site tenancy refactor (each deployment today runs its own database; the multi-tenant rebuild is held back until live-site count justifies it).
Three near-term milestones convert the existing engine into a paid platform. First, transactional-email integration completes the lead-magnet flow — Meta Pixel Lead event fire, post-download file delivery, weekly digest, per-project follow notifications — turning the existing capture pipeline into a closed-loop email engine. Second, Stripe-backed PRO subscriptions convert the existing PRO gate into actual monetization with checkout, dunning, and reader-status sync. Third, multi-site tenancy (the N20 refactor) lets one engine instance serve many independent sites under one database, opening the agency-as-customer revenue line where one provisioning step onboards a new tenant instead of a full redeploy.
The longer arc tilts Arcturus toward a partner-facing managed offering. The three-tier agent architecture is already prepared for it; the remaining gaps are deployment automation, billing, and a partner admin tier above the current GOD_ARCHITECT role. Several research and intelligence operators have signaled interest in running agentic-content desks on the engine — the next six months move it from solo-operator-grade to small-team-and-agency-grade.
Arcturus is available in three engagement modes. Founders or operators who want a similar build for their own publishing surface can commission a tailored deployment — same engine, custom theme, custom Master Page templates, fully owned codebase. Existing product teams can engage on extension work — adding a missing block type, integrating a new outbound channel, or wiring a custom agent into the inbound API while keeping the rest of the codebase untouched. Investors, partners, and adjacent platform operators can engage in strategic advisory — methodology review on multi-template content engines, agent architecture for content pipelines, or technical due diligence on a similar build. Reach out via sintegrium.io or LinkedIn for a 30-minute scoping call.
Built by Yurii Staryk · Solution Ecosystem Architect
Self-hosted YouTube-to-text pipeline — faster-whisper runs on a home GPU inside Docker, callable from any laptop on the LAN. Own your transcripts, no API fees, no rate limits, 99+ languages.
Self-hosted LAN clipboard for engineers running multiple machines on one network — paste text or files on one device, grab on another, with auto-expiring slots for API keys and zero internet dependency.
A desktop wizard that authors complete cognition bundles — identity, skills, credentials, runtime memory — for multi-agent AI teams, sealed with AES-256 and ready to deploy to any runtime.