Core and Labs
Which RelKit features are Core and covered by the stability promise, and which are Labs and can change in any release.
Every RelKit package, integration, runtime and deploy target is either Core or Labs.
- Core features are tested on every supported runtime. From 1.0 they follow semantic versioning: an incompatible change ships only in a major release.
- Labs features carry no compatibility promise. They can change or be removed in any release.
Their APIs carry the
@experimentaltag, so your editor shows it on hover, and their docs pages show a Labs badge on the page and in the sidebar.
Each package declares its tier in the relkit.maturity field of its package.json. A repository
check fails when that field, the @experimental tags and the docs badges disagree with the tables
below.
Core
| Feature | Packages | Notes |
|---|---|---|
| Application model and compiler | relkit, @relkit/app, relkit/contracts, relkit/graph, relkit/engine, relkit/invocation, relkit/diagnostics, relkit/provider, relkit/runtime-effect |
|
| Functions | relkit/functions |
|
| Services | relkit/services |
|
| Routes | relkit/routes, relkit/runtime-hono, relkit/runtime |
|
| Schemas | relkit/schema, relkit/openapi |
|
| Env and config | relkit/config |
|
| Events | relkit/events |
|
| Jobs and schedules with local and Postgres backends | relkit/jobs, @relkit/local, relkit/providers-local, relkit/local-service |
|
| Cache | relkit/cache, @relkit/redis |
|
| Buckets | relkit/buckets, @relkit/s3 |
|
| Drizzle | @relkit/drizzle |
|
| Better Auth | @relkit/better-auth |
|
| Built-in telemetry | relkit/observability, @relkit/inspector |
|
| Typed client | @relkit/client |
|
| Testing | @relkit/testing |
|
| CLI | relkit, @relkit/cli, create-relkit |
|
| Inspector | @relkit/inspector, relkit/inspector-api |
|
| relkit mcp | @relkit/cli |
|
| Agent declarations and tools | relkit/agents, relkit/tools |
|
| Bun and Node LTS runtimes | — | |
| Integration catalog | create-relkit |
|
| Provider and adapter contract | relkit/provider, relkit/cache, relkit/buckets, relkit/events, relkit/jobs, relkit/runtime, @relkit/testing, @relkit/cli |
Realtime and agent adapter contracts follow their Labs features |
| Docker deploy | @relkit/docker, relkit/deploy |
Labs
| Feature | Packages | Notes |
|---|---|---|
| Realtime | relkit/realtime |
|
| Railway deploy | — | |
| Vercel deploy | — | |
| Cloudflare deploy | — | |
| Cloudflare Workers runtime | — | |
| AWS hosting | @relkit/aws, @relkit/pulumi |
|
| Cloudflare bindings | @relkit/cloudflare |
|
| Inngest job adapter | @relkit/inngest |
|
| Trigger.dev job adapter | @relkit/trigger |
|
| Effect MQ job adapter | @relkit/effect-mq |
|
| Postgres durable backend | @relkit/postgres |
|
| Agent adapters (LangChain, DeepAgents and AI SDK) | relkit/agent-adapters, @relkit/langchain, @relkit/ai-sdk |
|
| Graph workflows | @relkit/langchain |
|
| Sentry telemetry | @relkit/sentry |
|
| OTLP telemetry | @relkit/otlp |
Moving a feature to Core
A Labs feature moves to Core when it meets the Core bar: tests on every supported runtime, a docs
guide, and for a deploy target, a newcomer deploy test that passes in CI. The move is a change to
this table, the package’s relkit.maturity field, its tags and its docs badges, made in one pull
request.
No new feature areas before 1.0
Until Core reaches 1.0, RelKit adds no new feature area, such as a descriptor kind, a provider family or an integration, unless an approved OpenSpec change lists it. Bug fixes and hardening remain welcome in both Core and Labs.