{"slug": "oncue", "title": "OnCue", "summary": "OnCue launches a self-hosted live blogging tool that lets teams post updates from Slack, Telegram, SMS, or Messenger directly to their own website. The platform supports WordPress, Ghost, and static sites, with no SaaS lock-in, and offers optional AI-powered summaries, polls, and sponsor slots.", "body_md": "OnCue turns your site into a live newsroom. Your team posts from Slack, Telegram, SMS, or Messenger, and your audience watches the story unfold on a page you host, style, and control. Built for WordPress first — and it also works with [Ghost and static sites](headless.html).\n\nBring your own keys · Bring your own AI · **No SaaS lock-in**\n\nMade For\n\nDifferent jobs, same tool. Here's what OnCue does for each.\n\nRun product drops, launch days, AMAs, and watch-alongs live on your own site — and turn viewers into participants instead of a comment count on someone else's platform.\n\nPost breaking updates from your phone over Telegram or plain SMS — no CMS login on the courthouse steps. Your archive lives on your domain, cited and timestamped.\n\nPost from the launch Slack channel, let every published update land in Teams or Google Chat on its own, and give customers a branded live page to follow.\n\nCover conferences, matchdays, earnings calls, and keynotes as they happen. The live page carries your polls and your sponsors — and it stays up afterward as the record people cite.\n\nNo new dashboard for your team to learn, and no content leaving your site. This is the whole loop.\n\nA message in the connected channel is the update — text, photos, and video. No new tools to learn.\n\nEach message becomes a published update under the author's name — held for review first if you want.\n\nUpdates appear on your page without a refresh — and can share themselves to the channels you pick.\n\nSetup is three steps: create an event in WordPress, drop the OnCue block into a post, and connect a channel. The [Admin Guide](guide.html) walks through every click.\n\nPublish on Ghost, Hugo, Next.js, or plain HTML? Run OnCue as a small live engine on a subdomain you own. Your team still posts from chat, and the full stream — or any single update — embeds on your site with a copy-paste snippet.\n\nA lean core that's always on, plus modules you turn on only when you need them. A module you haven't enabled adds nothing at all.\n\nLive updates served by your own server — no third-party service in the middle. Readers get a page that's fast, crawlable, and styled by your theme.\n\nContributors file from Slack, Telegram, SMS, or Messenger — text, photos, and video, with their own byline. No CMS login required in the field.\n\nA cited, auto-refreshing summary grounded only in your event's own updates — no made-up facts or links. Bring your own key for Claude, OpenAI, or Gemini, or point it at a model you host yourself. Editors can edit or pin every line.\n\nDrop a poll into any update and watch the votes come in live. Then let every entry travel as a rich share card set in your own typeface.\n\nSearch public Bluesky posts and YouTube videos about your event right from the composer, and drop the best ones into the stream without leaving the console.\n\nEvery published update can post itself into your team's Slack and out to Signal, Teams, and Google Chat — no copy-pasting, no duplicates. The moments you choose thread onto your Bluesky account.\n\nAn optional review step holds updates until an editor clears them — per event or per source — so an open channel never means an open mic.\n\nSell the moment: clearly labeled sponsor cards appear between updates at a rhythm you set, with optional start and end dates. Or plug in your own ad stack and let it fill the slots.\n\nReader activity flows through your own Google Analytics tag — OnCue collects nothing itself. A per-event stats screen shows readers, engagement, and poll results in one place.\n\nEvery key you paste is encrypted at rest, and the encryption key is kept outside your database. Your content and credentials never touch our servers.\n\nOnCue ships the connections — the accounts and keys are yours.\n\nEvery connection runs on credentials you create — so usage bills at each platform's own rates, with no middleman and no markup. Keys are encrypted at rest, and the encryption key stays out of your database.\n\nOnCue is a lean core plus optional modules. A module you haven't enabled adds nothing — no settings clutter, no background jobs, no open doors. Turn features on as your coverage grows.\n\nRestyle the reader with CSS variables, hand sponsor slots to your own ad stack, send reader activity to any analytics tool, and run AI highlights on any model with an OpenAI-compatible server — even one on your own hardware.\n\n**Bring your own keys.** Nothing turns on until you connect your own accounts — that's the whole model. [How BYOK works →](faq.html#byok) · [Step-by-step setup guide →](guide.html)\n\nDownload the plugin, upload it to your site under Plugins → Add New → Upload Plugin, and you're live. OnCue is in open beta — the download is free while testing continues, and a staging site is the smart place to start.", "url": "https://wpnews.pro/news/oncue", "canonical_source": "https://oncue.thelettertwo.com/", "published_at": "2026-07-10 17:08:13+00:00", "updated_at": "2026-07-10 17:35:29.019966+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools"], "entities": ["OnCue", "Slack", "Telegram", "WordPress", "Ghost", "Claude", "OpenAI", "Gemini"], "alternates": {"html": "https://wpnews.pro/news/oncue", "markdown": "https://wpnews.pro/news/oncue.md", "text": "https://wpnews.pro/news/oncue.txt", "jsonld": "https://wpnews.pro/news/oncue.jsonld"}}