Skip to content
Connectors

Pre-built integration engines for the systems you already run.

Connectors ingest, normalize and distribute data across your stack — so insight lands where it’s needed, without bespoke integration work.

Part of Platform
Feeds the Ingest moveIMS · Guidewire · ModotechTwo-way sync
What it is

Integration that’s already built.

Connectors are pre-built engines for the platforms insurers actually run. They move structured data in and out — no custom pipeline, no months of integration work.

  • Pre-built for IMS/Vertafore, Guidewire, Modotech and more
  • Ingest, normalize and distribute in one pass
  • No bespoke integration build to maintain
How it works

Ingest, normalize, distribute.

  1. 01

    Ingest

    Pull data from policy admin, claims and CRM systems as it changes.

  2. 02

    Normalize

    Map every source onto one consistent, structured shape.

  3. 03

    Distribute

    Push the result back to the systems and people that need it.

Capabilities

What Connectors give you.

  • Pre-built engines

    IMS/Vertafore, Guidewire, Modotech, EpicAssure — ready to use.

  • Two-way sync

    Data flows in and back out, kept consistent across systems.

  • Normalized schema

    Every source resolves to one structured record.

  • No bespoke build

    Skip the months-long integration project.

Where it fits

Connectors feed the Ingest move.

They’re how submissions and system data reach the platform — and how results get back to your core systems.

Common questions

Connectors, answered.

What are Inaza Connectors?+

Pre-built integration engines that ingest, normalize and distribute data across your stack in one pass — IMS/Vertafore, Guidewire, Modotech and more.

Do we have to build an integration?+

No. The engines are pre-built and maintained by us, so there is no bespoke integration for your team to own or keep working after an upgrade.

Is the sync two-way?+

Yes. Data flows in and back out, so the record Inaza builds lands in the systems your teams already work in.

What if our system is not on the list?+

The normalized schema is the point of integration, not the vendor name. New sources map onto the same schema, and browser automation covers systems that never exposed an API.

What does "normalized schema" buy us?+

Every source lands in one shape, so a workflow written once runs against all of them. You are not maintaining a variant per system.

Expedited Start

Connect one system this week.

Tell us what you run. We’ll show the data flowing in and back out — live.