Your carrier needs one route for partner data to reach Guidewire, and your team has to decide whether to build it or buy it. The usual comparison stops at the first release. The real difference is what your team still maintains on the day after go-live, and every day after that.
Both options leave work with your team. A build leaves the whole route, the mapping, the testing tools, and the release calendar with you. A purchase moves most of that to a provider but leaves the carrier’s own rules and decisions with you.
This article lists what a carrier-side intake gateway does, what your team maintains under each option, and a side-by-side ledger you can take into the decision meeting. It ends with the questions that settle the choice.
What Does a Carrier-Side Intake Gateway Do?
A carrier-side intake gateway is the single route that brokers, MGAs, TPAs, and vendors use to send data into your Guidewire instance. It sits across PolicyCenter, ClaimCenter, and BillingCenter, which is the cross-platform Guidewire view of intake.

It receives each partner’s payload
Each partner keeps its own data format and sends it to one endpoint. For submission intake, that means a broker or MGA sends its own payload instead of building a connector against your policy system’s API.
It validates against the carrier’s rules
The gateway checks each payload against the carrier’s definition of complete. First notice of loss adds rules of its own, and claims intake shows why: a claim cannot be created against a policy that was not in force on the loss date.
It delivers in the format Guidewire expects
The gateway translates the partner’s fields and values into the structure and codes the target module expects. A claim lands in ClaimCenter the way ClaimCenter requires, whatever format the TPA used.
What Does Your Team Maintain If You Build It?
A build gives the carrier full control of every layer. It also makes the carrier the owner of every layer, for every partner, for as long as the route runs.

The route and the infrastructure under it
Your team writes the endpoints, the calls into Guidewire, and the hosting they run on. The infrastructure a carrier needs to run an integration gateway in house stays on your team’s list for the life of the gateway.
Mapping and value translation for each partner
Every partner needs its fields mapped to Guidewire and its values translated into your codes. Your team owns payload mapping for Guidewire for every partner, and each new line of business adds more of it.
The onboarding and testing tools
Partners need sign-up, credentials, a sandbox, and test tools before any live data moves. In a build, your team writes and maintains each of those, alongside the mapping work.
Change handling and visibility
Guidewire releases and partner payload changes force retesting, and your team schedules and runs it. Your team also builds the logging that shows what was sent, what arrived, and what was rejected. The ongoing load is the same one described in what maintaining a Guidewire connector involves.
What Does Your Team Maintain If You Buy It?
Buying moves the route, the tools, and most of the change work to the provider. It does not move the carrier’s own rules, because only the carrier can write them.
What stays with the carrier
Your team still owns the payload specification and the definition of complete. Those are carrier decisions, and the guide to writing a payload specification a carrier will accept applies under either option.
What the provider maintains
The provider supplies the route, the self-service portal for senders, the test harness, and the sandbox. It also supplies AI-assisted mapping, rejection of incomplete payloads, and handling of payload and Guidewire release changes.
Where the gateway runs
Where the gateway runs is a separate decision from who builds it. Some carriers run an integration gateway inside their own environment, and that choice sets what the carrier’s infrastructure team maintains.
The Maintenance Ledger: Build and Buy Side by Side
We call this the Maintenance Ledger. It lists each layer of an intake gateway and who maintains it under each option.
Layer | If you build | If you buy |
|---|---|---|
Route and endpoints | Your team writes and runs them | The product supplies the route |
Payload specification | Your team writes it | Your team writes it |
Mandatory fields and valid values | Your team codes and updates the rules | Your team defines the rules, and the gateway rejects incomplete payloads |
Mapping and value translation | Your team maps each partner and re-maps each change | AI assists, and a person reviews every mapping |
Onboarding and testing | Your team builds the portal, credentials, sandbox, and test tools | A self-service portal, test harness, and sandbox come with the product |
Change handling | Your team retests after each release or payload change | The provider updates the mapping in one place |
Visibility | Your team builds the logs and dashboards | A dashboard shows what was sent, what arrived, and what was rejected |
Where build is the right answer
Build fits a carrier whose intake needs match no product’s route and whose team wants to own every layer. That carrier accepts the full ledger in the left column as its permanent workload.
Where buy is the right answer
Buy fits a carrier that wants its team writing rules and reviewing mappings, not maintaining routes and test tools. The carrier keeps the decisions and hands the upkeep to the provider.
Questions That Settle the Decision
Three questions decide most build or buy choices. Answer them with your own partner pipeline in front of you.
How many partners and lines of business are coming?
Count the partners and lines you plan to open. Every one adds mapping, testing, and change handling to the left column of the ledger.
Who owns the release calendar?
Name the team that retests every partner after each Guidewire release. If no team owns that work today, a build assigns it to one.
Who reviews the mappings?
Every mapping needs a person who approves it. Decide whether that person sits on your team or on the partner’s side, and whether your team writes the mappings or only reviews them.
How InsOps Helps
Yazh (Yaal) is the InsOps Integration Gateway, a data exchange layer for carriers on Guidewire. A sender maps its payload once, and Yazh translates it to each carrier’s Guidewire format. LiLa, our insurance-trained model, assists with the mapping, and a person reviews every mapping before it is used.
Yazh connects to Guidewire PolicyCenter, ClaimCenter, and BillingCenter. It includes a self-service portal for senders, a test harness, and a sandbox for testing before real data is sent. Mapping can carry carrier-specific fields without a fork of the integration.
Guidewire also has a product called Integration Gateway, which is a developer framework. Yazh sits beside it and supplies the sender-facing route, the mapping, and the testing. Payloads with gaps go back to the sender, and changes to a payload or a Guidewire release are handled in one place.
If you are weighing a build against a purchase without committing your team to maintaining every layer, contact us to talk through what this could look like for your operation.
Frequently Asked Questions
What is a carrier-side intake gateway?
It is the single route partners use to send policy, claims, and billing data into a carrier’s Guidewire instance. It receives each partner’s payload, checks it against the carrier’s rules, and delivers it in the format Guidewire expects.
What does a carrier’s team maintain if it builds one?
The team maintains the route and its hosting, the mapping and value translation for each partner, and the onboarding and testing tools. It also owns retesting after every Guidewire release or payload change, and the logs that show what arrived.
What does a carrier’s team still maintain if it buys one?
The team maintains the payload specification and the definition of complete, meaning the mandatory fields and valid values. It also reviews the mappings. The provider maintains the route, the portal, the test tools, and change handling.
Does buying a gateway remove the need for a payload specification?
No. Only the carrier can say what a complete submission looks like. The gateway applies that definition to each partner’s payload, so a clear specification is the first thing a carrier writes under either option.
Who reviews the mappings?
A person reviews and approves every mapping before it is used. The insurance-trained model suggests how each source field maps to Guidewire and flags the fields it did not match. It never approves a mapping on its own.
How is Yazh different from Guidewire’s own Integration Gateway?
Guidewire’s Integration Gateway is a developer framework. Yazh is a data exchange layer with a self-service portal, human-reviewed mapping, a test harness, and a sandbox for senders. Yazh sits beside Guidewire’s gateway and does not replace it.
What should a carrier ask before deciding between build and buy?
Ask how many partners and lines of business are coming, who owns retesting after each Guidewire release, and who reviews the mappings. The answers show how much of the ledger your team is ready to carry.

