API reference › @evolu/common › local‑first/Relay › RelayConfig

Defined in: packages/common/src/local-first/Relay.ts:59

Configuration of a relay. A relay should also send the heartbeats that OwnerWebSocketTransport describes.

Extends

Extended by

Properties

isOwnerAllowed?

readonly isOwnerAllowed?: (ownerId: string & Brand<"Id"> & Brand<"OwnerId">, options: {
  signal: AbortSignal;
}) => Awaitable<boolean>;

Defined in: packages/common/src/local-first/Relay.ts:164

Optional callback to check if an OwnerId is allowed to access the relay. If this callback is not provided, all owners are allowed.

The callback receives the OwnerId and an options object with an abort AbortSignal, and returns a Awaitable boolean: true to allow access, or false to deny.

The callback can be synchronous (for SQLite or in-memory checks) or asynchronous (for calling remote APIs).

The callback returns a boolean rather than an error type because error handling and logging are the responsibility of the callback implementation.

OwnerId is used rather than short-lived tokens because this only controls relay access, not write permissions. Changes are encrypted end-to-end, so OwnerId exposure reveals no change contents. But anyone who knows an OwnerId can download the owner's encrypted changes and their timestamps from a relay and subscribe to new ones, as Privacy describes.

OwnerId exposure also allows write-key squatting. The relay stores the write key of the first write it accepts for an owner, so anyone who learns an OwnerId can claim it by writing there before the owner's devices do, unless StorageConfig.isOwnerWithinQuota refuses that write. The owner then gets ProtocolWriteKeyError on this relay until the operator deletes everything the relay stores for that OwnerId with Relay.deleteOwner, which removes the squatter's key and the data stored with it. This callback does not prevent that: it receives only the OwnerId of a connection, which a squatter can name as well, and every message on the connection can name another owner.

Owners specify which relays to connect to via OwnerTransport. In WebSocket-based implementations, this check occurs before accepting the connection, with the OwnerId typically extracted from the URL query string (e.g., ws://localhost:4000/?ownerId=...). The relay requires the URL to be in the correct format for OwnerId extraction.

Example

import {
  AppName,
  assertEqual,
  assertTrue,
  assertType,
  createAppOwner,
  createEvolu,
  createOwnerWebSocketTransport,
  createOwnerSecret,
  createRandomBytes,
  id,
  RelayUrl,
  type AnyTask,
} from "@evolu/common";
import type { RelayConfig } from "@evolu/common/local-first";

// Create once, persist the mnemonic securely, and restore it on later runs.
const appOwner = createAppOwner(
  createOwnerSecret({ randomBytes: createRandomBytes() }),
);
// Client: include the OwnerId so the relay can admit the connection.
const transport = createOwnerWebSocketTransport({
  url: RelayUrl.orThrow("wss://relay.evolu.dev/"),
  ownerId: appOwner.id,
});

const createTodoEvolu = createEvolu(
  { todo: { id: id("Todo") } },
  {
    appName: AppName.orThrow("AuthenticatedRelayExample"),
    appOwner,
    transports: [transport],
  },
);
assertType<typeof createTodoEvolu extends AnyTask ? true : false, true>();

// Relay: accept owners allowed by the app's access policy.
type IsOwnerAllowed = NonNullable<RelayConfig["isOwnerAllowed"]>;
const allowedOwnerIds = new Set([appOwner.id]);
const isOwnerAllowed: IsOwnerAllowed = (ownerId, { signal }) =>
  !signal.aborted && allowedOwnerIds.has(ownerId);

assertEqual(
  await isOwnerAllowed(appOwner.id, {
    signal: new AbortController().signal,
  }),
  true,
);
assertTrue(transport.url.includes(`ownerId=${appOwner.id}`));

isOwnerWithinQuota

readonly isOwnerWithinQuota: (ownerId: string & Brand<"Id"> & Brand<"OwnerId">, requiredBytes: number & Brand<"NonNaN"> & Brand<"Finite"> & Brand<"Int"> & Brand<"NonNegative">) => Awaitable<boolean>;

Defined in: packages/common/src/local-first/Storage.ts:112

Callback called before an attempt to write, to check if an OwnerId has sufficient quota for the write.

The callback receives the OwnerId and the total bytes that would be stored after the write (current stored bytes plus incoming bytes), and returns a Awaitable boolean: true to allow the write, or false to deny it due to quota limits.

The callback can be synchronous (for SQLite or in-memory checks) or asynchronous (for calling remote APIs).

The callback returns a boolean rather than an error because error handling and logging are the responsibility of the callback implementation. It must not throw or reject, because a throw is a defect that shuts the relay down for a supervisor to restart it; a callback calling a remote service catches its failure and returns whether to allow the write.

Relay deployments configure this callback. Client applications observe a denied relay write as a ProtocolQuotaError in the failure of that relay's route, which syncStateToOwnerSyncStatus reports as the owner's Error status.

Example

import {
  assertEqual,
  createAppOwner,
  createOwnerSecret,
  createRandomBytes,
  PositiveInt,
} from "@evolu/common";
import type { StorageConfig } from "@evolu/common/local-first";

// Create once, persist the mnemonic securely, and restore it on later runs.
const appOwner = createAppOwner(
  createOwnerSecret({ randomBytes: createRandomBytes() }),
);
const maxBytes = PositiveInt.orThrow(1024);
const relayStorageConfig: StorageConfig = {
  isOwnerWithinQuota: (ownerId, requiredBytes) =>
    ownerId === appOwner.id && requiredBytes <= maxBytes,
};

assertEqual(
  await relayStorageConfig.isOwnerWithinQuota(
    appOwner.id,
    PositiveInt.orThrow(2048),
  ),
  false,
);

Inherited from

StorageConfig.isOwnerWithinQuota


name?

readonly name?: string & Brand<"UrlSafeString"> & Brand<"Name">;

Defined in: packages/common/src/local-first/Relay.ts:66

The relay name.

Implementations can use this for identification purposes (e.g., database file name, logging).