Deploy and operate DALP: plan, install, and run an instance

A DALP Instance deploys the Platform API, the Console and supporting services into your Kubernetes cluster. You supply the datastores, the ingress and the ledger endpoints. For a new deployment, plan the topology and hosting, prepare what the instance connects to, install, then connect sign-in, custody and observability. Go to runbooks for an incident, or Upgrades and migrations for a release window.

Plan the shape first

Two decisions come before any chart runs, because the install commits you to them: how the platform is sized, and whose infrastructure it runs on.

Topologies

The four separately sized Platform API roles, their replica ranges and PgBouncer cost.

Hosting and access

Whose infrastructure runs the instance and how much of it the vendor can reach.

Evidence for a security, procurement or audit review

A reviewer who accepts or audits an instance reads these four pages. The SettleMint Trust Centre holds the security and compliance documentation a security review or audit asks for.

Security and compliance posture

The control layers a reviewer checks before accepting an instance.

Supply chain and support policy

Image provenance, version-to-build mapping, patched release lines and fix reporting.

Third-party components and licences

The GPL-3.0 and AGPL-3.0 services the charts deploy, and how to switch them off.

Exit and data portability

Where each kind of data lives, which exports exist and what stays if you leave DALP.

Prepare what it connects to

Confirm every endpoint, credential and unit of capacity the instance needs, including the datastores and ingress you supply yourself, before you install.

Networks

Declare the ledger networks the instance settles on, validated before it serves traffic.

Gas settings

The per-network gas keys the instance reads, their layer order and calibrated chains.

Prerequisites

The endpoints, credentials and cluster capacity to have ready before you run the charts.

Price source prerequisites

The network paths, size caps, secret store and alerts to set before a price source runs.

Install, connect, and keep it current

Install runs the charts in the order that avoids a failed first install. Once the instance runs, connect an external identity provider and point telemetry at your own collector or the bundled stack, both through a values change that needs no reinstall. Every later version moves through one helm upgrade that treats the whole release as one unit. Upgrade to DALP 3.2 is the runbook for the move from 3.1 or 3.0.

Install

The charts, the CRD bundle and the Gateway API CRDs to apply before an HTTPRoute.

SSO

Connect an OpenID Connect provider that replaces local sign-in on the Console.

Observability

Export metrics, logs and sampled traces over OTLP to your collector or the bundled stack.

Upgrades and migrations

One helm upgrade moves every component, and its migration Job gates it by default.

Connect custody and funding

Set up the custody provider each organisation signs with, and the tokens investors can deposit.

Fireblocks policy

The Fireblocks policy rules each DALP vault needs with account abstraction off and on.

Ripple policy

The properties DALP sets on every Ripple intent and how to write matching policies.

Utila setup

What the operator and the Utila vault administrator prepare before adding Utila.

Utila signing agent

Deploy the customer-run Utila signing agent beside DALP: values, keys and network path.

Deposit funding instructions

Switch on the custody gateway and choose the coins clients can deposit.

Back up and recover

Backup and disaster recovery

In-cluster Velero backup, what your datastores must back up and how to prove a restore.

Runbooks

Start from the symptom: a pod not Ready, stalled indexing or failing webhooks.

When the vendor runs the infrastructure for you, the install and upgrade pages describe work that happens on your behalf, while the plan and integrate pages describe the instance you sign in to. SettleMint status reports current availability and incidents for SettleMint-hosted environments.

Plan the shape first#