Pricing

Priced per node, by how much redundancy you need.

Every tier is the same software with all twenty-four modules. What changes between them is what happens when a machine fails, and how quickly you are back — stated as an RPO and an RTO rather than as a promise.

Standard

Single node, continuous WAL archive, nightly full, offsite encrypted copy

Annual licence, per node

Quoted against your mandate count and migration scope.

RPO: ~5 min
RTO: 2–4 h

Dedicated node — own Postgres, object store and backups
Own NSDL and CDSL credentials, held only on your machine
Continuous WAL archive with a weekly automated restore test
72-hour offline grace if the control plane is unreachable

An RTA with a handful of mandates

Get a quote

Resilient

Most choose this

Primary plus hot standby in the same datacentre, streaming replication, manual promotion

Annual licence, per node

Quoted against your mandate count and migration scope.

RPO: ~0
RTO: 10–15 min

Everything in Standard
Hot standby with streaming replication
Human-confirmed promotion — no split-brain risk
99.9% monthly availability

The default. Most will want this.

Get a quote

Critical

Resilient plus an asynchronous DR node in a second Indian region, quarterly failover drill

Annual licence, per node

Quoted against your mandate count and migration scope.

RPO: ~0 local, ~15 min regional
RTO: ~30 min regional

Everything in Resilient
DR node in a second Indian region
Contractual quarterly failover drill
A failover that has never been rehearsed is not a failover

Large issuer books, high public visibility

Get a quote

Availability commitments: 99.5% monthly on Standard, 99.9% on Resilient and Critical, measured on the node and excluding maintenance windows you defer yourself.

Every tier

There is no feature-gated edition.

An RTA with four mandates has the same statutory obligations as one with forty. Charging them less for the audit trail would be charging them less for the thing that keeps their registration.

A dedicated node: own server, database, object store, depository credentials, backups and encryption keys

All 24 modules — licensing is per node, not per module

Unlimited named users with role and mandate scoping

Signed releases with staged rollout rings and automatic rollback on failed health

Deferrable updates — an RTA mid-dividend-run can defer a non-security release

White-labelling: your name, logo, palette, sender domain, custom domain and certificate

Continuous WAL archive, nightly full, offsite encrypted copy, weekly automated restore test

Migration support: staging schema, per-issuer reconciliation reports and a parallel-run period

Questions we get

The ones that decide it.

Why is pricing per node rather than per folio?

A node is the unit of isolation and the unit of cost. Folio-based pricing would mean us counting your register, which means us holding data about your register — the whole point of the architecture is that we do not.

What happens to our register if rgs.plus disappears?

Nothing, for at least seventy-two hours of full local operation without the control plane, and indefinitely thereafter with the stack you already hold. The node is your server, the database is your database, the backups are yours, and the depository credentials never left your machine.

Is there a per-issuer or per-mandate charge?

Activity-based charging exists inside the product so you can bill your own issuers per request, per folio, per corporate action and per report. What you charge them is your business; our licence is per node.

Can we start on Standard and move up?

Yes. Standard to Resilient adds a hot standby with streaming replication; Resilient to Critical adds a DR node in a second Indian region and a contractual quarterly failover drill. Neither is a rebuild.

Who holds the encryption keys?

You do. Depository credentials are encrypted at rest on the node with a key the control plane never holds.