> 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/our-core-tenets.md). # Platform principles The principles behind the platform and the decisions you make with it. Kinesis brings different sources of compute into a common deployment and operations workflow. Six principles guide that work. ## Reliability you can inspect An accepted deployment request is the start of a process. Follow app status, readiness, logs and usage to understand what is happening, and use those signals to decide when a service is ready for traffic. ## Deliberate access Choose where a workload runs and who can operate it. Resource sharing, API scopes and project restrictions express different parts of that decision. Select infrastructure appropriate to your data and requirements; discuss specific compliance needs with the team before deployment. ## Performance with context Match CPU, RAM, GPU and storage to the workload. Then measure. Hardware requirements, capacity availability and placement choices all affect the result. ## Transparent operations Configuration, status, logs and costs should help you explain the state of a deployment. The portal, REST API and MCP expose these resources through a shared platform model. ## Costs you can follow Understand the charging model for the compute you choose. Serverless usage, dedicated servers and externally managed infrastructure have different cost implications. Review cost data alongside utilization, and release dedicated capacity when you no longer need it. ## A direct path from intent to deployment Start with a template, container image or GitHub repository. Use the portal for interactive work, REST for integrations, and MCP for agent workflows. [Explore the platform](/what-you-can-do-with-kinesis.md) · [Choose compute](/getting-started/running-llms-with-kinesis-network/understanding-compute-sources.md) · [Talk to the team](/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/our-core-tenets.md?ask=&goal= ``` `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.