> For the complete documentation index, see [llms.txt](https://docs.kinesis.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kinesis.network/getting-started/running-llms-with-kinesis-network/creating-apps-with-app-gallery.md).

# Deploy from the App Gallery

Start from a curated app configuration and choose how to launch it.

The App Gallery provides starting configurations for supported workloads. A template supplies an app configuration that you can launch or customize for your own environment.

{% stepper %}
{% step %}

### Open app creation

Choose the intended organization, open a project where you have Developer or Admin access and select **Create App**. For a new project, the portal takes you directly to this flow.
{% endstep %}

{% step %}

### Choose a template

Select **Select Template from Gallery**, then choose a workload. **Choose Custom Model** comes first for an Ollama model of your choice. When no grid is available, templates that can run on serverless CPU are ordered first. The vLLM multi-GPU template category is currently hidden in both the gallery and templates API. Review the selected model, image and resource requirements.
{% endstep %}

{% step %}

### Review the compute target

Select serverless CPU capacity or an available grid. GPU workloads need a grid; serverless GPUs are currently paused. Grid quotas count against the app’s creator. If serverless capacity is disabled for Developers, Quick Launch needs an accessible grid; ask an admin when none is available.
{% endstep %}

{% step %}

### Launch or customize

**Quick Launch** submits the preconfigured app with the selected compute target. Use it when the settings already match your needs.

**Customize First** returns you to the configuration wizard. Review ports, environment variables, hardware and deployment location, then launch from **Resources**.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Launching an app can consume the organization’s credits or use dedicated capacity. Review the selected target and resource settings before choosing Quick Launch.
{% endhint %}

## Try a small model on CPU

Supported small Ollama models, up to about 9B parameters, offer **Try on CPU**. For a GPU template without a GPU grid, the portal offers **Start on CPU now** when eligible, **Set up a grid**, or **Not now**. CPU replies can be slower than GPU replies. The organization must have credit and allow the member to use serverless; otherwise an admin needs to resolve the credit or compute restriction. A CPU trial changes the configuration to use no GPU.

When using `list_templates`, read `notes` before passing a template to `create_app`. GPU templates do not include a grid and need `config.grids.ids`; copying their configuration unchanged will not create a serverless GPU app.

## Confirm that the app is ready

Open the app detail page. Follow its status, inspect startup logs and check the endpoint once the workload is ready. Model downloads and container startup can take time; an accepted launch does not mean that the service is immediately available.

If a template needs a token, password or other secret, configure it before sending production traffic. Do not put secrets in screenshots or support messages.

[Understand compute options](/getting-started/running-llms-with-kinesis-network/understanding-compute-sources.md) · [Monitor and troubleshoot](/getting-started/running-llms-with-kinesis-network/monitoring-apps.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kinesis.network/getting-started/running-llms-with-kinesis-network/creating-apps-with-app-gallery.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.