Skip to content

The hosted event hub for webhooks, devices and live feeds.

Eventeer is a hosted event hub. Point webhooks, WebSocket devices and live feeds at it, and every event is stored, streamed out in real time, and turned into metrics, alerts and dashboards. No infrastructure to run.

Plans from $19 a month. Already have an account? Log in

How events flow through Eventeer: webhooks, WebSocket devices and WebSocket feeds arrive at listeners, every event is stored, then it fans out to live streams, signed webhook destinations, metrics and dashboards, and alerts.
  • WebhooksPOST /in/w/lst_…
  • DevicesWebSocket /in/d/lst_…
  • WebSocket feedswss:// you configure
ListenerEvery event stored and searchable
  • Live streamsWebSocket, replay since
  • DestinationsSigned POST, retried
  • Metrics & dashboards1-minute buckets
  • AlertsThreshold or silence

From first request to live stream in three steps

The same flow works for webhooks, devices and external feeds.

  1. Create a listener

    A listener is where events come in. Pick webhook, device or WebSocket source, and whether callers must authenticate. Do it in the app or through the API.

    Create a webhook listener
    curl -X POST https://app.eventeer.io/api/v1/listeners \
      -H "Authorization: Bearer $EVENTEER_KEY" \
      -H "Content-Type: application/json" \
      -d '{"name":"orders","type":"webhook","auth_mode":"anonymous"}'
  2. Send it events

    Point any service at the listener URL. Each event is stored with its envelope and can be browsed, filtered and replayed for the length of your plan's retention.

    Send an event
    curl -X POST https://app.eventeer.io/in/w/lst_7Qp2xK9vLmN3rT5wY8zA1b \
      -H "Content-Type: application/json" \
      -H "Idempotency-Key: order-1234" \
      -d '{"type":"order.created","amount":42.5}'
    
    # 202 {"id":"0192f3a4-…","duplicate":false}
  3. Use them anywhere

    Subscribe over WebSocket, forward to your own endpoints with signed, retried webhooks, or chart and alert on any numeric field.

    Each frame on a stream
    // wss://app.eventeer.io/out/s/str_…?token=st_…
    {
      "type": "event",
      "id": "0192f3a4-…",
      "listener": "lst_7Qp2xK9vLmN3rT5wY8zA1b",
      "source": "webhook",
      "received_at": "2026-10-31T18:21:04.123456Z",
      "data": {"type": "order.created", "amount": 42.5}
    }

Everything between “received” and “handled”

Ingest, storage, fan-out and observability in one product, for every organization you run.

Events in

Three ways to get data into your organization.

  • Webhook listeners

    Every listener gets its own unguessable URL. It accepts JSON, text and form posts up to 256 KB, dedupes on Idempotency-Key, and can be open, token-protected or HMAC-verified.

  • WebSocket devices

    Devices keep a socket open, send events and get an ack for each one. See which are online and when each was last seen, and push messages down to them from the API.

  • WebSocket sources

    Give Eventeer a wss:// URL, headers and subscribe messages. It connects out, ingests every message and reconnects with backoff when the feed drops.

Inside

Everything is stored, searchable and measurable.

  • Live event explorer

    Filter by listener, device, source, time or JSON contents, open any payload, and replay an event to a destination.

  • Metrics and dashboards

    Count, sum, average, min or max any JSON field in 1-minute buckets. Build dashboards from charts, stats and live event feeds that update as events land.

  • Alerts

    Get notified by email or webhook when a metric crosses a threshold, or when a listener or device goes quiet for N minutes. Incidents resolve on their own.

Events out

Fan out in real time, to browsers, services or devices.

  • Streams

    Clients subscribe over WebSocket and receive matching events live. Reconnect with since to replay what was missed first.

  • Destinations

    Eventeer POSTs each matching event to your URL, signed with HMAC-SHA256 and retried 8 times over about 24 hours. Every attempt is in the delivery log.

  • Per-resource authentication

    Each listener and stream is anonymous or authenticated, with tokens, per-device tokens, scoped API keys or signatures. Anonymous traffic is still rate-limited.

Built for teams and automation

  • Organizations and roles

    All data belongs to one organization. Invite members by email as owner, admin or member.

  • Management API

    A REST API for listeners, events, devices, streams, destinations, metrics, alerts and usage, with read, write and ingest key scopes.

  • Usage you can see

    Track consumption against your quotas, projected overage and your spend cap, live, on the usage page.

Pricing that grows with your traffic

A monthly plan with included events and connection minutes. Go past them and usage is billed as overage, never beyond the spend cap you set.

Starter

$19per month

  • 500k events ingested / month
  • 1M events delivered / month
  • 5 listeners, 50 concurrent connections
  • 5 streams and destinations
  • 7-day event retention
  • 20 events/s per listener, 20 API req/s
  • 3 members
Choose Starter

Growth

$79per month

  • 5M events ingested / month
  • 10M events delivered / month
  • 25 listeners, 500 concurrent connections
  • 25 streams and destinations
  • 30-day event retention
  • 100 events/s per listener, 100 API req/s
  • 10 members
Choose Growth

Scale

$299per month

  • 50M events ingested / month
  • 100M events delivered / month
  • 100 listeners, 5,000 concurrent connections
  • 100 streams and destinations
  • 90-day event retention
  • 500 events/s per listener, 500 API req/s
  • 50 members
Choose Scale

Estimate your monthly bill and compare every limiton the pricing page.

Questions, answered

The details are in the API docs.

Is there a free tier or trial?

No. You can create an account, set up an organization and configure listeners, streams and metrics before you pay. Events are ingested and delivered once a plan is active.

What happens when I go over my monthly quota?

Nothing stops. Usage beyond the included events and connection minutes is billed as overage at your plan's rates, up to your spend cap. You get an email at 80% and 100% of each quota and of the cap.

What happens when I reach the spend cap?

Metered actions are blocked until the next billing period or until you change the cap: webhooks get 402 spend_cap_reached and WebSocket connections close with code 4402. A cap of 0 means no overage at all.

What can I send?

JSON or UTF-8 text up to 256 KB per event. Form posts are converted to JSON. Binary payloads are not accepted.

What delivery guarantees do I get?

Webhook destinations are at-least-once: a delivery counts when your endpoint returns a 2xx within 10 seconds, otherwise it is retried 8 times over about 24 hours. Live stream frames are at-most-once, and a client can reconnect with since to replay stored events it missed.

How do I verify a webhook really came from Eventeer?

Each request carries an X-Eventeer-Signature header with a timestamp and an HMAC-SHA256 of the timestamp and raw body, using your destination's secret. Reject requests older than 5 minutes. Secrets can be rotated without downtime.

What happens if I downgrade or cancel?

Downgrades take effect at the end of the period; resources above the new plan's limits are paused, not deleted. If you cancel, ingest and delivery stop and your data stays readable for 30 days. Your configuration is kept, so subscribing again restores it.

Create your first listener today

Set up your organization and listeners now, choose a plan when you are ready to send traffic.