The feasibility study, made readable. Then a live scorecard across every placement in the captive, so the parent always knows where the retained risk sits.
A captive starts with a feasibility study: dense, actuarial, and delivered as a PDF the parent's CFO reads the night before the board vote. Then the captive goes live and the same parent gets a quarterly pack, a renewal deck, and a call from the captive manager when something drifts.
Keel closes that gap. The study becomes a decision the parent can actually read. Then the same numbers keep running as a live scorecard: every placement in the captive, retained against expected, cell by cell, updated as claims come in. The captive manager stops rebuilding the picture every quarter, and the parent stops learning about problems at renewal.
Keel takes the actuarial study your captive manager already produces and presents it to the parent as a decision, not a document.
Once the captive is live, the study's assumptions become the baseline and Keel tracks reality against them across every line and every cell.
Turn the feasibility engagement into the start of a monitoring relationship. One Keel deployment serves every captive you manage, on your brand.
See the retained layer the way you see the balance sheet: current, comparable, and without waiting for the quarterly pack.
The same scorecard the parent sees, scoped to your layer. Fewer surprises at the treaty renewal, and a cleaner conversation about collateral.
Ask the captive a question in plain language and get an answer with the arithmetic shown. Every response is logged, and nothing acts without a person approving it.
Your cells, your lines, your fronting and reinsurance arrangements. Keel is assembled to how your captive actually works, not a template everyone gets.
Build-and-handover puts the code in your walls. The managed subscription carries hosting and updates for you. Either way, the data stays yours.
Every assumption change, every re-run, every AI suggestion and who accepted it. Logged as it happens, so the board pack can always be traced back.
Either way the build is to your specifications and nothing trains our models. The difference is ownership: take the keys, or let us carry it.
One-time engagement
We build Keel to your captive's structure, deploy it inside your environment, and hand over code and documentation. Your team runs it from there. Support available on request.
Recurring engagement
We build to your structure, then run it for you: hosting, monitoring, new cells and lines as the captive grows, and model upgrades. The platform is licensed, not owned; your data and assumptions remain yours. Convert to full ownership at any time.
Thirty minutes, your team, and one real study. We'll show you what the parent would have seen, and what the scorecard looks like a year in.