> For the complete documentation index, see [llms.txt](https://docs.one-click.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.one-click.dev/readme.md). # Getting Started This getting started guide is meant to get you up and running with One-Click as fast as possible. {% hint style="warning" %} **🌅 One-Click is winding down — something better is coming.** One-Click proved that deploying containers to Kubernetes should be a single click, not a stack of YAML. We're now channeling everything we learned into **klickops** — a batteries-included Container-as-a-Service platform for Kubernetes: containers, secrets, networking, scaling, backups, managed databases and more, from one clean UI, plus a CLI, an MCP server for AI agents, and a full REST API. No operator, no CRDs — just deploy. klickops is **not open source yet**, but it's coming. Bookmark and watch the repo: [**github.com/natrontech/klickops**](https://github.com/natrontech/klickops) These docs and the One-Click repositories are now in maintenance mode. Thanks to everyone who used and contributed to One-Click. 🙏 {% endhint %} {% embed url="" %}


🚀 Get started 🚀	with deploying One-Click to your Kubernetes cluster!		Platform Installation	Jan Lauber	Illustration 2.svg
🏗️ Architecture 🏗️	Learn more about the One-Click architecture!		Architecture		Illustration 1.svg

--- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.one-click.dev/readme.md?ask=&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 `build a script that syncs our docs to a CMS` 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.