Most teams managing REC portfolios aren't dealing with one registry. They're dealing with multiple, each with its own login, its own data structure, its own quirks. The operational layer stitching them together is usually a spreadsheet and someone who knows which portal to use for what. Registry Gateway replaces that layer.
Quick Answer: Registry Gateway is a feature within Solas, Innovo's REC operations platform, that connects to U.S. and international REC registries through a single connection point. It is the operational backbone that powers the rest of the Solas platform: Inventory, Transfers, Retirements, and Task History all draw from the unified registry connection Registry Gateway establishes.
What is Registry Gateway and what does it replace?
Registry Gateway is the operational backbone of Solas. It is the connection layer between your team and every registry your portfolio touches, replacing the combination of individual logins, manual exports, and spreadsheet reconciliation that most teams currently use to manage multi-registry positions.
The problem it addresses is structural. Each registry—M-RETS, WREGIS, NEPOOL, PJM-GATS, NYGATS, and others—operates independently. Different data formats, different workflows, different interfaces. Teams managing positions across more than one registry are effectively maintaining separate operational processes for each one, with no shared source of truth between them.
Registry Gateway collapses that into a single connection. It powers everything else in Solas: the Inventory view, Transfers, Retirements, and Task History all operate on top of the registry connection Registry Gateway establishes.
How does Registry Gateway connect to multiple registries?
Registry Gateway connects to the full landscape of U.S. and international REC registries through a single gateway, using your existing registry credentials. You don't create new accounts or transfer any ownership. Your existing registry relationships, sub-accounts, and facilities stay intact.
Once connected, all certificate holdings across every linked registry and sub-account become available across the Solas platform automatically. The platform handles the registry-specific plumbing: authentication, data retrieval, and action routing to the correct registry for each certificate.
The registry is a parameter. Your team doesn't need to know which portal handles what. Registry Gateway does.
For organizations with positions across multiple registries, sub-accounts, and organizational entities, this means a single operational surface that covers everything, without requiring the institutional knowledge of which login goes where.
How does Registry Gateway power inventory management in Solas?
Inventory is the Solas module where every certificate across every connected registry appears in one consolidated holdings view. Registry Gateway is what makes that possible: it pulls and normalizes data into a consistent model so that attributes like RPS eligibility, tier and class designations, and vintage are presented identically regardless of which registry the certificate came from.
From the Inventory view, users filter by any data point to build exactly the view their workflow requires: a client allocation summary, a compliance position by program, or a raw export for an accounting system. Column order, visible fields, and saved views are configurable per user.
One source of truth doesn't mean one view. Every user sees the same data, shaped differently.
| Manual registry management | Solas | |
|---|---|---|
| Position refresh | Log into each registry separately, export, paste into spreadsheet | Automatic sync across all registries, current across the platform |
| Data normalization | Manual cross-reference across registry-specific exports | Standardized model: RPS eligibility, tier/class, vintage consistent in every row |
| Multi-registry view | Separate exports stitched together | One consolidated holdings view, filterable by any attribute |
| User customization | None | Column order, visible fields, customizable organization |
How do custom tags work in Solas Inventory?
Custom tags are applied in the Inventory module and let you attach any internal label to any certificate or batch. Trade confirmation numbers, client accounts, compliance years, counterparty names, any organizational logic your team relies on can be encoded as a tag directly in Inventory.
Tags carry through to exports, transfers, and retirement records. Your output reflects your internal structure rather than requiring manual re-sorting.
Common tagging applications:
- Allocating inventory to named client accounts before transfer or retirement
- Flagging certificates by RPS program, compliance year, or carve-out category
- Marking positions as reserved or staged without altering the underlying registry record
Tags don't modify the certificate in the registry. They impose your operational logic on the data inside Solas without changing the source record.
How do transfers work in Solas?
Transfers is the Solas module for executing new certificate transfers, tracking in-progress activity, and reviewing historical transfer records. From Transfers, users select certificates, specify the recipient, and confirm. Solas queues the action through the appropriate registry and triggers an automatic resync once it completes.
An inbox and outbox workflow tracks the full status of each transfer, so no transaction disappears into a registry queue without visibility. Historical transfers are accessible in the same module, giving teams a complete record of what moved, when, and to whom.
Most reconciliation errors in REC trading happen not because data is wrong, but because it's invisible at the moment it matters.
For workflows that require review before execution, Solas supports approval policies. Approvers are assigned by role within the Solas platform. A trader initiates; a designated approver confirms before the registry action fires.
How do retirements work in Solas?
Retirements is the Solas module for executing new certificate retirements and reviewing historical retirement records. From Retirements, users select certificates, choose the applicable retirement reason, add any notes, and confirm. Solas initiates the retirement via the relevant registry and logs the full record.
For organizations managing bulk retirements, Solas lets you select and retire across multiple certificates in a single workflow. Historical retirements are accessible in the same module, so documentation is always available without hunting through registry portals.
Like transfers, retirements support approval policies. The approver is a named Solas member with the appropriate role, and the approval is captured in Task History.
How does Task History create an audit trail?
Task History is the Solas module that logs every action across the platform: who did what, when, and where. This covers registry connections, inventory syncs, tag assignments, transfers, approvals, and retirements. Nothing happens silently.
Critically, Task History captures both user-initiated actions and platform-initiated ones. When Registry Gateway runs a sync, that sync appears as a logged event showing which certificates changed, when, and why. Task History shows who initiated what and when. For organizations where REC operations have historically lived in one person's spreadsheets and logins, this is the shift from key-man risk to institutional memory.
How does Innovo support registry operations at scale?
Solas is Innovo's REC operations platform, built as financial market infrastructure rather than registry software. Registry Gateway is the feature that handles registry connectivity into a single interface with normalized data and a full activity log. Inventory, Transfers, Retirements, and Task History all operate on top of the connection Registry Gateway establishes.
Every operation in Solas is accessible via API, enabling direct integration with trade capture, risk management, compliance reporting, and ERP systems. Custom tags, configurable views, and approval policies sit on top of the same underlying data model, so the entire operational surface reflects how your team works rather than how the registries are structured.
The REC market has a connectivity problem, not a data problem. The certificates exist. The records exist. What's been missing is a connection layer that treats all of them the same way.
Registry Gateway is that layer that makes unified inventory, structured data, and automated workflows possible. What we're building on top of this in Solas is what takes things further.
Frequently Asked Questions
Does Registry Gateway replace my existing registry accounts?
No. Registry Gateway connects to your existing accounts using your current credentials. Your registry relationships, sub-accounts, facility records, and compliance standings remain unchanged. Solas reads your position and routes actions through the same access rights your team already holds.
How is Registry Gateway different from connecting to each registry directly?
Connecting to registries directly means maintaining separate credentials, separate workflows, and manually reconciling them into a single view. Registry Gateway normalizes all of that into one connection, one data model, and one activity log captured in Task History.
How does Task History work for compliance purposes?
Task History logs every action across the Solas platform with a timestamp and the user who executed it. This covers syncs, transfers, retirements, tag assignments, and approvals. The log is exportable.
Can Solas integrate with our ETRM or trade capture system?
Yes. The Solas API exposes every platform operation through a single integration. You can trigger retirements, sync inventory positions, and push data directly into trade capture, risk management, and compliance systems in real time. There is no middleware required and no manual export step between the registry and your internal systems.