IT signs off. Your people build.

SensorUp is the system IT signs off on and the surface your people build on: one foundation, three layers, one way of working across every business domain.

  • Studiobuild
  • Autopilotagentic
  • Warehousefoundation

A finite set of building blocks, the same ones in every solution

The composable units the layers are built from, not product lines or separate databases. Hover any one to see what it does.

[ 01 ]StudioBUILD
  • CalculationsContinuous calculation engines: emission rates, intensity, KPIs, derived as Observations land.
  • ScenariosModeling and forecasting: ESG projections, trajectories, forecast-vs-actual variance.
  • EventsLifecycle-tracked occurrences: emission events, pressure exceedances, incidents.
  • WorkProcess orchestration: issues, workflows, LDAR sequences, repair orders, escalations.
  • MetricsTracked targets: KPI definitions, methane-intensity targets, performance metrics.
  • ReportsAutomated reporting and document generation: OGMP 2.0, TCFD, and ESG outputs.
  • ComplianceObligations and tracking: regulatory programs, schedules, and status.
[ 02 ]AutopilotAGENTIC
  • AgentsManaged, supervised AI agents with an audit trail. Engaged and monitored, not unleashed.
  • CoraThe copilot: chat-driven composition and the agentic builder experience.
  • Solution BuilderCompose solutions with Cora, binding domains to resources.
  • WorkflowsRouting, escalation, and scheduled or event-driven automation.
[ 03 ]WarehouseFOUNDATION
  • AssetsInfrastructure hierarchy: facilities, wells, compressors, tanks, valves, sensors.
  • IntegrationsConnectors: SCADA (PI, CygNet), ERP (SAP, Maximo), satellite, continuous monitors.
  • DatasetsStructured collections: OGI definitions, CEMS configs, satellite schemas, tag registries.
  • RelationshipsEntity links across domains: Asset HAS Events, Work RESOLVES Event.
  • Reference LibraryReusable factors, rule sets, methodologies, and equipment taxonomies.
  • LedgersImmutable chain-of-custody: credit ledgers, compliance audit trails, verification records.
  • ApprovalsMulti-stage review and sign-off across the record.
The layers are the marketing view; in the app the same domains group as Data, Analyze, Operate, and Comply.

It fits what you already run, and all of it stays yours

No rip-and-replace, nothing new on your control network. It reads the systems you already operate, your own team runs it, and your data is yours to take with you.

[ 01 ]Works with what you run

It reads the systems you already operate

Historians (PI, CygNet), ERP (SAP, Maximo), continuous monitors, satellite, and OGI. Read-only, so nothing new is opened up on your control network.

[ 02 ]Run by your team

Your people change it, not a vendor

The next solution, a changed workflow, an adjusted calculation: your operations team builds it in Studio, from the same blocks every shipped solution uses.

[ 03 ]Owned by you

Your data leaves with you

The full operational record exports on demand, complete. Access runs through your own login. If the software stops earning its place, your data walks out with you.

Because your security review will ask

$schedule --with engineer --bring your-stack-diagram

Request a technical demo

Bring your stack diagram and your second problem. We'll name which domains bind it, against your actual asset hierarchy, and tell you what configuration can and cannot do before you scope the work.

SecurityTrust ↗