> 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.md).

# Deploy an app

Choose a source, configure your app and verify its first deployment.

An app is a container workload inside a project. You can start with a curated template, a container image or a GitHub repository. The same concepts apply to model serving, web services and background jobs.

## Choose your starting point

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>App Gallery</strong></td><td>Use a curated configuration and customize it for your workload.</td><td><a href="/getting-started/running-llms-with-kinesis-network/creating-apps-with-app-gallery.md">Deploy from the App Gallery</a></td></tr><tr><td><strong>Your image or repository</strong></td><td>Configure a container image or build from GitHub with the app wizard.</td><td><a href="/getting-started/running-llms-with-kinesis-network/creating-an-app-from-scratch.md">Create a custom app</a></td></tr><tr><td><strong>Automation</strong></td><td>Create the project and app from scripts or an MCP client.</td><td><a href="/api.md">REST API</a></td></tr></tbody></table>

{% stepper %}
{% step %}

## Create or choose a project

Open [Projects](https://portal.kinesis.network/dashboard/projects). A project groups related apps and gives you a place to manage access. See [Create a project](/getting-started/running-llms-with-kinesis-network/creating-a-project.md).
{% endstep %}

{% step %}

## Configure the app

Choose **Create App** and work through **Source**, **Runtime**, **Network**, **Execution** and **Resources**. Review environment variables, the container port and the compute requirements before launching.

For a model server, check the model's GPU memory needs and any registry or model-download credentials. For a repository, confirm the branch, build context and Dockerfile.
{% endstep %}

{% step %}

## Choose compute and launch

Use [serverless capacity or a grid](/getting-started/running-llms-with-kinesis-network/understanding-compute-sources.md). If a teammate shared a grid with you, select the appropriate grid and check its available capacity and quotas.

Launching starts deployment and can consume credits. A repository first goes through a build; a dedicated grid may need to acquire machines before the app starts.
{% endstep %}

{% step %}

## Verify the endpoint

Open the app's status, logs and metrics. Use the endpoint shown by Kinesis once it is ready. The container must listen on the configured port and bind to `0.0.0.0` to accept incoming traffic.

If deployment stalls, follow [Monitor and troubleshoot](/getting-started/running-llms-with-kinesis-network/monitoring-apps.md).
{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.