Deno LandDeno

Deploy Docs


In Deno Deploy, code is run in different data centers around the world in order to reduce latency by servicing requests at the data center nearest to the client. In the browser, the BroadcastChannel API allows different tabs with the same origin to exchange messages. In Deno Deploy, the BroadcastChannel API provides a communication mechanism between the various instances; a simple message bus that connects the various Deploy instances world wide.


The BroadcastChannel() constructor creates a new BroadcastChannel instance and connects to (or creates) the provided channel.

let channel = new BroadcastChannel(channelName);


name type description
channelName string The name for the underlying broadcast channel connection.

The return type of the constructor is a BroadcastChannel instance.


name type description
name string The name of the underlying broadcast channel.
onmessage function (or null) The function that's executed when the channel recieves a new message (MessageEvent).
onmessageerror function (or null) The function that's executed when the arrived message cannot be deserialized to a JavaScript data structure.


name description
close() Close the connection to the underlying channel. After closing, you can no longer post messages to the channel.
postMessage(message) Post a message to the underlying channel. The message can be a string, object literal, a number or any kind of Object.

BroadcastChannel extends EventTarget, which allows you to use methods of EventTarget like addEventListener and removeEventListener on an instance of BroadcastChannel.


A small example that has an endpoint to send a new message to all other actively running instances in different regions and another to fetch all messages from an instance.

const messages = [];
// Create a new broadcast channel named earth.
const channel = new BroadcastChannel("earth");
// Set onmessage event handler.
channel.onmessage = (event: MessageEvent) => {
  // Update the local state when other instances
  // send us a new message.

addEventListener("fetch", (event: FetchEvent) => {
  const { pathname, searchParams } = new URL(event.request.url);

  // Handle /send?message=<message> endpoint.
  if (pathname.startsWith("/send")) {
    const message = searchParams.get("message");
    if (!message) {
      return event.respondWith(
        new Response("?message not provided", { status: 400 }),

    // Update local state.
    // Inform all other active instances of the deployment
    // about the new message.
    return event.respondWith(new Response("message sent"));

  // Handle /messages request.
  if (pathname.startsWith("/messages")) {
    return event.respondWith(
      new Response(JSON.stringify(messages), {
        "content-type": "application/json",

  return event.respondWith(new Response("not found", { status: 404 }));

You can test this example by making an HTTP request to<region> and then making another request to from a different region (by using a VPN or some other way) to check if the first request's message is present in the second region.

We built a small chat application that you can play with at

Please file an issue in our feedback repository if you find any problem in Deploy service or documentation.