Ship

Scoped access

Organize developer access around organizations, Apps and server credentials.

Your backend

Server SDK · BeeOSClient

BeeOS Cloud

Agent runtime

harness-sdk.ts

import {
  RuntimeRegistrationCoordinator,
  type RuntimeRegistrationConfig,
  type RuntimeRegistrationTransport,
} from "@beeos-ai/cloud-harness-sdk";

async function startRuntime(
  transport: RuntimeRegistrationTransport,
  config: RuntimeRegistrationConfig,
  onLeaseLost: (reason: "fenced" | "expired" | "heartbeat_failed", cause?: unknown) => void,
) {
  const runtime = new RuntimeRegistrationCoordinator(transport, config, onLeaseLost);
  await runtime.start();
  return runtime;
}

Authorize from the backendIssue App-scoped server credentials and enforce your own user permissions before any request.

Connect the runtimeRegister the runtime, declare the methods it supports and deliver replies to your product.

Receive eventsSubscribe to lifecycle and operational webhooks, then update state in your own store.

Your backend owns end-user identity and ACLs. The frontend renders authorized data fetched through your backend; there is no separate App client SDK.

Documentation

01
Create an organization and App
02
Issue an App-scoped server key
03
Keep the key in your backend and enforce user permissions there

A practical use case

Issue an App-scoped server key for your backend while your product continues to own its users and permissions.

Organization and App boundaries
Scoped server credentials
Separate product user authorization

Start integrating

Read the integration guide, then connect your runtime and backend.

Documentation