Start with one customer-facing feature

Ship Schedules, Approvals, or Bulk inside a multi-tenant SaaS without owning the component state machine and operator tooling. Your application remains responsible for identity, authorization, domain data, and business side effects.

Choose the workflow you need to ship

@incld/react-schedules

Scheduling composer, trigger, lists, details, next-run display, run history, and hooks.

supported

@incld/react-approvals

Request dialogs, reviewer inboxes, decisions, timelines, policies, presentation gates, and hooks.

supported

@incld/react-bulk

Live operation progress, history, chunk inspection, cancellation, events, and polling hooks.

supported

@incld/react-audit

Viewer-aware audit filters, timeline, event details, and query hooks.

supported

Use the shipped UI before going headless

The first project on an account gets Schedules, Approvals, and Bulk on Developer with no card and no expiry. Those components have monthly hard limits; Audit becomes available with the first paid component upgrade and combines lifecycle events with manual events from your application.

Request and delivery paths

01

Resolve the current identity

Read your existing session and return stable user and organization IDs plus the roles, permissions, or claims used by authorization.
02

Authorize the browser proxy

React calls your same-origin /api/incld route. The adapter removes browser identity fields, injects trusted context, and forwards only allowlisted operations.
03

Verify signed delivery

Schedules and Bulk send events to a separate webhook route. Verify the raw body and signature, then dispatch the declared action with an idempotency key.
04

Inspect operations

Use the dashboard for run delivery, approval policy changes, audit queries, Bulk progress, API keys, and component usage.

Application boundary text

React component ──same-origin──▶ your /api/incld/v1/* proxy
                   │ trusted context + secret key
                   ▼
                @incld API v1
                   │ signed event
                   ▼
your action handler ◀──────── your /api/incld/webhook route

Supported surfaces

Surface	Status	Use it for
REST API v1	Supported	Every server-side operation and language-neutral integration.
JavaScript / TypeScript	Supported	Authenticated server calls, same-origin browser calls, framework adapters, and webhooks.
React	Supported	The supported UI runtime for every component.
Next.js, Express, SvelteKit, Nuxt	Supported	Trusted context, browser proxy routes, signed webhooks, and action sync.
Go and Elixir	Supported	Direct server API clients with schedule events, project Run lookup, and webhook verification. React requires your own trusted proxy route.
Svelte UI	Experimental	Unpublished prototypes; use the SvelteKit backend adapter with your own UI today.

Pick your path

Next.js quickstart Install the client, proxy, webhook, provider, and first component. Another backend Start with Express, SvelteKit, Nuxt, Go, Elixir, or REST.