> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.2/platform/technology-stack.md).

# Technology Stack

This page lists all the technologies used in building OpenG2P. Free and open-source softwares with clear long-term support availability have been chosen. Certain choices can be replaced with other free or commercial options for deployment.

<table><thead><tr><th>Domain</th><th>Tools/Technologies</th><th width="123">Version</th><th>Licence Type</th></tr></thead><tbody><tr><td>Operating System</td><td>Ubuntu Server</td><td>20.04</td><td>Free</td></tr><tr><td>Business Apps</td><td>Odoo</td><td>15.0</td><td>LGPL</td></tr><tr><td>ID System</td><td>MOSIP</td><td>1.2</td><td>MPL 2.0</td></tr><tr><td>Development - Language Runtime</td><td>Python</td><td>3.5+</td><td><a href="https://docs.python.org/3/license.html#psf-license">PSF License</a></td></tr><tr><td>Database</td><td>Postgres</td><td></td><td>Postgres License BSD 2-clause "Simplified License"</td></tr><tr><td>ID Verification</td><td>MOSIP Token Seeder</td><td></td><td>MPL 2.0</td></tr><tr><td>ID Verification</td><td>eSignet</td><td></td><td>MPL 2.0</td></tr><tr><td>Analytics Engine</td><td>Elasticsearch</td><td></td><td>Elastic License 2.0</td></tr><tr><td>Data streaming</td><td>Debezium</td><td></td><td>Apache 2.0</td></tr><tr><td>Offline data collection</td><td>ODK</td><td></td><td>Apache 2.0</td></tr><tr><td>Visualization</td><td>Kibana</td><td></td><td>Elastic License 2.0</td></tr><tr><td>S3 Storage</td><td>MinIO</td><td></td><td>AGPL 3.0</td></tr><tr><td>Development - API Documentation</td><td>Swagger</td><td></td><td>Apache License 2.0</td></tr><tr><td>Task Management</td><td>Jira</td><td></td><td>Commercial (OpenG2P has a free license)</td></tr><tr><td>Source Code Management</td><td>GitHub</td><td></td><td>Commercial (OpenG2P uses Free plan)</td></tr><tr><td>Deployment</td><td>Docker</td><td></td><td>Apache 2.0</td></tr><tr><td>DevOps tools</td><td>Ansible</td><td></td><td>GNU GPL v3.0</td></tr><tr><td>DevOps tools</td><td>Github actions</td><td></td><td>Free</td></tr><tr><td>DevOps tools</td><td>Prometheus</td><td></td><td>Apache License 2.0</td></tr><tr><td>DevOps tools</td><td>Grafana</td><td></td><td>Apache License 2.0</td></tr><tr><td>Messaging</td><td>Apache Kafka</td><td></td><td>Apache License 2.0</td></tr><tr><td>Web Server/HTTP proxy server</td><td>Nginx</td><td></td><td></td></tr></tbody></table>


---

# 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.openg2p.org/1.2/platform/technology-stack.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.