# Hosting
The dydu solution is available in SaaS (*Software as a Service*). It means the dialog engine is hosted by the dydu infrastructure.
The dialog box is generated by javascript code. This, as well as image files accompanying it can be hosted either by dydu, or by the client himself.
If the client hosts its own dialog box, each modification, in design or function, requires a package that has to be tested on the customer's acceptance test environments before being published.
The diagrams below explain the network flows when a user connects to the customer's site and chats with the bot.
Whatever the product (automatic chat, Livechat,dynamic FAQ, static FAQ), the hosting issue is essential.
Two alternatives are possible:
* External hosting;
* Internal hosting.
### External Hosting
Most of the time, hosting is not managed by the customer's infrastructure but by dydu infrastructure.
External hosting allows, without making any change on the client-side integration, take advantage of the following developments:
* Aesthetic improvements;
* New pushing rules;
* Bug Fixes;
* Added context variables (user information).
The deliverable is then the link to the dialog box / Dynamic FAQ / Static FAQ to integrate as defined in *Integration / Source Code* of each of these products.
### Internal hosting
If, for reasons of security or accessibility to the network, the dialog box must be hosted by the client, dydu provides a package containing all the necessary files.
* **Dialog box / Dynamic FAQ**
In this case, the dialog box and/or the dynamic FAQ is delivered in the form of a zip file with compressed elements and contains the following files:
* **assembly.min.js**
* assembly.js
* sample.debug.html
* **pushrules\_angular.js**
* **surveys\_angular.js**
* backup.zip
* **files/...** Only files / folders in bold must be deployed in production. Others are useful for test, debug, or restore purposes.
* **Static FAQ**
In the case of the static FAQ, a zip archive containing the HTML/CSS/JS file tree is provided and must be implemented on a web server.
The dydu solution is available in SaaS (*Software as a Service*). It means the dialog engine is hosted by the dydu infrastructure.
The dialog box is generated by javascript code. This, as well as image files accompanying it can be hosted either by dydu, or by the client himself.
If the client hosts its own dialog box, each modification, in design or function, requires a package that has to be tested on the customer's acceptance test environments before being published.
The diagrams below explain the network flows when a user connects to the customer's site and chats with the bot.
### Hosting the dialog box by dydu[](https://dev.docs.dydu.ai/docs/Others/Technical_aspects/hosting#hosting-the-dialog-box-by-dydu)
 **Login to web site**
The user connects to the website, hosted in the customer's infrastructure.
 **Downloading the dialog box**
The HTML code of the page that includes the dialog box tells the browser to download the javascript code and images from the dialog box.
These are hosted by the **dydu** infrastructure, specifically by a web server.
 **Querying the bot**
When the user asks the bot a question, the request is sent to the dydu web server.
 **Transmission of the request to the dialog engine**
The web server acts as a reverse proxy and sends the request to the dialog engine that deals with the question and provides the matching answer.
### Hosting the dialog box by the client[](https://dev.docs.dydu.ai/docs/Others/Technical_aspects/hosting#hosting-the-dialog-box-by-the-client)
 **Login to web site**
The user connects to the website, hosted in the customer's infrastructure.
 **Downloading the dialog box**
The HTML code of the page that includes the dialog box tells the browser to download the javascript code and images from the dialog box.
These are hosted by the **client's** infrastructure.
 **Querying the bot**
When the user asks the bot a question, the request is sent to the dydu web server.
 **Transmission of the request to the dialog engine**
The web server acts as a reverse proxy and sends the request to the dialog engine that deals with the question and provides the matching answer.
---
# Agent Instructions: 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:
```
GET https://docs-en.dydu.ai/other/technical-aspects/hosting.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.