The ingredients
API documentation, test access, product and eligibility information, plus brand and compliance requirements.
Infrastructure, made understandable
A lot goes on
behind a simple quote.
Your customer sees a clear comparison. Behind it, Yeti connects the journey, the insurer’s quoting system and the information your team needs to run the partnership.
Microsoft AzureThe cloud foundation behind Yeti Engines
Different journeys.
One comparison engine.
The platform at a glance
Your brand at the front.
Connected all the way through.
Approved distribution journeys share the core comparison and insurer connections. A new placement can build on that foundation.
WHERE THE CUSTOMER STARTS
Yeti CompareOur consumer proposition
Your branded siteWhite-label or co-branded
Your content or appEmbedded widget or API
Collect the details · Request quotes · Present the results
Hosted on Microsoft Azure
Journey configurationInsurer connectionsAttribution & reporting
Insurer quote APIs
Each insurer calculates its quotes using its own products, pricing and eligibility rules.
Insurer purchase journey
The customer continues to the selected insurer to complete the purchase.
Follow one quote
What happens when
someone presses compare?
Four steps, with a clear job at each stage. Open a step to see what sits behind it.
01The customer tells us about their pet.
The journey collects the customer and pet details needed for the agreed products. The platform checks required fields before asking insurers for quotes.
Why it matters: A useful question asked once is better than making the customer repeat themselves.
02Yeti speaks to the insurers.
Each connection maps the details into the insurer’s expected format and handles authentication, responses and errors. The insurer’s quoting system determines its price and eligibility.
Why it matters: The comparison can work across different insurer systems without asking them all to operate identically.
03The results become easier to compare.
Returned quotes and approved product information are brought into a consistent results experience, including price, cover limits, excesses and other relevant differences.
Why it matters: Customers can understand more than the cheapest number on the page.
04The customer continues with the insurer.
The selected quote leads into the insurer’s purchase journey. Attribution connects the referral to its originating partner and placement, with subsequent policy outcomes dependent on insurer reporting.
Why it matters: Customer handover and commercial reconciliation are considered together.
Built around the connection you have
Your quote API.
Our integration work.
We start by understanding your existing quoting capability. Founding insurers don’t need to begin by rebuilding it around a new proprietary specification.
Explore the founding insurer panelThe working connection
Map the fields, configure the journey, validate responses and handle timeouts and errors.
A launch you can approve
Test the customer journey, confirm the handover and reporting, then agree readiness and operating contacts.
The Microsoft Azure architecture
Protection at the edge.
Resilience underneath.
Azure connects the public journey to the application, data and operating controls behind it. Separate environments keep development and testing apart from production.
Microsoft AzureSeparate production and development subscriptions
Customer traffic
Azure Front Door + Web Application Firewall
Route requests to the application and filter common web threats at the edge.
Private connections into the application environment
Primary region
Run the journey.
- Azure App Service
- Application hosting on managed App Service plans.
- Azure SQL Database
- The application’s relational data.
- Azure Storage
- Files and application storage.
- Azure Key Vault
- Secrets and credentials.
Virtual network · Private endpoints · Private DNS
Secondary region
Plan for disruption.
- Azure App Service
- Application capacity in the secondary region.
- Azure SQL failover groups
- Database replication and regional failover.
- Azure Storage RA-GZRS
- Storage redundancy across zones and regions, with secondary read access.
- Azure Key Vault
- Service resilience and private access to credentials.
Virtual network · Private endpoints · Private DNS
Connected by replication and recovery planning
SQL failover groups and geo-redundant storage support regional recovery. Replication timing, failover policies and recovery targets form part of the operating plan.
Management & access
A separate management subscription.
Microsoft Entra ID manages identity. VPN Gateway, virtual-network peering and network security groups support controlled access between the management and application environments.
Monitoring & security
Visibility across the service.
Azure Monitor and Application Insights support application monitoring. Microsoft Defender for Cloud and Microsoft Sentinel provide security monitoring and investigation capabilities.
More about the Azure services
Private endpoints provide private network access to supported services. SQL failover groups replicate databases between regions; storage uses its own redundancy and failover mechanisms. These controls work together, with configuration and operating procedures determining the final behaviour.
The Azure foundation
Built to be operated.
As well as launched.
The architecture approach brings security, visibility and recovery into the delivery plan. Detailed controls and evidence are reviewed for the proposed deployment.
Protect
Data & credentials
Encryption in transit and at rest, credentials managed through Azure Key Vault, and access scoped to the people and services that need it.
What that means for a partner
We review data flows, access responsibilities and credential handling with your technical and security teams. Logs should support investigation without unnecessarily exposing customer information.
Observe
Connections & journeys
Centralised monitoring helps identify failed requests, unexpected responses and problems in the quote journey.
What that means for a partner
A quote problem needs a traceable cause and a named owner. Monitoring, escalation and insurer support contacts form part of the operating plan.
Recover
Changes & service
Controlled deployments, rollback planning and managed backups support a considered response when a change or incident needs attention.
What that means for a partner
Recovery expectations, support hours and service levels are agreed for the deployment. The right commitments depend on the launch scope and the systems involved.
Clear responsibilities
The engine connects.
The insurer underwrites.
Sharing a platform does not blur the ownership of the product.
- Insurers control
- Products, pricing, underwriting, eligibility and policy issuance.
- Yeti connects
- The comparison journey, insurer interfaces, customer handover and agreed reporting.
- Publishers bring
- The audience, brand, placements and distribution proposition.
- We agree together
- Data responsibilities, approved journeys, commercial arrangements and launch requirements.
From conversation to controlled launch
A shared plan.
No mystery handover.
- Map itSystems, products, data and responsibilities.
- Connect itIntegration, configuration and test access.
- Prove itJourney testing, reporting checks and approvals.
- Operate itControlled traffic, monitoring and a review plan.
Bring your technical team.
We’ll make it concrete.
Start with your quote API, a proposed publisher journey or the questions in your procurement process.