Services & institutional customers
Sections ↑R3 supplies software and network technology for multi-party institutional workflows. Corda’s model distinguishes authenticated legal entities and application-defined transaction processes from a public permissionless trading network. Participating institutions decide which information they share and how their contractual and technical rules apply.[2]
CorDapps encode application workflows, while network identities and notary mechanisms support validity and uniqueness checks. The technology can provide a shared record for obligations or assets, but it does not by itself supply underlying legal title, settlement cash, regulatory recognition or a secondary market for the assets represented.[2]
R3 shifted its public strategy in 2025 toward bridging institutional financial assets and public-chain liquidity, announcing collaboration with the Solana Foundation. This direction is distinct from its existing Corda Enterprise platform, and a prospective customer should identify which technology, foundation and governance arrangement is actually being proposed.[5]
Corda technology families
| Family | Role | Do not assume |
|---|---|---|
| Corda Open Source | Ledger/application technology for governed networks. | A paid support entitlement.Source 2 |
| Corda Enterprise | Commercial enterprise software family. | One support window for all versions.Source 2Source 3 |
| CENM | Corda Enterprise Network Manager. | It is the same thing as an application contract.Source 2 |
| Corda protocol | Separately promoted Solana-native RWA/vault initiative. | It is a drop-in replacement for a private Corda 4 deployment.Source 6Source 7 |
Core application and network concepts
| Component | Purpose |
|---|---|
| States | Represent the facts or obligations being recorded.Source 2 |
| Contracts | Specify transaction-validity rules.Source 2 |
| Flows | Coordinate the application’s multi-party workflow.Source 2 |
| CorDapps | Package application logic for the network.Source 2 |
| Notary | Supports transaction uniqueness checks.Source 2 |
Platforms & integrations
Sections ↑A Corda deployment involves application contracts, flows, node identities, key management, notary selection, communication paths and participant permissions. Unlike a conventional centralized API, successful processing depends on multiple parties agreeing to the same transaction and meeting the network’s validation rules.[2]
Network identity and operating controls
| Element | Institutional significance |
|---|---|
| Verified participants | Legal identity and network admission are part of the model.Source 2 |
| Node operations | Participants operate the software and application services appropriate to their role.Source 2 |
| Signing keys | Transactions depend on authorised signatures and key management.Source 2 |
| Shared information | The application determines what is exchanged among involved parties.Source 2 |
Version families in the documentation
| Documentation family | What the catalogue proves |
|---|---|
| Corda Enterprise 4 | Versioned enterprise documentation is available.Source 2 |
| Corda Open Source 4 | Separate versioned open-source documentation.Source 2 |
| Corda 5 | A different software generation is documented.Source 2 |
| CENM | Network-management documentation has its own versions.Source 2 |
A version appearing in the documentation index is not proof that it remains in standard support. Deployment decisions should use the lifecycle entry for the exact product and release.[3]
Pricing & commercial terms
Sections ↑Open-source availability is not the same as a free enterprise network. R3 documents Corda open-source and enterprise editions, with network-management tools and applications. Firms must budget the correct commercial support, hosting, security controls, development and participant onboarding rather than quoting only the software acquisition price.[2]
The support table is release-specific: versions have separate maintenance, security and end-of-support dates. Running a version beyond its support window creates a migration and security obligation even where the software still operates technically.[3]
The December 2025 Corda protocol announcement describes a planned Solana-native curated-yield product on behalf of R3 Foundation. No fixed investor return, public enterprise licence or guaranteed deployment timetable can be established from that announcement; it should not be treated as an investable offer in this profile.[6]
Different commercial relationships
| Relationship | Commercial boundary |
|---|---|
| Open-source use | Software availability is separate from paid service commitments.Source 2 |
| Enterprise deployment | Licensing and support follow the applicable enterprise agreement.Source 3 |
| Network application | Integration and consortium operating costs are distinct from the base software.Source 2 |
| RWA vault participation | Protocol product terms and eligibility are separate from an enterprise software purchase.Source 7 |
Implementation & delivery
Sections ↑Institutional onboarding requires governance documents identifying legal parties, the network operator, role permissions, notary and transaction finality policy, incident authority, disputes and exit procedures. Technical acceptance should check what each participant can see or sign and how applications behave when a counterparty is unavailable.[2]
Multi-party deployment dependencies
| Dependency | Why it matters — editorial analysis |
|---|---|
| Governance | Participants need admission, change and exit rules.Source 2 |
| Application versions | Counterparties must run compatible transaction workflows.Source 2 |
| Notary and identity | Uniqueness and identity infrastructure must match the network design.Source 2 |
| Upgrade schedule | Supported versions and coordinated upgrades affect continuity.Source 3 |
Support & contacts
Sections ↑R3 maintains public technical documentation and a developer route. Enterprise support and response terms require the applicable agreement; the support lifecycle notes should be used to verify that the chosen versions remain within relevant maintenance and security windows.[4]
Published contact and documentation routes
Scope Official corporate channel and strategic programme information.
Release lifecycle checks
| Check | Published distinction |
|---|---|
| Product family | Enterprise Corda and network-management software have separate release information.Source 3 |
| Release version | Maintenance status must be assessed for the selected version.Source 3 |
| Security maintenance | Security coverage is governed by the relevant lifecycle and agreement.Source 3 |
| Technical reference | Public documentation explains features but is not a contractual response SLA.Source 4 |
Permissions & service scope
Sections ↑Corda is technology for recording and enforcing agreed workflows; it does not confer exchange, custody, banking or securities-issuance permission. Transfer restrictions and title rules must be established by governing agreements and applicable law.[2]
Ledger records and external legal effects
| Technical result | Separate requirement |
|---|---|
| Contract-valid transaction | Legal enforceability of the real-world arrangement.Source 2 |
| Unique state transition | Underlying title and the authoritative ownership register.Source 2 |
| Token transfer | Custody, redemption and asset-backing arrangements.Source 5 |
| Shared record | Regulatory permission for the participants’ activities.Source 2 |
Operator & evidence
Sections ↑Corda protocol: announcement and current status
| Evidence date | Statement | Editorial treatment |
|---|---|---|
| 12 December 2025 | R3 announced a Solana-native curated-yield protocol with an H1 2026 target. | A planned date, not proof of launch.Source 6 |
| 26 October 2026 check | Current site still displays a waitlist and “Launching 2026”. | Public launch is not represented as completed.Source 7 |
| Current site | Corda Foundation is named as governing organisation; R3 as builder. | Use the current foundation name while retaining the historical announcement context.Source 7 |
Corporate group and protocol governance
| Identity | Published evidence |
|---|---|
| R3 group | September 2025 privacy policy identifies R3 HoldCo LLC together with its subsidiaries.Source 8 |
| Protocol governance | Current protocol site identifies Corda Foundation.Source 7 |
| Technology builder | Protocol site identifies R3 as builder and technology partner.Source 7 |
- Operator
- R3 HoldCo LLC and subsidiaries; Corda Foundation separately governs the promoted protocol
- Service scope
- Institutional distributed-ledger technology for governed transaction networks and CorDapps, with enterprise and open-source software and a separately promoted Solana/RWA initiative.
- Customer types
- Banks; Market infrastructures; Capital-market participants; Technology integrators; Tokenisation projects; Consortia
- Delivery
- On premises; Hosted; Hybrid
- Pricing publication
- Public and quoted pricing
- Platforms
- Corda 4 Enterprise; Corda Open Source; Corda Enterprise Network Manager; R3 Developer Platform
- Integrations
- CorDapps; Corda node APIs; Enterprise Network Manager; Corda network notaries; Solana ecosystem tools
- Implementation
- A Corda network requires participating legal entities, governance, notary configuration, application deployment, identity and signing infrastructure and version-lifecycle planning.
- Support
- Corda documentation, enterprise agreements and developer ecosystem routes; supported versions and security-maintenance windows vary by release.
- Permissions and regulatory scope
- Enterprise ledger software does not confer permission to issue, custody or trade regulated assets. The separately governed Corda protocol has its own eligibility and product arrangements.
Provider metadata checked 26 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8
Additional information
Sections ↑Public-chain and enterprise workflows
| Dimension | Private enterprise deployment | Promoted protocol |
|---|---|---|
| Users | Admitted institutional network participants. | Eligible users of a separately governed product.Source 2Source 7 |
| Assets | Defined by the installed CorDapp and legal arrangements. | RWA exposure through the proposed vault structure.Source 2Source 7 |
| Risk boundary | Network, application and participant dependencies. | Additional token, smart-contract, custody and redemption dependencies.Source 2Source 7 |
Sources & further reading
- R3 corporate activities and recent announcements R3 · Accessed 22 Oct 2026
- R3 Corda platform documentation and versions R3 · Accessed 22 Oct 2026
- R3 documentation and lifecycle schedules R3 · Accessed 22 Oct 2026
- Technical API documentation index R3 · Accessed 22 Oct 2026
- R3 collaboration with Solana Foundation R3 · Accessed 22 Oct 2026
- R3 Foundation Corda protocol announcement R3 · 12 Dec 2025 · Accessed 22 Oct 2026
- Corda protocol: current site and waitlist Corda Foundation · Accessed 26 Oct 2026
- R3 privacy policy and group identity R3 · Accessed 26 Oct 2026
This profile reports dated public information, including provider-published services and terms. It does not independently test or guarantee service delivery, integrations or performance. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.