Stable multi-source ingestion
Google / Jina / Firecrawl search, RSSHub with two-layer failover, IMAP email, inbound webhooks, Google Drive, and scholarly databases — every collector ships with health checks and retry policies.
OctoReport is built for real workloads, not demo dashboards — multi-source ingestion, AI cleaning, versioned content, and atomic billing, each engineered for data consistency, observability, and fault tolerance.
No credit card · 10,000 free credits
Ingestion, content, billing — every stage is built to production standards, not demo standards.
Google / Jina / Firecrawl search, RSSHub with two-layer failover, IMAP email, inbound webhooks, Google Drive, and scholarly databases — every collector ships with health checks and retry policies.
URL-level deduplication: a successful re-collection supersedes the old version, a failure only updates the timestamp. Reports read valid versions only, and every change is traceable.
Credit deduction runs in transactions with row locks and automatic compensation. Every LLM call gets its own log; every balance change leaves a transaction record.
Every stage of the pipeline owns its responsibility — and its observability.
Google · Jina · Firecrawl · RSS · email · webhooks · Google Drive · scholarly APIs · tech communities, all under one collector spec.
Embedded and external instances switch automatically by priority. Relative paths like /rsshub/github/trending work out of the box.
Your custom prompt plus a choice of models extracts titles, summaries, and key fields while filtering ads and navigation noise.
Duplicates are detected by normalized URL: a successful re-collection expires the old version, and reports read unexpired content only.
Drag-and-drop step configuration with variable injection ({library:N} {source:N} {step:N-1}); each step feeds the next.
BullMQ queues process asynchronously with RETRYING and FAILED as distinct states, per-step timing, and instantly visible failure reasons.
Every query is filtered by userId, API keys are stored with AES-256-GCM encryption, and routes are permission-guarded.
Per-call or per-token pricing inside atomic transactions — failed charges roll back. Every cost is traceable, and balance pre-checks prevent overspend.
Interval, weekly, or cron. Failed tasks retry up to 3 times with exponential backoff, with email alerts on failure or low balance.
When a collector fails, it should be able to explain why — not silently leave your morning report blank.
From UI to storage, from collection to delivery — every layer is explicit, and every stage is observable, retriable, and reversible.
Actual captures from the console and share pages, taken July 2026.


Sign up and run on real data: get your first collector live and your first report in your inbox — not a demo, but the report you will actually read next Monday at 8 a.m.
10,000 free credits · No credit card · Export your data anytime