Integrations & compatibility

Understand what Intoto can connect to — and what still needs validation

Intoto can work with sensors, external data sources, APIs and customer systems, but compatibility depends on the actual interface and operating context. We distinguish verified support from configuration, validation and custom work.

Integrations & compatibility

Understand what Intoto can connect to — and what still needs validation

Intoto can work with sensors, external data sources, APIs and customer systems, but compatibility depends on the actual interface and operating context. We distinguish verified support from configuration, validation and custom work.

Sensor compatibility

Compatibility starts with the measurement need and interface

Intoto's Professional monitoring system is configurable and can combine multiple modules, components and sensors. Exact device compatibility should be confirmed for the specific deployment rather than assumed from a generic brand list.

Standard field sensors

Common monitoring inputs such as water level, weather and other environmental measurements can be part of an Intoto monitoring setup where the sensor and interface are already supported or can be configured within the established system.

Existing monitoring fleets

When a customer already operates sensors or telemetry, the goal is to fit the surrounding environment where practical. Exact interfaces, power, telemetry and enclosure requirements remain deployment-specific.

Specialized or unusual sensors

Advanced deployments may include specialized or unusual sensors, but these should be validated and scoped rather than presented as standard compatibility.

Sensor compatibility

Compatibility starts with the measurement need and interface

Intoto's Professional monitoring system is configurable and can combine multiple modules, components and sensors. Exact device compatibility should be confirmed for the specific deployment rather than assumed from a generic brand list.

Standard field sensors

Common monitoring inputs such as water level, weather and other environmental measurements can be part of an Intoto monitoring setup where the sensor and interface are already supported or can be configured within the established system.

Existing monitoring fleets

When a customer already operates sensors or telemetry, the goal is to fit the surrounding environment where practical. Exact interfaces, power, telemetry and enclosure requirements remain deployment-specific.

Specialized or unusual sensors

Advanced deployments may include specialized or unusual sensors, but these should be validated and scoped rather than presented as standard compatibility.

Sensor compatibility

Compatibility starts with the measurement need and interface

Intoto's Professional monitoring system is configurable and can combine multiple modules, components and sensors. Exact device compatibility should be confirmed for the specific deployment rather than assumed from a generic brand list.

Standard field sensors

Common monitoring inputs such as water level, weather and other environmental measurements can be part of an Intoto monitoring setup where the sensor and interface are already supported or can be configured within the established system.

Existing monitoring fleets

When a customer already operates sensors or telemetry, the goal is to fit the surrounding environment where practical. Exact interfaces, power, telemetry and enclosure requirements remain deployment-specific.

Specialized or unusual sensors

Advanced deployments may include specialized or unusual sensors, but these should be validated and scoped rather than presented as standard compatibility.

Integration types

Data can move into Intoto, out to customer systems, or both

The right integration pattern depends on where the data originates, who owns the surrounding system and what the operational workflow requires.

Sensors and field devices into Intoto

Measurements can enter the Intoto platform through supported field-device and ingestion paths where the device, interface and data format are established.

External data sources into Intoto

Customer or third-party data can be brought into the Intoto context when the source, access method and mapping are defined.

Intoto data into customer systems

Customers may need Intoto monitoring data delivered into an existing operational system or application. API-based exchange is one supported pattern where the implementation is clearly defined.

Two-way integration context

Some customer needs involve data moving in both directions. The exact interfaces, ownership and implementation scope must be defined for each case.

Integration types

Data can move into Intoto, out to customer systems, or both

The right integration pattern depends on where the data originates, who owns the surrounding system and what the operational workflow requires.

Sensors and field devices into Intoto

Measurements can enter the Intoto platform through supported field-device and ingestion paths where the device, interface and data format are established.

External data sources into Intoto

Customer or third-party data can be brought into the Intoto context when the source, access method and mapping are defined.

Intoto data into customer systems

Customers may need Intoto monitoring data delivered into an existing operational system or application. API-based exchange is one supported pattern where the implementation is clearly defined.

Two-way integration context

Some customer needs involve data moving in both directions. The exact interfaces, ownership and implementation scope must be defined for each case.

Integration types

Data can move into Intoto, out to customer systems, or both

The right integration pattern depends on where the data originates, who owns the surrounding system and what the operational workflow requires.

Sensors and field devices into Intoto

Measurements can enter the Intoto platform through supported field-device and ingestion paths where the device, interface and data format are established.

External data sources into Intoto

Customer or third-party data can be brought into the Intoto context when the source, access method and mapping are defined.

Intoto data into customer systems

Customers may need Intoto monitoring data delivered into an existing operational system or application. API-based exchange is one supported pattern where the implementation is clearly defined.

Two-way integration context

Some customer needs involve data moving in both directions. The exact interfaces, ownership and implementation scope must be defined for each case.

Support state

Four states keep compatibility claims clear

Use these four states to distinguish established capabilities from connections that still need configuration, validation or custom work.

Supported now

The capability or integration pattern is already established and can be used within its known technical boundaries.

Supported with configuration

The underlying capability is established, but the customer-specific setup still needs mapping, credentials, configuration or other normal implementation work.

Requires validation

The connection appears plausible but the actual sensor, protocol, API, data format, security requirements or operating context must be checked before commitment.

Custom / non-standard

