> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/installation/modes/single-server-installation.md).

# Single Server Installation

## IZ Suite Single Server Installation

{% hint style="warning" %}
Before installing, make sure you have:

* Purchased a valid license.
  {% endhint %}

The single server section describes the installation of a single-node **`IZ Suite`** instance from the ZIP file or from a docker image.

### Components of IZ Suite Server Installation

In a single server deployment model, IZ suite has the following main components:

1. **`IZ Suite Server`**: IZ Suite server component with UI, backend API
2. **`IZ Suite Database`**: IZ Suite requires a database (PostgreSQL preferred) to be installed which contains all the data needed for the server
3. **`IZ Agents`**: IZ Suite requires an agent component for certain products to work (for example - IZ Eye and IZ Pulse).<br>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F9Qo7v4c0aoJ9bEWHKJKH%2Fiz_suite_architecture_single_server.png?alt=media&amp;token=89b2c016-ec61-43d0-b351-17310e81ee90" alt=""><figcaption></figcaption></figure>

### Installation Steps

1. **`Install IZ Suite Database`**: For optimal performance, the database and server should be installed on separate servers. If a database already exists, keep the database connection details handy to configure the server installation.
2. **`Install the IZ Suite server`**: This can be a stand alone server installation from a zip file or from a docker image. You would need to follow installation instructions to point the server to the IZ suite database
3. **`Install IZ Agents`**: You can download agent from a zip file or from a docker image. You would need to configure the agent to point to the IZ suite server for them to connect and work.

### Performance considerations

For optimal performance, the database and server should be installed on separate servers. On a development or trial instance, database can be installed on the same machine as the IZ suite software for easy debug/maintenance.

Depending on the connectivity use cases, the agents could be co-located with the IZ suite server or could be installed on different machines. Number of agents and location will depend on licensing and customer requirements. For most public use cases, agent could be co-located with the IZ server installation.

### See Also

* [Prerequisites](/product-guides/integral-zone/iz-suite/installation/installation-requirements.md)
* [Cluster Mode](/product-guides/integral-zone/iz-suite/installation/modes/cluster-installation.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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/installation/modes/single-server-installation.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.