> For the complete documentation index, see [llms.txt](https://wiki.datadike.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.datadike.com/pam/deploy-operate.md).

# Deploy and operate

| Page                                                                                 | What it covers                                                                                                                                                                                            |
| ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [System requirements](/pam/deploy-operate/requirements.md)                           | Deployment models, machine sizing, storage planning and platform dependencies for a DataDike PAM instance, with the figures DataDike publishes and the gaps you must confirm before you buy hard          |
| [Network and connectivity requirements](/pam/deploy-operate/network-requirements.md) | The connectivity the solution itself needs — who reaches the console and on which ports, what the solution originates outbound, how to publish it safely, and why it needs no internet access of its own. |
| [Install a single node](/pam/deploy-operate/install-single-node.md)                  | The documented path for bringing up one instance from the appliance image — console setup, DNS, first login, licence — and the parts of the procedure that only DataDike holds.                           |
| [Install a high-availability cluster](/pam/deploy-operate/install-cluster.md)        | What a high-availability deployment is made of, how it differs from a single node, the decisions to settle before the build, and how to prove the cluster actually tolerates losing a node.               |
| [Certificates and HTTPS](/pam/deploy-operate/certificates.md)                        | Serving the console over HTTPS: the name the certificate has to match, the Site URL setting that has to agree with it, and what breaks quietly when the two disagree.                                     |
| [Upgrade](/pam/deploy-operate/upgrade.md)                                            | What is established about upgrading the solution, the preparation you own before one, the version-specific traps on record, and how to verify an upgrade afterwards.                                      |
| [Availability and continuity](/pam/deploy-operate/availability-and-sla.md)           | Availability levels, redundancy, continuity objectives and the update model, for the SaaS and on-premises delivery modes.                                                                                 |
| [Back up and restore](/pam/deploy-operate/backup-and-restore.md)                     | Backing up the installation — database, configuration and recordings — where each of those actually lives, and the test restore that turns a backup into something you can rely on.                       |
| [Monitoring and health](/pam/deploy-operate/monitoring.md)                           | How to tell whether the installation is healthy: the health endpoint an external monitor should poll, the console screens that show component and task state, and the alerts worth subscribing to.        |