---
title: Elevasis SDK
description: The three published Elevasis packages — @elevasis/sdk, @elevasis/core, and @elevasis/ui — that tenant projects install and compose to build AI workflows and feature-rich applications on the platform.
---

The Elevasis SDK is the published surface for building on the Elevasis platform. It ships as three independent npm packages that can be installed together or separately depending on what you are building.

- **`@elevasis/sdk`** -- runtime + resource definitions + CLI + worker adapters. The entry point for any tenant project. Install this to write workflows, agents, and resources and deploy them to the platform.
- **`@elevasis/core`** -- shared Zod schemas, organization model, knowledge graph, entity contracts, and auth types. Install this when you need the typed contracts without the full SDK runtime.
- **`@elevasis/ui`** -- React 19 feature-shell and manifest-backed feature modules (Lead Gen, CRM, Projects, Operations, Monitoring, Settings, SEO, and more). Install this when you are building a host UI that embeds Elevasis features.

## How They Compose

A typical tenant project installs `@elevasis/sdk` first. The SDK peer-depends on `@elevasis/core` for its shared schemas, so the contracts are always in sync. A tenant UI project adds `@elevasis/ui` on top to embed the shared React feature modules into its own shell.

```
@elevasis/sdk       -- workflows, agents, adapters, CLI, deploy
      |
      uses types from
      |
@elevasis/core      -- Zod schemas, org model, entities, knowledge, auth

@elevasis/ui        -- React feature-shell (provider + manifest-backed modules)
      |
      uses types from
      |
@elevasis/core
```

You do not need all three packages. A pure automation project needs only `@elevasis/sdk`. A shared-types layer needs only `@elevasis/core`. A UI host without custom workflows can install `@elevasis/ui` alone.

## Packages

### @elevasis/sdk (v1.30.2)

The primary developer package. Provides the TypeScript API for defining workflows and agents, the `elevasis-sdk` CLI for validation and deployment, and typed worker adapters for 25 platform and integration tools.

**Install:** `pnpm add @elevasis/sdk`

**Published subpaths:** `.` (default), `./worker`, `./test-utils`, `./node`

See [@elevasis/sdk](sdk/index.mdx) for the full group overview, getting started guide, CLI reference, adapter catalog, and more.

### @elevasis/core (v0.39.0)

The shared contract layer. Exports Zod schemas and TypeScript types that are shared between the SDK, the UI, and the platform API. Useful when you need the typed contracts (organization model, entities, knowledge, auth) in a package that does not pull in the full SDK runtime.

**Install:** `pnpm add @elevasis/core`

**Published subpaths:** `.` (default), `./auth`, `./test-utils`, `./organization-model`, `./entities`, `./knowledge`

See [@elevasis/core](core/index.mdx) for subpath details, browser/server split, and when to use it.

### @elevasis/ui (v2.42.0)

The shared React feature-shell. Provides an `ElevasisProvider` and manifest-backed feature modules that a host UI embeds. Many peer dependencies are optional -- pull only what the features you use require.

**Install:** `pnpm add @elevasis/ui`

**Peer deps:** React 19, Mantine 8.2.7, TanStack Query, TanStack Router, Zod 4.1, Zustand 5, cytoscape (many optional)

See [@elevasis/ui](ui/index.mdx) for the provider model, feature modules, peer dependency details, and when to use it.

## Authoring Note

These pages have a dual surface. At SDK build time, `packages/sdk/scripts/copy-reference-docs.mjs` copies every `apps/docs/content/docs/sdk/**.mdx` into `packages/sdk/reference/`, which ships inside the npm package (`files: ["reference/"]`). The `external/_template/CLAUDE.md` points tenant-project agents at `node_modules/@elevasis/sdk/reference/` as their primary reference bundle. Drift in these docs does not just affect the public site -- it actively misleads every agent building a tenant project.
