> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/on-premise/id/on-premise.md).

# On-Premise

Akses panduan untuk instalasi, konfigurasi, Pemeliharaan, dan peningkatan Navixy On-Premise. Bandingkan opsi On-Premise dan PaaS di bagian Tanya jawab.

Bagian ini memberikan pemahaman mendalam tentang opsi penerapan On-Premise di platform Navixy, beserta tipe PaaS.

Temukan panduan komprehensif yang menyederhanakan [instalasi](/docs/on-premise/id/on-premise/how-to-guide/installation.md), [pembaruan](/docs/on-premise/id/qa/software-updates.md), [konfigurasi](/docs/on-premise/id/on-premise/how-to-guide/configuration.md) dan [Pemeliharaan](/docs/on-premise/id/on-premise/how-to-guide/maintenance.md) infrastruktur Navixy di lokasi Anda sendiri. Dapatkan wawasan berharga untuk menentukan infrastruktur yang paling sesuai bagi kebutuhan spesifik Anda. Manfaatkan sumber daya lengkap ini untuk meningkatkan kualitas instalasi, menyederhanakan pembaruan, dan memastikan Pemeliharaan yang optimal.

Jika Anda tidak yakin jenis penerapan mana yang paling cocok untuk Anda, buka [bagian Q\&A](/docs/on-premise/id/qa.md) untuk membandingkan fitur dan batasan dari [PaaS dan On-Premise](/docs/on-premise/id/qa/paas-vs-on-premise.md) opsi.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/on-premise/id/on-premise.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.