[ RESEARCH_OPERATIONS ]

Self-Hosted Reading & Research Client

2025Data Pipelines & AutomationCapability

What it is

A private feed reader with full-text search and annotation.

Client work is shown without identifying imagery

[ THE_PROBLEM ]

Why this existed

Competitive intelligence gets done in a browser with fifty tabs and no record. The article that mattered six months ago cannot be found.

[ WHAT_WE_BUILT ]

What we built

Feed subscription and fetching, read and saved state, per-article notes, and full-text search across everything ingested — with a schema-managed Postgres backend and its own auth.

Feed subscription and scheduled fetching
Read and saved state per article
Per-article notes
Full-text search across everything ingested
Schema-managed Postgres backend with its own authentication

[ HOW_IT_IS_USED ]

How a company uses it

A research or competitive-intelligence function keeps its sources, its reading state and its own notes in one searchable place it controls.

Built with

SvelteKitDrizzlePostgresArgon2

[ COMMON_QUESTIONS ]

Questions clients ask

Why self-host a feed reader?

For control over what is retained and searchable. Hosted readers come and go, and the annotations are usually the most valuable part — losing them with a shutdown is a real risk for a research function.

Why store notes alongside articles?

Because the note is the analysis. An archive of articles without the reasoning about them is a bookmark folder.

Is RSS still relevant?

For monitoring specific sources, more than ever — it is the remaining channel where you control what you see rather than an algorithm choosing for you.

[ RELATED_WORK ]