For firms whose data already sits in their cloud.
Exalt Reserve
For banks and financial firms whose data already sits in AWS, Azure or Google Cloud. Exalt Reserve deploys open models, retrieval, agents and monitoring into that account, reachable only from your private network.
Where a bank starts.
The data is already in your cloud
If your data already sits in AWS, Azure or Google Cloud, Reserve deploys into that account rather than adding an Exalt-hosted service.
A new AI service is a new third party
The Interagency Guidance on Third-Party Relationships, issued by the Federal Reserve, the FDIC and the OCC in June 2023, describes a life cycle for each relationship: planning, due diligence and selection, contract negotiation, ongoing monitoring, and termination.Interagency Guidance on Third-Party Relationships
Subcontractors are part of the review
The same guidance counts a third party's reliance on subcontractors among the things a bank evaluates in due diligence.
Your review
Your organization runs its own review and stays responsible for its conclusions.
Same question. Different access.
Two people ask Exalt Reserve the same question. Each answer comes only from the documents that person can read.
Signed in as a third-party risk analyst
- A third-party risk analyst asks: "What did due diligence find on the new payments vendor?"
- The answer comes from the vendor due diligence file and cites it. The question, who asked and the source shown are recorded in the audit log.
- The citation opens the vendor due diligence file at "Findings", with the passage highlighted.
Signed in as a branch operations lead
- A branch operations lead asks the same question.
- They cannot read the vendor due diligence file, so the answer never mentions it. It comes from the third-party risk policy, which says who to ask.
- The citation opens the third-party risk policy at "Vendor reviews", and the audit log records the question, who asked and the one source shown.
Illustrative. A demonstration workspace, not a customer session.
What sits in your account.
- Models, retrieval, agents and monitoring run inside your own AWS, Azure or Google Cloud account. This is not an Exalt-hosted shared service.
- Open models self-hosted in your account are the default: Llama, Mistral, Qwen, Gemma and DeepSeek. Which models run, and whether a use case also uses an outside AI service, is decided with you.
- Reachable only from your private network, with no public endpoint. People sign in through your own identity provider.
- Data is encrypted at rest and in transit.
- Exalt runs a management plane outside your account. It holds no customer content.
- Two bills: Exalt's software, and your own cloud bill. You keep the data, models, vector stores, credentials and subscription.
- An audit log of questions, answers and admin actions is kept in your own cloud account, and your admin sets how long history is kept.
Start with the account you already run.
Bring the cloud account, the material you would put to work and the person who reviews your vendors. The consultation starts with those three.