Insights · Comparison
Timvero and Capital Refinery: what each does
Timvero treats the credit agreement as a first-class object and scores covenant breach probability. Capital Refinery reads the same documents to keep the credit committee's approval and conditions connected after the deal closes.
Timvero is a credit portfolio platform that models sponsors, borrowers, facilities and tranches as structured objects, authors covenants as policies-as-code, and scores breach probability under cash and PIK scenarios. Capital Refinery reads the credit agreement and compliance certificate a lender already receives, spreads the financials with figures traced to source, grades risk signals against the firm's own thresholds, and records committee conditions as tracked actions after approval. Credit teams run Timvero for risk modeling and Capital Refinery for the committee's record.
What Timvero is built for
Timvero is a credit portfolio platform built around a structured data model: sponsors, borrowers, co-lenders, funds, SPVs, facilities and tranches are all first-class objects. Covenants are authored as policies-as-code rather than kept as prose clauses, which lets the platform test them programmatically across the book.
On top of that model, Timvero's AI scores sponsor and borrower risk, predicts covenant breach probability, and models cash versus PIK coverage under multiple scenarios. For a credit team that needs portfolio-wide covenant modeling, that is a more purpose-built tool than a generic monitoring dashboard.
What Timvero is built for
- Covenant modeling authored as policies-as-code
- Sponsor and borrower risk scoring
- Breach-probability prediction under scenarios
- Cash versus PIK coverage modeling
What Capital Refinery is built for
- Reading the credit agreement and compliance certificate as filed
- Spreading the financials with figures traced to source
- Reporting headroom and drift on each reporting pack
- Recording committee conditions as tracked actions after approval
Where Timvero stops
Risk modeling answers what could happen. It does not, by itself, answer whether the decision the credit committee already made still holds. Timvero's breach-probability output is not bound back to the specific assumptions the committee approved at closing, so a rising breach probability does not, on its own, tell the team which approval condition that erosion actually threatens.
That is a different object from the one Timvero was built to produce. Policies-as-code covenant modeling and a structured record of the committee's conditions sit at different layers of the credit stack, and Timvero does not carry the second one.
How Capital Refinery works alongside Timvero
Capital Refinery does not model risk, and it does not integrate with Timvero. It reads the documents a credit team already receives, keeps figures traced to the source they came from, and keeps the committee's approval connected to what arrives afterward.
Read
Documents classified on arrival against a 41-family taxonomy, including the credit agreement and the compliance certificate, read to the clause as filed.
Spread and test
Statements spread to a standard structure with figures traced to source, then run through ten advisory reconciliation checks that flag rather than gate.
Grade and record
Risk signals graded against the firm's own policy thresholds, memo sections assembled from that cited evidence, and committee conditions recorded as tracked actions on the deal.
Timvero and Capital Refinery at a glance
The two read different inputs and answer different questions. Here is where each capability actually sits.
| Capability | Timvero | Capital Refinery |
|---|---|---|
| Covenants authored as policies-as-code | Yes, a core differentiator | Reads the credit agreement and compliance certificate to the clause as filed |
| Sponsor and borrower risk scoring | Yes, core capability | No; grades risk signals against the firm's own policy thresholds instead |
| Covenant breach probability modeling | Yes | No prediction; reports headroom and drift against the filed terms each period |
| Cash versus PIK scenario modeling | Yes | Runs five house stress scenarios instead, with a modeled first-breach quarter |
| Record of the committee's approval and its conditions | No | Yes; memo sections assembled from cited evidence, conditions recorded as tracked actions |
| Citation on each spread figure | Not its function | Yes, traced to source; cited to the page where a locator resolves |
Where Capital Refinery sits in the credit stack
Neither platform replaces the other. Timvero sits at the risk-modeling layer, scoring what could happen across the book. Capital Refinery sits at the layer above it, holding the record of what the committee actually approved and whether the documents arriving since then still match the terms as filed.
Timvero tells a team the breach probability. Capital Refinery tells the team what the committee conditioned the approval on, and whether the latest compliance certificate still clears it.
Questions
Is Capital Refinery an alternative to Timvero?
Usually no. Timvero models covenant risk and breach probability across a credit portfolio; Capital Refinery reads the credit agreement and compliance certificates a lender already receives and keeps the committee's approval record connected to them. They do different jobs.
Can I use Timvero and Capital Refinery together?
Yes. A credit team can run Timvero for portfolio-wide risk modeling and Capital Refinery for spreading the financials, grading risk signals against policy, and tracking committee conditions after approval. Neither reads from the other; each reads the source documents directly.
What does Timvero not do?
Timvero does not hold the credit committee's original approval, the assumptions behind it, or the conditions attached to it as a connected record. It scores breach probability; it does not track whether the approval basis still holds.
Does Capital Refinery predict covenant breaches like Timvero?
No. Capital Refinery does not run predictive breach modeling. It reads the compliance certificate to its filed terms and reports the headroom and drift on each reporting pack as it arrives.
Does Capital Refinery recompute covenants under the credit agreement's definitions?
No. Capital Refinery reads the compliance certificate to the clause as filed; recomputing a covenant under the agreement's own definitions is not part of the current read.