When to Use Edge

Seuraa Edge is a managed realtime service for delivering application events to connected clients. It makes sense when you need realtime features but do not want to build and operate the delivery infrastructure yourself.

Edge Is a Good Fit#

Use Edge when your application needs one or more of the following:

• Live notifications, chat, activity feeds, dashboards, or collaborative updates.
• Public, private, or presence channels.
• Channel access controlled by your backend.
• Automatic reconnection, with persisted replay available when missed events must be recovered.
• Browser, mobile, and backend SDKs with a consistent channel model.
• Predictable capacity based primarily on concurrent connections.
• Metrics and operational visibility without running a WebSocket platform.

Your application continues to own users, permissions, business rules, and permanent data. Edge carries events between your backend and connected clients.

What You Avoid Building#

A basic WebSocket server is straightforward. A production realtime system also needs:

• Connection lifecycle and heartbeat handling.
• Reconnection, token renewal, and subscription restoration.
• Authorization for every channel and publish operation.
• Cross-server event delivery as the service scales horizontally.
• Presence state across multiple servers.
• Backpressure, rate limits, connection limits, and graceful draining.
• Replay cursors and duplicate-tolerant delivery.
• Metrics, diagnostics, and client SDK behavior across platforms.

Edge provides these capabilities as one service so you can focus on the application you are building. It works whether you are shipping independently or as part of a team.