The requirement needs material engineering, specialized hardware, unusual sensors, R&D or a bespoke integration and should be separately scoped.

Support state

Four states keep compatibility claims clear

Use these four states to distinguish established capabilities from connections that still need configuration, validation or custom work.

Supported now

The capability or integration pattern is already established and can be used within its known technical boundaries.

Supported with configuration

The underlying capability is established, but the customer-specific setup still needs mapping, credentials, configuration or other normal implementation work.

Requires validation

The connection appears plausible but the actual sensor, protocol, API, data format, security requirements or operating context must be checked before commitment.

Custom / non-standard

The requirement needs material engineering, specialized hardware, unusual sensors, R&D or a bespoke integration and should be separately scoped.

Support state

Four states keep compatibility claims clear

Use these four states to distinguish established capabilities from connections that still need configuration, validation or custom work.

Supported now

The capability or integration pattern is already established and can be used within its known technical boundaries.

Supported with configuration

The underlying capability is established, but the customer-specific setup still needs mapping, credentials, configuration or other normal implementation work.

Requires validation

The connection appears plausible but the actual sensor, protocol, API, data format, security requirements or operating context must be checked before commitment.

Custom / non-standard

The requirement needs material engineering, specialized hardware, unusual sensors, R&D or a bespoke integration and should be separately scoped.

What we validate

Compatibility is more than whether two systems can technically exchange data

Before committing to an integration, Intoto needs enough information to understand the interface, ownership and operational consequences.

Interface and data format

Confirm how the sensor or external system exposes data, what format is available and whether the required read or write direction is supported.

Access and ownership

Confirm who controls credentials, APIs, networks, source systems and changes to the integration.

Security and governance

Authentication, client IT requirements, cybersecurity, authority approvals and data-governance constraints can materially affect the solution.

Operational responsibility

Define who operates, monitors and supports each side of the integration so the connection does not create unclear service responsibility.

What we validate

Compatibility is more than whether two systems can technically exchange data

Before committing to an integration, Intoto needs enough information to understand the interface, ownership and operational consequences.

Interface and data format

Confirm how the sensor or external system exposes data, what format is available and whether the required read or write direction is supported.

Access and ownership

Confirm who controls credentials, APIs, networks, source systems and changes to the integration.

Security and governance

Authentication, client IT requirements, cybersecurity, authority approvals and data-governance constraints can materially affect the solution.

Operational responsibility

Define who operates, monitors and supports each side of the integration so the connection does not create unclear service responsibility.

What we validate

Compatibility is more than whether two systems can technically exchange data

Before committing to an integration, Intoto needs enough information to understand the interface, ownership and operational consequences.

Interface and data format

Confirm how the sensor or external system exposes data, what format is available and whether the required read or write direction is supported.

Access and ownership

Confirm who controls credentials, APIs, networks, source systems and changes to the integration.

Security and governance

Authentication, client IT requirements, cybersecurity, authority approvals and data-governance constraints can materially affect the solution.

Operational responsibility

Define who operates, monitors and supports each side of the integration so the connection does not create unclear service responsibility.

When it becomes custom

Non-standard integration belongs in an explicit engineering scope

Intoto should not promise a new integration simply because it seems technically possible. Material uncertainty or engineering effort moves the work into validation or a custom scope.

New or unverified interface

A protocol, API, device or data source without verified implementation history requires technical validation before it can be treated as supported.

Specialized hardware or safety-critical context

Unusual sensors, site-specific engineering or safety-critical requirements may belong in an Advanced custom scope.

Significant custom development

If the requirement needs material software or integration engineering beyond normal configuration, it should be estimated and agreed separately.

When it becomes custom

Non-standard integration belongs in an explicit engineering scope

Intoto should not promise a new integration simply because it seems technically possible. Material uncertainty or engineering effort moves the work into validation or a custom scope.

New or unverified interface

A protocol, API, device or data source without verified implementation history requires technical validation before it can be treated as supported.

Specialized hardware or safety-critical context

Unusual sensors, site-specific engineering or safety-critical requirements may belong in an Advanced custom scope.

Significant custom development

If the requirement needs material software or integration engineering beyond normal configuration, it should be estimated and agreed separately.

When it becomes custom

Non-standard integration belongs in an explicit engineering scope

Intoto should not promise a new integration simply because it seems technically possible. Material uncertainty or engineering effort moves the work into validation or a custom scope.

New or unverified interface

A protocol, API, device or data source without verified implementation history requires technical validation before it can be treated as supported.

Specialized hardware or safety-critical context

Unusual sensors, site-specific engineering or safety-critical requirements may belong in an Advanced custom scope.

Significant custom development

If the requirement needs material software or integration engineering beyond normal configuration, it should be estimated and agreed separately.

Check compatibility

Have a sensor, system or data source you need to connect?

Send us the device or system, the data you need to move, the direction of the integration and any known interface details. We can then tell you whether it is supported, configurable, needs validation or belongs in a custom scope.

Check compatibility

Have a sensor, system or data source you need to connect?

Send us the device or system, the data you need to move, the direction of the integration and any known interface details. We can then tell you whether it is supported, configurable, needs validation or belongs in a custom scope.

Vil du se nettsiden på norsk?

Du kan bytte språk i menyen når som helst.