> For the complete documentation index, see [llms.txt](https://docs.flowiseai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowiseai.com/espanol/documentacion-oficial/configuracion/deployment.md).

# Deployment

Aprende cómo hacer deployment de Flowise a la cloud

***

Flowise está diseñado con una platform-agnostic architecture, asegurando compatibilidad con una amplia gama de deployment environments para adaptarse a tus necesidades de infrastructure.

## Local Machine

Para hacer deployment de Flowise localmente, sigue nuestra guía [Get Started](https://github.com/FlowiseAI/FlowiseDocs/blob/main/esp/getting-started/README.md).

## Modern Cloud Providers

Las modern cloud platforms priorizan la automation y se enfocan en developer workflows, simplificando el cloud management y ongoing maintenance.

Esto reduce la technical expertise necesaria, pero puede limitar el nivel de customization que tienes sobre la underlying infrastructure.

* [Elestio](https://elest.io/open-source/flowiseai)
* [Hugging Face](/espanol/documentacion-oficial/configuracion/deployment/hugging-face.md)
* [Northflank](https://northflank.com/stacks/deploy-flowiseai)
* [Railway](/espanol/documentacion-oficial/configuracion/deployment/railway.md)
* [Render](/espanol/documentacion-oficial/configuracion/deployment/render.md)
* [Replit](/espanol/documentacion-oficial/configuracion/deployment/replit.md)
* [RepoCloud](https://repocloud.io/details/?app_id=29)
* [Sealos](/espanol/documentacion-oficial/configuracion/deployment/sealos.md)
* [Zeabur](/espanol/documentacion-oficial/configuracion/deployment/zeabur.md)

## Established Cloud Providers

Los established cloud providers, por otro lado, requieren un mayor nivel de technical expertise para manage y optimize según tus specific needs.

Esta complexity, sin embargo, también otorga mayor flexibility y control sobre tu cloud environment.

* [AWS](/espanol/documentacion-oficial/configuracion/deployment/aws.md)
* [Azure](/espanol/documentacion-oficial/configuracion/deployment/azure.md)
* [DigitalOcean](/espanol/documentacion-oficial/configuracion/deployment/digital-ocean.md)
* [GCP](/espanol/documentacion-oficial/configuracion/deployment/gcp.md)
* [Kubernetes using Helm](https://artifacthub.io/packages/helm/cowboysysop/flowise)


---

# 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.flowiseai.com/espanol/documentacion-oficial/configuracion/deployment.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.