Obserra

SaaS integration

Connect Obserra to customer systems

The SaaS model stays launch-based and protected, but each tenant can still connect approved local or enterprise applications, services, databases, webhook sinks, or API gateways through a governed integration profile.

Supported connection patterns

  • Local applications and services: connect on-premises or device-local tools through approved tenant endpoints or managed desktop bridges.
  • SaaS bridge: connect to a customer-owned HTTPS endpoint through approved host validation.
  • Managed desktop: subscribe once, install a governed launcher on a computer, and keep the core app SaaS-delivered.
  • Enterprise applications and services: route to SAP, ServiceNow, and other approved business systems through tenant-managed integration endpoints.
  • Enterprise databases: connect to governed database services through tenant-approved private or API-mediated access.
  • Webhooks: deliver events into a customer-controlled automation or ticketing platform.
  • Standalone fallback: keep the app usable even when external systems are offline.

App connector templates

Each app has its own set of connection targets. Expand a template, approve it, then use its specific connect buttons.

Integration profile

No customer system endpoint configured yet.

SaaS integration remains available without exposing raw backend access.

Connection status

No connection test has been run yet.

Status: Needs attention

No blocking issues found for the current connection profile.

Governance notes

  • Only approved local and HTTPS hosts should be connected.
  • The SaaS app remains non-downloadable and launch-based.
  • Managed desktop delivery is a companion access path, not the SaaS payload itself.
  • SAP, ServiceNow, local systems, and additional enterprise applications should be configured through approved tenant endpoints.
  • Enterprise database access should use tenant-approved private links, gateways, or governed service endpoints.
  • External systems can be connected without exposing raw backend control.
  • Standalone mode stays available if the external system is unavailable.