> 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.md).

# Installation

Choose how to run IZ Suite on your own infrastructure, from a single-VM proof of concept to a resilient production deployment

IZ Suite runs as a set of containers next to a PostgreSQL database. You can run it on a single virtual machine for a proof of concept, or spread it across managed services for production. Both use the same container images.

## Components

| Component    | Image                                       | What it does                                                                                            |
| ------------ | ------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Server**   | `iz-suite-server` with `FALCON_MODE=api`    | The web interface and the API. Applies database updates when it starts.                                 |
| **Worker**   | `iz-suite-server` with `FALCON_MODE=worker` | Background processing: assessment lifecycles, risk matching, reports, notifications and scheduled work. |
| **Agent**    | `iz-suite-agent`                            | Runs scans and connector jobs against your platforms and repositories, and Service Health checks.       |
| **Database** | PostgreSQL 16                               | Holds all IZ Suite data.                                                                                |

The images are published at `public.ecr.aws/h0h7r7j4/iz-suite-server` and `public.ecr.aws/h0h7r7j4/iz-suite-agent`, tagged with the release.

## Choose a Path

| Path                              | Use it for                                                                                                                  | Page                                                                                                                                                     |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Single VM with Docker Compose** | Proofs of concept, trials and small teams. Everything, including PostgreSQL, runs on one VM.                                | [Proof of Concept Installation](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/installation/proof-of-concept-installation.md) |
| **Managed services**              | Production: two or more servers behind a load balancer, a managed PostgreSQL database with backups, and workers that scale. | [Production Deployment](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/installation/production-deployment.md)                 |

Whichever you choose, size it from the number of assets you plan to assess; see [Requirements & Sizing](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/installation/requirements-and-sizing.md).

## Next Steps

* [Requirements & Sizing](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/installation/requirements-and-sizing.md): work out the machines and database you need.
* [Proof of Concept Installation](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/installation/proof-of-concept-installation.md): run IZ Suite on one VM.
* [Production Deployment](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/installation/production-deployment.md): the recommended production setup.
* [First Start](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/installation/first-start.md): apply the licence and sign in.


---

# 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.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.
