Automate the work between systems

Events that keep your stack in sync.

Every state change emits an event. Subscribe with webhooks, handle in your own systems, or wire up the platform's built-in workflows. The handful of jobs you should never have to touch run themselves.

How we work

Here to help

Insurance is not a product you can ship in a box. Off-the-shelf SaaS asks you to bend around their software. We don't work that way.

InsureOS is a bespoke service built on shared infrastructure. The platform is the same for every insurer. The setup never is.

01

Bespoke setup

We partner with each insurer one by one. We map your rates, build your forms, and wire your integrations, all the way through to production.

02

Yours to own

Everything we set up is editable from the admin portal. Change rates, tweak forms, adjust rules. No tickets, no waiting.

03

Support when you want it

Independent doesn't mean alone. We're a message away whenever you'd rather have a hand on the wheel.

Integrations that flow both ways

Between our API and our event system, we can enable any flow you need.

Example · a quote referral flow
InsureOS
Policy provider
1. Customer fills in the quote
2. Referral rule is triggered
referral.created
3. Underwriter reviews, adjusts, approves
POST /payment-links
200 · payment_link
4. Payment link sent to customer
5. Customer pays on our checkout
payment_link.paid
6. Policy issued to customer

Headless when you need it

Every state-changing action the platform exposes is also available via REST. Quote, rate, bind, refund, generate documents, fetch a policy schedule. Same engine the embedded widget uses, with idempotency keys on every call and per-organisation tokens scoped to environment and permission set.

  • REST API for rating, quoting, binding, and policy management
  • Idempotency keys on every state-changing call
  • Per-organisation tokens scoped to environment and permission set
See APIs

Events on every state change

Every meaningful change in the platform fires an event. Subscribe with webhooks and your downstream systems stay in sync without polling. Deliveries are asynchronous, HMAC-signed, and replayable from a timestamp if your receiver was down.

  • Asynchronous webhook delivery, HMAC-signed
  • Stable event taxonomy: quote.*, payment.*, policy.*, document.*
  • Replay-from-timestamp to catch up after downtime
Event stream
acme-auto · production
  • quote.created
    14:32:18 qx_7f3a92 124ms
  • quote.rated
    14:32:19 qx_7f3a92 98ms
  • payment.initiated
    14:32:24 pay_8b1c4 142ms
  • payment.succeeded
    14:32:48 pay_8b1c4 108ms
  • quote.paid
    14:32:48 qx_7f3a92 116ms
  • policy.bound
    14:32:49 pol_3d9f7 132ms
  • document.generated
    14:32:50 doc_2a4e1 94ms
  • webhook.dispatched
    14:32:51 whk_5g8h2 88ms

Frequently asked questions

Get in touch

We'd love to hear from you

hello@os.insure
Built by
The Caretakers

A small New Zealand product studio. We design, build, and operate software for insurers.

caretakers.io