Live in weeks, in your cloud or ours.
Isomer deploys as a packaged product, not a project: an Azure Managed Application inside your own tenant, or a dedicated tenant in ours. Here’s what it takes.
In your tenant, or a dedicated one in ours.
Sovereign
In your Azure tenant
- An Azure Managed Application, installed from the Azure Marketplace.
- Single-tenant, inside your own Azure tenant.
- Bring your own keys and your own models, Azure AI or open-weight.
- No public internet exposure, if you want none.
Managed
A dedicated tenant in ours
- Single-tenant and managed by Isomer.
- No commingled data with any other customer.
- Private models available.
- The same product and controls as the sovereign install.
What you’ll need on your side.
Less than most claims technology. No claim-system project, schema work, or workflow design to begin, and a short briefing for handlers.
For every deployment
- Inbox access. A Microsoft 365 or Google Workspace admin grants scoped, read-only OAuth consent to the claims mailboxes, or sets up forwarding.
- Detectors and routing. A claims lead picks the detectors for your lines and states, and where signals go: the handler, a daily report, a webhook.
- Shadow mode. A few adjuster hours to grade a sample of flags before alerts go live.
- Working systems, for lifecycle detection. After first notice, work moves to adjuster inboxes and the claim system. Read-only access to them keeps each claim current on the claim graph. Single-message and cross-claim detection need only the claims inbox.
- Claim-system write-back, optional. For notes, tasks, and diary entries written to your claim system: API access, or where there’s no API, a dedicated service account that agents use to work through its screens on your network, with every session logged and replayable. Not needed to start.
For a sovereign install in your Azure tenant
- An Azure subscription in your tenant, and an admin who can deploy a Marketplace managed application into it.
- A region with capacity for the resources and the Azure AI Foundry models the install uses, or your own open-weight models.
- A network decision. Private ingress reachable only from your network, with hostnames under your internal domain, if you want no public exposure.
- Azure consumption for the install’s resources runs on your subscription.
Who’s involved on your side
- An IT or cloud admin, for the install and inbox consent
- A security reviewer
- A claims lead, for detectors and routing
- A few adjusters, during shadow mode
What Isomer provides
- The deployment template and its parameters
- A resource-level bill of materials: every resource, SKU, region, network dependency, identity, endpoint, and log destination
- Operation and updates. Isomer’s access is scoped to the managed resources; your team keeps read access for audit
- Security documentation for your review
Security and compliance are in the Trust Center.
SOC 2 Type II, HIPAA, ISO 27001 in progress, and no training on your data, with the documentation your security team will ask for.
Walk through a deployment.
Thirty minutes with our team on installing Isomer in your tenant: keys, models, network, and review.
