> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/setup/implementations/country-implementation.md).

# Implementations

## Overview

This is a guide to implement MOSIP for a country. It is advised that Government and System Integrators (SI) study the recommended steps to work out an appropriate implementation strategy. The items are in "near-chronological order" and may differ for an implementation.

## Key decisions

1. Choice of deployment of [Pre-registration](/1.2.0/id-lifecycle-management.md#pre-registration).
2. Rate of enrolment desired.
3. Rate of authentication expected.
4. [Languages](/1.2.0/id-lifecycle-management/supporting-services/module-configuration.md#languages).
5. Customisation and procurement of components as given [here](/1.2.0/setup/implementations/reference-implementations.md).
6. [ID schema](/1.2.0/id-lifecycle-management/identity-management/id-schema.md) (as prescribed by the country's regulatory authority).
7. Hardware requirements estimate.
   * [Server side](https://github.com/mosip/documentation/tree/develop/docs/_files)
   * [Devices](https://github.com/mosip/documentation/blob/1.2.0/docs/_files/mosip-devices-calculator.xlsx)
8. [Credential choices](/1.2.0/id-lifecycle-management/identity-issuance/id-repository.md#credential-types).
9. ID Card print design.
10. MOSIP versions.
11. MOSIP support (scope).
12. Disaster recovery strategy.
13. A phased approach for rollout.

## Procurement

1. Engagement with an SI - terms and conditions.
2. Procurement of biometrics and other external components.
3. HSM
4. [Postgres](https://docs.mosip.io/1.2.0/modules/persistence/postgres-db)
5. [Object store](https://docs.mosip.io/1.2.0/modules/persistence/object-store)
6. Computer hardware

## Country specific data

1. [Masterdata](https://docs.mosip.io/1.2.0/modules/administration/masterdata-guide)
2. [Applicanttype MVEL](https://github.com/mosip/mosip-config/blob/develop3-v3/applicanttype.mvel)

## Customisation

1. Customisation of components as decided in [step 5 of Key decisions](#key-decisions) above.

## Deployment

1. [Certifcate/key generation](/1.2.0/id-lifecycle-management/supporting-components/keymanager/keys.md)
2. [Deployment design](https://docs.mosip.io/1.2.0/deploymentnew/getting-started).
3. Disaster recover set up
4. Biometric thresholding
5. Phased implementation
6. [Sandbox](https://docs.mosip.io/1.2.0/sandbox-details), staging, development setups.
7. IDA installation

## Partners

1. Onboarding of trusted partners
2. Print partner

## Rollout

1. Set up of registration centers
2. Onboarding of officers and supervisors
3. Training


---

# 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.mosip.io/1.2.0/setup/implementations/country-implementation.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.