> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stardeck.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Blueprints

> Start a new app from a complete existing foundation

<Info>
  **Blueprints are in Alpha** and available only to selected organizations. If you don't see **Start
  from a Blueprint** when creating an app, your organization does not currently have Alpha access.
</Info>

A **Blueprint** is a complete starting app. Creating from one forks that whole foundation into your new app and remembers the Blueprint lineage so you can pull published updates later.

Use a Blueprint when you want a proven, end-to-end product foundation — not just a single reusable capability. For individual capabilities, see [Modules](/app-structure/modules). For how Blueprints fit the larger model, see [One Product, One App](/app-structure/overview).

## Platform vs organization Blueprints

| Kind                       | Who publishes it  | Typical use                                                   |
| -------------------------- | ----------------- | ------------------------------------------------------------- |
| **Platform Blueprint**     | Stardeck          | Starting points available across enabled organizations        |
| **Organization Blueprint** | Your organization | Your team's proven apps that others in the org can start from |

Both appear in the same **Choose a Blueprint** picker when your organization has Alpha access.

## Creating an app from a Blueprint

1. Open **New App** on your dashboard.
2. Choose **Start from a Blueprint**.
3. Pick a platform or organization Blueprint.
4. Describe what you want to build on top of that foundation and submit.

Starting from a Blueprint and starting from Modules are mutually exclusive. You pick one creation path for the new app.

Your new app is a fork of the Blueprint. Starcat Developer still helps you customize it — the Blueprint just gives you a stronger first version.

## Lineage and updates

Apps created from a Blueprint keep a link back to that source. When the Blueprint owner publishes a new version (with a changelog and change type), apps built from it can see a **Blueprint update available** indicator.

### In-product updates

From the project toolbar, you can run an agent-driven sync that pulls the published Blueprint changes into your app. Prefer this when your fork is lightly customized and you want a hands-off update.

### Local merge workflow

If your fork is heavily customized and you want to review every changed line before anything lands, use the local update flow instead:

<Card title="Update from a Blueprint (local)" icon="code" href="/local-claude-code/blueprint-updates">
  Review and merge published Blueprint updates from your local workspace
</Card>

## When not to use a Blueprint

* You only need a blank canvas — create a blank app.
* You want a few reusable capabilities rather than a whole starting app — use [Modules](/app-structure/modules) if your organization has Alpha access.
* You need a second audience experience inside an existing product — add a [Surface](/app-structure/surfaces), don't fork another Blueprint.