Overview

TailorKit lets you add an app ecosystem directly into your product. We handle the infrastructure, sandboxing, distribution, and more, so users can build features for themselves and organizations can unblock their own workflows.

The host product remains in control: it chooses where apps render, which data they receive, which components they can use, and which trusted actions they can request.

Start here

Choose your path

If you own the product that will host apps, start with Installation, then define screens, components, and actions.

If you are building an app for an existing TailorKit host, start with the Quickstart, then read Writing apps.

What TailorKit provides

• Secure sandboxing for running apps inside your product.
• Proxied UI rendering, so apps can use your existing components and feel native.
• Agentic app builder, so users can create apps from a prompt.
• TypeScript app development with support for external data fetching and npm packages.
• Managed infrastructure for advanced apps, including backend functionality, databases, secret storage, email services, and more.

Terminology

• Host app: your product. It owns routing, data loading, permissions, actions, and the design system.

• TailorKit app: a lightweight runtime app that renders inside the host app through the components and screens the host exposes.

• Schema: the typed contract that describes the components, screens, context, actions, and theme tokens available to TailorKit apps.

• Registry: the list of TailorKit apps the host can load for an environment, workspace, customer, or user.

• Screen: a host-owned surface where one or more TailorKit apps can render.

FAQ

How is TailorKit secure?

TailorKit keeps the host app in control. Apps only see the screens, components, theme tokens, context, and actions you expose. In production, treat apps as untrusted code and validate the registry, permissions, actions, and component surface area before loading them.

How do apps interact with external data?

Apps should use explicit host actions or their own external APIs. They should not reach directly into host route data, databases, or private internals. The host decides what context is passed into each screen and which actions an app can call.

How do apps use our design system?

The host publishes a typed schema of allowed components, fields, children, actions, and theme tokens. Apps render through that schema, so they can feel native while still staying inside the UI surface you support.

How do you code apps?

TailorKit apps are lightweight runtime apps. We auto-generate typed components from the schema you provide, so app developers can compose your approved UI, define screens, and run the preview server while building.