> 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/operations/deployment.md).

# Deployment

OpenG2P Deployment — choosing and running a sandbox or production deployment.

OpenG2P supports two deployment shapes. Pick the one that matches your stage, then follow that section — the prerequisites and steps differ.

|                           | **Sandbox** (Single-Node)                                    | **Production**                                                                                                                                               |
| ------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Use for**               | Evaluation, dev/QA, demos, pilots-on-a-budget                | Pilots and production rollouts                                                                                                                               |
| **Machines**              | 1 VM                                                         | **Minimum:** 4 VMs (RP, Compute, Storage, Backup). **High-Availability:** more nodes of the same shape — HA control plane, redundant RPs, PG primary/replica |
| **TLS**                   | Self-signed local CA (built in)                              | Customer CA cert (commercial / sovereign)                                                                                                                    |
| **DNS**                   | Local — dnsmasq, `*.<local_domain>` (built in)               | Customer DNS (admin + citizen records)                                                                                                                       |
| **Admin access**          | Wireguard / VPC — private by default; optional public opt-in | Wireguard VPN + private channel                                                                                                                              |
| **Procurement lead time** | None — just a machine                                        | Compute + certificate (2–4 weeks)                                                                                                                            |

{% hint style="info" %}
**Rule of thumb.** To get started quickly with a sandbox or two (dev/QA), use **Single-Node**. For pilots and production, use the **Production** path — strongly recommended. The Production path has two configurations sharing the same architecture: **Minimum** (a four-node setup — Reverse Proxy, Compute, Storage, and a required Backup node) and **High-Availability** (more nodes added for redundancy — supported architecture, not yet automated). If you do run a pilot on single-node, ensure backups are in place (data on Kubernetes-hosted PostgreSQL must be migrated to a standalone PostgreSQL server when you move to production — see the [migration guide](/operations/deployment/deployment-guide/transitioning-postgresql-from-docker-on-k8s-to-standalone-postgresql.md)).
{% endhint %}

* **Sandbox** → [Single-Node automation](/operations/deployment/single-node-automation.md) (prerequisites are included on that page)
* **Production** → start with [Prerequisites & Procurement](/operations/deployment/infrastructure-setup/prerequisites-procurement.md), then the [infrastructure automation](/operations/deployment/infrastructure-setup/production-automation.md)

For the conceptual picture (deployment models, architecture, channel separation), see [OpenG2P Deployment Architecture](/operations/deployment/openg2p-deployment-model.md).


---

# 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/operations/deployment.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.