Product

What problems we solve

Realtime is easy to demo — hard to run in production

Building realtime features sounds simple — until you hit production.

At a glance

Three reasons teams choose ApexStream

Use cases

Same transport — outcomes that matter

The hands-on cloud flow is in See it in action below — dashboard, SDK, and wss://api.apexstream.org.

export function reconcileOrder(order) {  const status = order.paid ? "ready" : "pending";Mia   return { ...order, status };}

From client connection to operations

One product story: gateway, control plane, and dashboard

import { ApexStreamClient } from "@apexstream/client";

const wsUrl = import.meta.env.VITE_APEXSTREAM_WS_URL!;
const apiKey = import.meta.env.VITE_APEXSTREAM_API_KEY!;

const client = new ApexStreamClient({
  url: wsUrl,
  apiKey,
  allowInsecureTransport: wsUrl.startsWith("ws://"),
});

client.connect();

const unsubscribe = client.subscribe("orders", (payload) => {
  console.log("orders event", payload);
});

client.publish("orders", { kind: "placed", id: "ord_123" });

unsubscribe();
client.disconnect();

Built for production

Ship traffic you can operate — not a demo you hope will scale

ApexStream is designed for systems that are already in production, with visibility, control, and operational safety built in from day one.

• Scale without client changes

  Add gateway replicas horizontally and optionally enable fan-out between nodes.

  Your client code and event model stay unchanged.

• Same system in cloud or self-hosted

  Run in our managed cloud or deploy via Docker and Kubernetes using the same runtime components.

  No forked versions. No "enterprise edition" rewrite path.

• Secure by default

  Secrets never leave your servers.

  Clients receive app-scoped keys or short-lived tokens depending on your security model.

• Operational visibility built-in

  Monitor connections, throughput, and authentication failures through the same API surface used by the platform itself.

  Your on-call sees issues before users do.