Every external change,
delivered to your AI agent
Aggregate webhooks, RSS feeds, webpage changes, and social media updates into a single event stream. Your local agent polls, consumes, and reacts — no open ports, no tunnel setup.
One inbox for every change
Push webhooks and polled sources converge into a durable queue. Your agent pulls events on its own schedule — nothing is lost when it goes offline.
Sources we aggregate
From developer webhooks to content feeds and webpage monitors — everything lands in the same queue.
GitHub
AvailablePush events, pull requests, issues, releases, and deployments.
Stripe
AvailablePayment intents, subscriptions, invoices, and dispute events.
Custom Webhook
AvailableAny service that can POST JSON — Shopify, Linear, Slack, and more.
RSS / Atom
RoadmapNew posts from any blog, podcast, or news feed, polled on a schedule.
YouTube
RoadmapNew video uploads from channels you subscribe to.
X / Twitter
RoadmapNew posts from accounts you follow, delivered as structured events.
Webpage Monitor
RoadmapDetect content changes on any URL — price drops, restocks, updates.
Email Inbox
RoadmapParse incoming emails as events your agent can react to.
Built for local-first agents
A lightweight Cloudflare Worker that gives your desktop agents a durable, public inbox.
Unified event stream
Webhooks, RSS, and webpage changes all land in the same queue. Your agent sees one consistent event format, regardless of source.
Persistent & durable
Events are stored in Turso and survive gateway restarts. When your agent comes back online, it picks up right where it left off — nothing is dropped.
Dual-token security
Webhook tokens let platforms send events. Consumer tokens let your CLI poll them. Role-based routes keep each token where it belongs.
Instant public URLs
Each subscription gets a unique endpoint. No port forwarding, no tunnel setup, no exposing your machine to the internet.
CLI forwarding
Install the CLI, log in with your consumer token, and point it at any local URL. Events stream to your agent in seconds.
Open source & self-hostable
Deploy the Worker to your own Cloudflare account. You control the data, the domains, and the limits.
Get started in three steps
- 1
Create a subscription
Sign in to the console and create a subscription. You get a public webhook URL and a consumer token for the CLI.
- 2
Connect your sources
Paste the webhook URL into GitHub, Stripe, or any service that can POST JSON. For RSS, YouTube, and webpage monitors, configure them in the console — the gateway polls on your behalf.
- 3
Forward events to your agent
Run the CLI and point it at your agent's local endpoint. Events arrive as POST requests — acknowledge each one once your agent has handled it.
# Install the CLI
npx event-gateway login --token <your-consumer-token>
# Forward incoming events to your local agent
npx event-gateway start --target http://localhost:8673/hooks/agentOpen source and self-hostable
Deploy the Worker to your own Cloudflare account. You control the data, the domains, and the limits.
Deploy your gatewayFrequently asked questions
What is change detection for AI agents?
It is the practice of monitoring external sources — webhooks, RSS feeds, webpages, social media — for changes, then delivering those changes as structured events to a local AI agent. SignalFeed is the infrastructure that makes this possible without exposing your machine to the internet.
How is this different from a webhook relay?
Webhook relay services forward HTTP requests to your machine in real time. If your machine is offline, the event is lost. SignalFeed takes a different approach: it persists every event in Turso, and your agent polls on its own schedule. Nothing is dropped, and no inbound connection is ever needed.
How is this different from changedetection.io?
changedetection.io monitors webpages and sends notifications to humans via Slack, Discord, or email. SignalFeed aggregates many source types — not just webpages — and delivers structured events to an AI agent via a CLI, so your agent can programmatically react to changes.
Do I need to open a port on my machine?
No. Your agent listens on localhost and the CLI polls the gateway for events. The gateway never connects inbound to your network.
What happens when my agent is offline?
Events accumulate in the gateway's Turso-backed queue. When your agent comes back online, the CLI resumes polling and drains the queue. You can acknowledge events individually to mark them as consumed.
Can I self-host it?
Yes. The entire stack is open source and runs on Cloudflare Workers and Turso. You can deploy it to your own account in minutes.
Which sources are available today?
GitHub webhooks, Stripe webhooks, and any custom service that can POST JSON are fully supported. RSS feeds, YouTube, X / Twitter, webpage monitoring, and email are on the roadmap — the architecture already supports them, connectors are being built.