What Feed is#
Feed is the part of the ecosystem that answers "what should I write next?". It pulls in multi-source industry signal, RSS first, with scraped sites, YouTube, Reddit, and newsletters as it grows, and turns a noisy stream into a short, ranked list of content opportunities worth acting on.
It is a supplier, not a destination. Feed finds and surfaces; the writing happens elsewhere. On its own it is a focused curation tool; alongside the other Gillish tools it becomes the front of a content pipeline.
Finder, not creator#
- It finds; it does not write. Feed ingests, scores, and surfaces content opportunities. It does not draft articles or generate media, content creation is a separate Gillish concern, by design. Keeping Feed to one job keeps it honest and keeps it free.
- It spots gaps with Node. Better-together with Gillish Node, Feed compares the signal it finds against your site's actual structure and surfaces what you are missing, not just what is trending. Standalone it still works; with Node it gets sharper.
- It hands off. The opportunities Feed identifies are passed to whichever tool does the writing. Feed's responsibility ends at "here is what is worth saying, and why".
Free forever, AI-free#
Feed has no Pro tier, no licensing layer, no upgrade screen, and no feature gating, permanently. That is a deliberate house exception, not a launch-pricing trick.
It holds because Feed's free baseline is AI-free: ingestion, manual curation, and manual export cost nothing to run, so there is nothing to meter. Any AI scoring or automation is a better-together layer that other Gillish tools bring, or a per-user bring-your-own-key fallback. Feed itself never hosts an AI service and never carries that cost, which is exactly why it can stay free without a catch.
Where Feed stands today#
The honest current state:
- A scaffold, not a tool yet. The plugin boots and registers its admin surface (a curation dashboard shell and a settings screen), but the engine behind it is not implemented, the feed pull, the scoring, the export transport, and the refresh cycle are stubs.
- Only the seed is sketched. What exists is the lightweight starting point, an RSS list, a Copy-for-AI string, and a webhook export shape. The broader content-engine ambition is captured in the product vision, not built.
- Deliberately parked. Feed is not stalled; it is sequenced. Cairnstone and Node ship first; Feed resumes after, built on the finder scope rather than the original lighter sketch.
What comes next#
When development resumes, Feed grows from the seed into the full finder: real multi-source ingestion, scoring of what is worth writing, content-gap detection paired with Node, and a clean hand-off to the ecosystem's creator side. None of that is claimed here before it ships, this page moves only when real work lands, the same as every other status surface on this site.
The full parked ambition, the finder scope, the modules, the better-together-with-Node seam, and the open questions left deliberately undecided, is set out in the Feed product vision. Where Feed actually stands on GDPR, CCPA, the CRA, OWASP and WCAG 2.2 AA is the security & compliance posture.
For the other tools, see the rest of the ecosystem: Cairnstone, Node, Mesh, Core, or the toolset overview.