Topic starter
25/10/2026 11:03 am
TL;DR: Low resource use and a 0% error rate point to scaling headroom in Procivis research on digital identity, with Procivis reporting 287 MB of RAM and 0.61 vCPU at 20 credentials per second. Identity services still need usable performance under concurrency, constrained networks and edge deployment conditions.
Editorial analysis by NHI Mgmt Group, based on content published by Procivis: “Procivis One: High-Performance Digital ID Core, 10× Faster Than Others”.
By the numbers:
- Procivis One Core consumed just 287 MB of RAM and 0.61 virtual CPU while issuing 20 credentials per second.
- In idle state, Procivis One Core consumes just 19 MB of RAM and 0.029 virtual CPU.
Key questions
Q: When does slow identity performance become a governance problem?
A: Slow identity performance becomes a governance problem when delays interfere with timely provisioning, deprovisioning, approvals, or certification.
Q: What are the signs that an identity architecture will not scale?
A: Frequent retry loops, rising error rates, uneven response times and heavy resource consumption under moderate load are the clearest warning signs.
Q: What should security teams test before going live with a new identity platform?
A: They should test authentication flows, tenant mapping, MFA enrollment, passwordless behavior, and any step-up controls in staging before production migration.
Practitioner guidance
- Benchmark identity services under realistic concurrency Measure issuance, verification and storage under the concurrency levels your production environment will actually see, not just single-user tests.
- Test degraded-network user journeys Validate offline, low-bandwidth and intermittent-connectivity flows for the specific mobile and field environments you plan to support.
- Set resource ceilings for every target runtime Define memory and CPU budgets for server, mobile and edge deployments before you standardise the identity architecture.
Bottom line: The article argues that digital identity platforms fail when performance is treated as a feature rather than a design constraint.
Glossary terms: Identity Throughput, Operational Resilience, Offline Identity, Control Portability
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
27/10/2026 7:15 pm
Performance is part of identity governance, not a separate infrastructure concern. When a digital identity platform cannot sustain issuance and verification at scale, the governance problem is no longer abstract policy but practical availability. That shifts identity architecture from an administrative layer to an operational dependency, because users, wallets and relying parties all experience the control as latency, retries or failure. The practitioner conclusion is that performance thresholds belong in identity programme design.
A question worth separating out:
Q: Should teams optimise for portability or raw throughput in digital identity?
A: That depends on where the identity service must run. If the programme needs mobile, edge or offline support, portability and low resource use matter as much as raw throughput. If the service is centralised and high-volume, throughput and stability dominate. Most identity programmes need a balance, not a single metric.
👉 Read our full editorial: Performance and scalability define Procivis One's identity architecture
This post was modified 7 days ago by NHI Mgmt Group