Home

Welcome to Lynx: The Future of Real-Time Database Streaming

Stop Polling. Start Streaming.

For years, developers have relied on "polling" (querying the database every few seconds) or "database triggers" to create real-time experiences. Both methods are flawed: polling creates unnecessary load and high latency, while triggers are hard to maintain and slow down write operations.

Lynx solves the problem of high-latency database polling by using Postgres Logical Replication.

Why Lynx?

Lynx operates at the infrastructure level. Instead of asking the database for changes, Lynx sits quietly next to your database and listens to the Write-Ahead Log (WAL).

• Sub-millisecond Latency: Data moves from the database disk to the connected client in the blink of an eye.
• Infrastructure Agnostic: Works with any standard Postgres installation (AWS RDS, Google Cloud SQL, or local Docker).
• Developer First: Plug-and-play binary that provides a clean WebSocket API for your frontend.

Key Features

• Zero Query Overhead: Lynx reads the logs directly; it doesn't run SELECT statements.
• Topic-Based Multiplexing: Clients only receive data for the specific tables they are authorized to see.
• Binary Efficiency: Uses Go’s high-performance networking stack to handle thousands of concurrent connections.