> For the complete documentation index, see [llms.txt](https://docs.industryapps.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.industryapps.net/onboarding-to-industryapps/application-pre-requisites/basic-requirements.md).

# Basic Requirements

### <mark style="color:green;">You application is stateless</mark> <a href="#id-1-1-keep-your-application-stateless" id="id-1-1-keep-your-application-stateless"></a>

It is explicit by saying that *web applications should be stateless*, as *web applications should be stateless unless there is a very good reason to have a state*. A *shopping cart* is a stateful feature by design and denying that is counterproductive. What our proposal is to make these state persevere on the client-side rather than at the server-side. If it is not possible, keep a shared resource for instances to store that data and retrieve. IndustryApps platform expects your application to be stateless, so we can increase and decrease the number of instances based on the load.

### <mark style="color:green;">Your application supports multitenancy</mark> <a href="#id-1-5-should-support-multitenancy" id="id-1-5-should-support-multitenancy"></a>

IndustryApps is a platform used by multiple clients called tenants. We must take care not to share the data of each tenant. ie if your application needs to store some data, you must be cautioned on tenants. Currently, tenant is a Key combination of companyId and plantId of each user.

{% hint style="info" %} <mark style="color:green;">IndustryApps focuses on Industrial solutions. Your product should be proven and already deployed in at least 1 reference factory site any where in the world. It is always a best practice to provide references to support customers decision.</mark>&#x20;
{% endhint %}

### &#x20;<a href="#id-1-2-keep-your-application-sync-with-application-registry" id="id-1-2-keep-your-application-sync-with-application-registry"></a>


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.industryapps.net/onboarding-to-industryapps/application-pre-requisites/basic-requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.