On this page
- Which REC registries does Solas connect to?
- How do transfers and retirements work across every registry?
- What does non-custodial registry operations mean?
- How does Tasks keep a complete record of registry activity?
- How do approval policies and custom roles control who can move certificates?
- How do multiple connections, sandbox and alerts help teams at scale?
- How do trades and registry deliveries connect?
Registry Gateway was built around a simple goal: one connection to the registries your portfolio touches, instead of a login for each. Recent work has focused on two things operations teams asked for most: coverage of every major registry, and more control over what moves and when. Here's what's new in Solas.
Quick Answer: Solas is REC registry software that connects to 10+ U.S. and international registries, including M-RETS, PJM-GATS, WREGIS, NEPOOL GIS, NYGATS, ERCOT and Evident (I-REC). Teams can transfer and retire certificates on every connected registry, with a reason recorded for each action, approval policies, and a full task log. Certificates never leave the customer's own registry accounts, because Solas is non-custodial.
See how Solas connects to every registry your portfolio touches → Solutions
Which REC registries does Solas connect to?
Solas now connects to 10+ REC registries through Registry Gateway, with NYGATS, NAR, MIRECS, NC-RETS and ERCOT joining M-RETS, WREGIS, PJM-GATS, NEPOOL GIS and Evident (I-REC).
Every registry signs users in differently. Some use API keys, some use a username and password, and some add two-factor codes. Registry Gateway asks only for what each registry needs, then handles the connection from there. Your team connects the registry accounts it already has.
How do transfers and retirements work across every registry?
You can transfer and retire certificates on every registry connected to Solas, from the same workflow. Pick the registry, select the certificates, choose the reason, and confirm. Solas sends the action to the right registry and updates your inventory when it completes.
Reasons on every action. Retirements and transfers both carry a reason, so each record says why certificates moved, not just that they did. For retirements, that includes state program options where a registry supports them, such as specific compliance programs in PJM-GATS. For example, a supplier retiring certificates for one state's renewable portfolio standard records that program on the retirement itself, so the compliance filing and the registry record match.
Batch retirements. Compliance season means retiring large volumes against several programs. Teams can now retire in batches, and queue the next batch while earlier ones process. Large transfer and retirement requests are split into smaller registry submissions automatically, so a big compliance run doesn't fail on a registry's size limits.
Incoming transfers. Where a registry supports it, incoming transfers arrive in Solas for your team to accept or reject. That gives you a review step before a counterparty's delivery lands in your account.
A retirement without a reason is a record. A retirement with a reason is evidence.
What does non-custodial registry operations mean?
Non-custodial registry operations means Innovo never takes custody of your certificates. Your RECs stay in your own registry accounts, under your own registry relationships, the whole time. Solas acts on those accounts with the access you grant, and nothing moves to an Innovo-held account along the way.
That design has practical consequences:
- Your registry standing doesn't change. Accounts, subaccounts, facilities and compliance history stay exactly where they are.
- The registry stays the source of truth. If someone on your team executes an action directly in a registry portal, Solas picks it up on the next sync. Your inventory and history in Solas reflect it, whether or not the action started in Solas.
- You can stop at any time. Disconnecting a registry from Solas doesn't move or change a single certificate.
For teams that have to answer to auditors and regulators, this matters. The registry remains the system of record, and Solas is the operating layer on top of it.
Your certificates stay where they are. Solas makes them easier to act on.
How does Tasks keep a complete record of registry activity?
Tasks is the log of every action across Solas. It records who did what, when, on which registry and account, and whether it succeeded. That covers registry syncs, transfers, retirements, approvals and tag changes, whether a person started them or the platform did.
From Tasks, teams can:
- See transfer and retirement history across every connected registry in one place, instead of exporting it from each registry portal.
- Open any task to see its details and the certificates involved.
- Retry a failed task without rebuilding the request, for example after a registry outage or an expired credential.
For organizations where REC operations used to live in one person's spreadsheets and logins, Tasks turns that personal knowledge into a shared, searchable record.
How do approval policies and custom roles control who can move certificates?
Approval policies let you require sign-off before certain actions reach a registry. You define when transfers, retirements or trades above a dollar threshold need approval, and name who can approve. Approvers are notified by email, and every approval is logged in Tasks.
For example, a trader can prepare a transfer to a counterparty, but nothing is sent to the registry until a designated approver confirms it.
Approval policies work alongside roles. Beyond the standard Admin, Member and View Only roles, organizations can create custom roles with their own set of permissions. A compliance lead might be able to retire but not transfer, or a back-office analyst might see inventory and history without being able to act on it. Together, roles and approval policies give operations leads control over who can initiate actions and who can release them.
How do multiple connections, sandbox and alerts help teams at scale?
Large organizations rarely have one registry account. Solas now supports several connections to the same registry, so separate trading desks or legal entities can keep their accounts, credentials and activity apart. Teams can filter inventory by connection to make sure they act only in the account they mean to.
- Sandbox and production. Teams can test workflows against registry sandbox accounts, then switch to production with real certificates.
- Credential alerts. When a registry rejects stored credentials, for example after a password change, Solas notifies your team so syncs don't silently stop.
- Counterparties from registry data. Counterparties your organization transacts with in the registries are added to your address book automatically.
How do trades and registry deliveries connect?
When you deliver certificates for a trade, the transfer opens directly on the trade, using the same registry workflow as any other transfer. The trade shows where delivery stands, from awaiting delivery through delivered, alongside the invoice and payment status. The commercial record and the registry record stay together, so no one has to reconcile them later.
Every update in this post points the same way: fewer places to look, and fewer steps between a decision and the registry.
How does Innovo support registry operations?
Solas is Innovo's REC operations platform, built as infrastructure for energy commodity markets. Registry Gateway connects to your existing accounts on 10+ registries. Inventory normalizes certificates across them, transfers and retirements run on every connected registry with reasons and approvals, and Tasks logs every action. Operations are non-custodial: certificates stay in your registry accounts, and activity done directly in a registry shows up in Solas.
Everything in the platform is also available through the API, with sandbox and production environments, so teams can run the same operations from their own systems. Innovo is SOC 2 Type II certified.
The registries aren't going to standardize themselves. Solas does it for them, and leaves your certificates exactly where they belong.
Related reading
- How Solas replaces a patchwork of registry logins: the original walkthrough of Registry Gateway, Inventory, tags, Transfers and Retirements.
- REC registry use cases: how three types of energy companies use Solas: how advisory firms, ETRM platforms and retail suppliers put these features to work.
- How to manage REC inventory across multiple registries: keeping one source of truth when holdings live in several registries.
Frequently Asked Questions
What is REC registry software?
REC registry software connects to renewable energy certificate registries so teams can view inventory and run transfers and retirements without logging into each registry portal separately. Solas connects to 10+ registries and standardizes their data and workflows in one place.
Does Innovo take custody of my RECs?
No. Solas is non-custodial. Certificates stay in your own registry accounts at all times, and Solas acts on them only with the access you grant. Disconnecting a registry doesn't move or change any certificates.
What happens if I make a transfer directly in the registry?
Solas picks it up on the next sync. Your inventory, transfer history and retirement history in Solas reflect actions taken in the registry itself, not just actions started in Solas.
Can I record a reason for a retirement?
Yes. Every retirement and transfer in Solas carries a reason, including state compliance program options where the registry supports them. The reason is saved on the record and appears in your history and exports.