> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/es/recursos/administrativo/implementacion-local.md).

# Implementación local

### Descripción general

Violet está diseñada para admitir sin problemas tanto implementaciones en la nube como locales.

Nuestra plataforma aprovecha tecnologías como Kubernetes, Docker y Terraform que permiten que Violet esté completamente en contenedores. También utilizamos servicios en la nube de código abierto siempre que sea posible, garantizando la interoperabilidad con cualquier entorno.

Esta arquitectura nos permite ofrecer:

* Implementación rápida y sin fricciones en local
* Actualizaciones rápidas a la última versión con una cadencia flexible
* Implementación en entornos aislados (air-gapped) cuando se requiera

Consulta la guía de instalación para tu entorno a continuación, o envíanos un mensaje a <hello@violetlabs.com> para obtener más información.

### Guías de instalación

[Implementación en Azure](/es/recursos/administrativo/implementacion-local/implementacion-en-azure.md)

[Implementación en AWS](/es/recursos/administrativo/implementacion-local/implementacion-en-aws.md)

[Implementación en Nutanix AHV](/es/recursos/administrativo/implementacion-local/implementacion-en-nutanix-ahv.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 by asking a question.

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

```
GET https://docs.violetlabs.com/es/recursos/administrativo/implementacion-local.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.