<!-- Canonical: https://easyiga.com/deployment -->

[Home](https://easyiga.com/) / Deployment

Deployment

# Self-hosted by default.
EU option on request.

Self-hosted by default, on your own infrastructure, in your own jurisdiction. For organisations without suitable infrastructure, an EU-hosted deployment operated by our team is available on request.

[Discuss your deployment](https://easyiga.com/contact#form)

## Choose who operates the stack

### On your infrastructure

Your organisation operates the deployment and chooses its jurisdiction. Agree the responsibilities for backups, upgrades and recovery with your platform team. Confirm the external connections and support access required for your configuration.

### EU-hosted on request

For organisations without suitable infrastructure, our team offers an EU-hosted deployment on request. Hosting location, access arrangements and the operating scope must be agreed before contracting. Request the proposed processing and service terms as part of that discussion.

### With an existing midPoint installation

easyIGA provides the business-facing layer over midPoint. Review your current version, connectors and approval policies with us before agreeing the integration work.

## Size the deployment around your systems

The stack uses a container runtime and PostgreSQL. We will size the environment and plan the deployment around your identity population, connected systems and integration scope.

Document the authentication boundary and service-account permissions. Identify which data enters easyIGA and where each integration sends it. See the [security page](https://easyiga.com/security) for the evidence to request.

## Agree the pilot and its acceptance criteria

Start with a named population and a small set of applications. Confirm the source data and application owners, then agree which requests and approval policies the pilot must exercise.

Test the target-system result, including a failure and a missing-data case. Record the recovery procedure and the responsibilities for operating the deployment before moving it into production.

Use those results to agree the remaining scope and schedule. [Compare the full cost](https://easyiga.com/pricing), including integration work and your own operating effort.

## Bring your platform team into the conversation

Send the systems you want to govern and whether you already run midPoint. We will use those facts to discuss a deployment boundary and the work needed to validate it.

[Discuss your setup](https://easyiga.com/contact)
