> [Agent navigation index](/llms.txt)

# Application types

Brix supports full-stack Hono and Preact applications, browser-only managed React applications, and integrations with independently hosted applications. Choose the runtime and ownership model before following the rest of the guides: the choice decides which features, commands, and deployment targets apply.

## Full-stack Preact

Use `brix create app <name>` for server-rendered pages, Hono API routes, Preact islands, HTML fragments, and built-in Panda styling. Only interactive islands ship component JavaScript to the browser. This is the application model used by the [pages](/docs/pages.md), [islands](/docs/islands.md), and [server](/docs/server.md) guides, and the only type that deploys to Node, AWS Lambda, Cloudflare, or Fastly.

## Managed React

Use `brix create react-app <name>` for a React SPA or `brix create contentful-app <name>` for a Contentful App SDK and Forma 36 project. Brix owns their Vite, test, and lint configuration, and they import React through `@brix/react`. They do not use Hono routes, SSR, Preact islands, Panda, `brix start`, or managed Storybook. Their production output is a static browser bundle that calls separately deployed APIs.

[Create and operate a managed React application.](/docs/react-managed.md)

## External hosts

Adopt an existing project, such as a React application with its own build system, into a workspace when it should keep its own runtime and lifecycle scripts. It consumes shared contracts and libraries through declared direct dependencies, and `brix workspace integrate react` adds the `@brix/react` bindings.

[Integrate an external React host.](/docs/react-external.md) See [external workspace applications](/docs/workspaces-external.md) for other hosts and cross-origin integration.
