> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/knowledge-base/infrastructure-and-platform/is-ilert-hosted-in-the-cloud-or-on-premises.md).

# Is ilert hosted in the cloud or on-premises?

ilert is a cloud-hosted platform, managed entirely by us — no on-premises infrastructure is required on your end.

## Cloud hosting benefits

### Rapid deployment

* **No infrastructure setup**: Get started immediately without provisioning servers
* **Instant scalability**: Scale up or down based on your needs without hardware changes
* **Managed updates**: Receive automatic updates and improvements without manual intervention

### Operational advantages

* **Reduced overhead**: No need to manage servers, databases, or infrastructure
* **High availability**: Benefit from our redundant cloud infrastructure
* **Security**: Leverage our enterprise-grade security measures and compliance

### Maintenance-free

* **Automatic backups**: Data is automatically backed up and secured
* **Monitoring**: Our team monitors the platform 24/7
* **Updates**: New features and security patches are deployed automatically

## Getting started

Since ilert is cloud-hosted, you can start using the platform immediately after account creation. Simply sign up and begin configuring your alert sources, teams, and escalation policies.


---

# 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://docs.ilert.com/knowledge-base/infrastructure-and-platform/is-ilert-hosted-in-the-cloud-or-on-premises.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.