Reeve
Developers

Build an app

Build an app or connector that runs inside Reeve — scaffold it, declare permissions in a manifest, and submit it for review.

Build an app

Apps extend Reeve from the inside: they run embedded in the Reeve app and use the SDK to reach managed AI, cloud storage, live data, and events. Users install your app and use it right where they already work.

The App Platform is in developer preview. The flow below describes how building and shipping an app works at a high level; the exact scaffolding command, manifest fields, and review SLA may change before general availability. Confirm specifics against the current tooling; this section will expand as the App Platform reaches general availability.

The shape of an app

An app is a web app you host, plus a manifest that tells Reeve how to install it:

  • Your app — any framework, served over HTTPS, loaded in an iframe inside Reeve.
  • A manifest (reeve-manifest.json) — identity, the permissions your app needs (e.g. AI, storage, specific data sources), and listing metadata.
  • The SDK — how your app actually calls Reeve. See SDK & embeds.

From idea to listed

Scaffold a new app and run it locally, then load it into Reeve to see it live in the iframe.

Declare permissions in reeve-manifest.json — request only what your app uses. Permissions are shown to users at install time and enforced at runtime.

Build against the SDK: generate with managed AI, persist app data in cloud storage, query connected platforms, and react to events.

Submit for review. Apps are reviewed for quality and security before they're listed. You'll get actionable feedback; most apps need a round or two before approval.

Connectors

A "connector" in this sense is an app whose job is to bridge Reeve to an outside system — pulling data in or pushing actions out via the SDK and your own backend. The same build-and-review flow applies.

Note: "connector" is also used in Reeve for the built-in data integrations users link in Connect Your Data (Shopify, Klaviyo, Meta Ads, and so on). Those are configured in the app, not built by developers.

Reference

On this page