Skip to main content
OMNINET VISIONOmniNet Vision LLC — home
Platform

Connect the systems you already run

Each integration is per tenant, opt-in, set up by an operator at onboarding, and off until then. It lands with the phase whose data it carries. These are integrations, not partnerships or certified marketplace apps. The status on each row is marketing availability — planned until that phase is accepted.

Phase 1 sign-in is Microsoft Entra ID. Google Workspace and Okta sign-in are Phase 5: a later phase, optional, and not required. They stay planned, the same as every other integration here.

Collect, correlate, alert, review and verify — including the on-site appliance — is described on the managed assurance page. Integrations read and notify only. A notification is not an after-hours response; engineers respond during business hours.

Integration catalogue

Sign-in

Phase 1

  • Microsoft Entra ID

    Phase 1 sign-in through the client’s Entra ID directory — single-tenant with B2B guest onboarding, or multi-tenant.

    Planned

Phase 5 · later phase, optional

  • Google Workspace

    Phase 5 sign-in through the client’s Google Workspace directory. Later phase, optional, and not required.

    Planned
  • Okta

    Phase 5 sign-in through the client’s Okta directory. Later phase, optional, and not required.

    Planned

Tenant API and automation· Phase 2

  • Tenant API and webhooks

    Versioned per-tenant API and signed webhooks for the records the portal already shows.

    Planned
  • Automation recipes (n8n, Make, Zapier)

    Example recipes that call the tenant API or consume webhooks — documentation only, not a store listing.

    Planned

Notifications and paging· Phase 2

  • Email, Slack, Microsoft Teams, Google Chat

    Per-tenant notifications to the client’s own channels. Not a substitute for business-hours engineer response.

    Planned
  • PagerDuty and Jira Service Management

    Optional on-call paging into the client’s existing paging tools.

    Planned

Ticketing and MSP PSAs· Phase 2

  • ServiceNow

    Ticketing that mirrors OmniNet actions. Closing a ticket means awaiting verification — Postgres stays the system of record.

    Planned
  • Other ITSM tools

    Additional ITSM connectors after ServiceNow, same mirror-and-verify model.

    Planned
  • MSP PSAs (ConnectWise, Autotask, HaloPSA)

    PSA ticketing for managed-service operators, opt-in per tenant.

    Planned

Report delivery· Phase 2

  • Microsoft 365 report delivery

    Engineer-reviewed reports delivered into the client’s Microsoft 365 workspace.

    Planned
  • Google Workspace report delivery

    Engineer-reviewed reports delivered into the client’s Google Workspace.

    Planned

BI datasets· Phase 2

  • Power BI

    Versioned BI dataset for Power BI — sanitized records only.

    Planned
  • Tableau

    Versioned BI dataset for Tableau — sanitized records only.

    Planned
  • Looker Studio

    Versioned BI dataset for Looker Studio — sanitized records only.

    Planned

Network controllers· Phase 3

  • Cisco Meraki

    Read-only network controller API for inventory and change context.

    Planned
  • UniFi

    Read-only network controller API for inventory and change context.

    Planned
  • Aruba Central

    Read-only network controller API for inventory and change context.

    Planned
  • Juniper Mist

    Read-only network controller API for inventory and change context.

    Planned
  • Fortinet

    Read-only network controller API for inventory and change context.

    Planned

Device inventory· Phase 3

  • Microsoft Graph device inventory

    Read-only device inventory from Microsoft Graph where the tenant opts in.

    Planned
  • Google Workspace device inventory

    Read-only device inventory from Google Workspace Admin SDK where the tenant opts in.

    Planned

CMDB· Phase 4

  • ServiceNow CMDB

    Asset sync into the client’s ServiceNow CMDB — Postgres remains the authority for actions.

    Planned

SIEM feeds· Phase 4

  • SIEM feeds

    Sanitized security-tool feeds into the client’s SIEM — never raw telemetry bodies.

    Planned