> 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/understanding-how/how-does-kinesis-network-work.md).

# How Kinesis works

From an app definition to a running workload, with control at each step.

Kinesis separates the app you want to run from the compute that runs it. You describe the container, runtime and resources; the platform coordinates deployment onto compatible capacity.

```mermaid
flowchart LR
  A[Container image or GitHub repo] --> B[App configuration]
  B --> C{Compute target}
  C --> D[Serverless capacity]
  C --> E[Dedicated or shared grid]
  D --> F[Running app instances]
  E --> F
  F --> G[Endpoints, logs and usage]
```

## 1. Define the workload

Create an app inside a project. Start with a container image or connect a GitHub repository for an image build. Configure environment variables, network ports, execution settings and resource requirements.

## 2. Choose where it runs

Use serverless capacity for managed placement, or target a grid backed by dedicated cloud servers or infrastructure you bring. Available capacity, hardware requirements, placement constraints and grid quotas determine whether an app can be scheduled.

## 3. Follow deployment

Creation, builds, provisioning and lifecycle changes can be asynchronous. An API response or successful portal action acknowledges the request. App status, build status and server orders tell you how execution is progressing.

## 4. Connect and operate

Use the configured endpoint for traffic, logs for application output, and metrics for resource usage. Configure the application's own authentication and network behavior to match its purpose. When an app fails to start, check its configuration and startup logs before retrying.

## 5. Review capacity and cost

Stopping an app and releasing a dedicated server are separate actions. Check which resources remain allocated and their charging model before treating a workload as fully shut down.

The portal, [REST API](/api.md) and [MCP server](/mcp.md) provide different interfaces to these same resources.

[Deploy your first app](/getting-started/running-llms-with-kinesis-network.md) · [Choose compute](/getting-started/running-llms-with-kinesis-network/understanding-compute-sources.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 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/understanding-how/how-does-kinesis-network-work.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.