> For the complete documentation index, see [llms.txt](https://wavatec.gitbook.io/ninoxbee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wavatec.gitbook.io/ninoxbee/introduction.md).

# Introduction

**How it works**

Ninoxbee exposes a series of **dynamically** generated questions to your visitors in the form of individual cards. Each card submit invokes an API call on your ninox database in order to fetch the next card. Once all cards are answered, a recap screen is displayed to your visitor with a thank you message.

The diagram below shows the positionning of ninoxbee in your architecture. Regardless to your deployement type, you will always be able to expose ninoxbee forms on the internet to collect feedback from your users in real time.

<figure><img src="/files/oD9KSFHHPNDM3JY9Ccyo" alt=""><figcaption><p>Ninoxbee positioning in your architecture</p></figcaption></figure>

Ninoxbee acts like a typical forms app, with the only difference that all forms questions are  **dynamically** generated, meaning that you benefit from the abundance and the configurability of the ninox language to build complex and inter-dependent questions / answsers, while keeping the data collection simple and straightforward for public end clients who don't have access to your database.&#x20;