> 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/welcome-to-kinesis-network.md).

# Compute, on your terms.

Deploy containers. Choose your compute. Build with agents.

Bring a container or a GitHub repository. Run it on serverless GPU and CPU capacity, dedicated cloud servers, or infrastructure you already own. Kinesis brings deployment, operations and cost visibility into one place.

## Start building

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-rocket" style="color:$primary;">:rocket:</i></td><td><h3>Deploy your first app</h3></td><td>Go from a project to a running service with the App Gallery or your own image.</td><td><a href="/getting-started/running-llms-with-kinesis-network.md">Deploy an app</a></td></tr><tr><td><i class="fa-code" style="color:$primary;">:code:</i></td><td><h3>Build with the API</h3></td><td>Automate deployments, inspect infrastructure and track spend with REST.</td><td><a href="/api.md">REST API</a></td></tr><tr><td><i class="fa-robot" style="color:$primary;">:robot:</i></td><td><h3>Connect your agent</h3></td><td>Give an MCP client the tools to deploy, diagnose and operate Kinesis.</td><td><a href="/mcp.md">MCP &amp; agents</a></td></tr><tr><td><i class="fa-microchip" style="color:$primary;">:microchip:</i></td><td><h3>Choose your compute</h3></td><td>Understand serverless capacity, dedicated servers and grids.</td><td><a href="/getting-started/running-llms-with-kinesis-network/understanding-compute-sources.md">Compute options</a></td></tr><tr><td><i class="fa-chart-line" style="color:$primary;">:chart-line:</i></td><td><h3>Operate with visibility</h3></td><td>Read logs, follow app status, inspect metrics and understand failures.</td><td><a href="/getting-started/running-llms-with-kinesis-network/monitoring-apps.md">Monitor and troubleshoot</a></td></tr><tr><td><i class="fa-network-wired" style="color:$primary;">:network-wired:</i></td><td><h3>Contribute compute</h3></td><td>Learn how approved providers bring idle hardware to the network.</td><td><a href="/getting-started/kinetization-of-idle-compute.md">Contribute compute</a></td></tr></tbody></table>

## One platform. Three ways to work.

| Interface    | Use it for                                                           | Start here                                        |
| ------------ | -------------------------------------------------------------------- | ------------------------------------------------- |
| **Portal**   | Interactive setup, configuration, logs and infrastructure management | [Open the portal](https://portal.kinesis.network) |
| **REST API** | CI pipelines, scripts and application integrations                   | [API documentation](/api.md)                      |
| **MCP**      | Agent-driven deployment, investigation and operations                | [Connect an agent](/mcp.md)                       |

Projects organize your apps. Apps define what runs. Serverless capacity or grids determine where it runs.

[Explore the platform](/what-you-can-do-with-kinesis.md) · [Get support](/support.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/welcome-to-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.