Skip to main content
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.
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. For how Blueprints fit the larger model, see One Product, One App.

​
Platform vs organization Blueprints

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:

Update from a Blueprint (local)

Review and merge published Blueprint updates from your local workspace

​
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 if your organization has Alpha access.
  • You need a second audience experience inside an existing product — add a Surface, don’t fork another Blueprint.