Partner however it fits. The backbone is open.
Measurement providers and consulting firms build on SensorUp's backbone: your findings become owned work, or you compose solutions in Studio, under your brand.
The ecosystem
Bring what you do best. We'll bring the rest.
There is no fixed partner lane. Some feed the operator's work with detection and data, some build the workflows in Studio, and many do both, on their own terms. All of it stands on the same backbone SensorUp's own solutions run on, and the partner keeps their own brand on the front.
Your findings become owned work, not another report
Satellite, aerial, continuous, and OGI findings enter as typed observations.
Your detections land in the Warehouse as typed observations, reconcile against the operating context the customer already runs, and become owned work with documented closure inside their operation. The finding stops being a PDF in an inbox and starts being the first step: catch, prioritize, resolve.
You build the workflows, in Studio, under your brand
Compose solutions for your clients in Studio. Configure, not code.
Consulting and service firms compose solutions and workflows for their clients in Studio, on the same modules SensorUp builds with: configure, not code. You stand up and change a client deployment without a software team to maintain, and the work ships under your name.
Frameworks plug into the same record
Standards and certification bodies align the record to the framework.
Certification and standards partners align the operator record to the framework it reports against, so a number carries its provenance into OGMP 2.0, OOOOa/b/c, and the regimes that follow. The record an auditor accepts is the same record the certification reads.
In the ecosystem
Zeitview · GHGSat · Vanguard Pipeline · Momentick · Alliance Technical Group · Emerson · ERM · Orbio Earth · Manzer Environmental · Vertex Resource Group · Intero (The Sniffers) · MiQ
What you get
Reach, revenue, and your brand on the front
The program is built so partnering grows your business, not just your integration backlog. Powered By SensorUp puts your name on the offering and the backbone behind it.
You earn on the customers you bring and serve
A value-added reseller model, not a referral kickback.
Partner economics run on a value-added reseller model: you earn on the engagements you bring and the deployments you run, not a one-time referral fee. The platform is the backbone; the customer relationship stays yours.
Powered By SensorUp, with your name on the front
White-label the offering; the customer sees you, backed by the backbone.
The customer sees your offering, branded as yours, Powered By SensorUp underneath. You keep the relationship and the front of the product; the backbone, the record, and the work run behind it.
Stand it up without building a platform
Low-code composition in Studio: deploy and customize without a software team.
Solutions compose in Studio, low-code, so a partner deploys and customizes for a client without writing or maintaining a platform. A new client is a configuration on the same backbone, not a build that restarts every time.
SOC 2 Type II and ISO 27001, so the security review is already answered
Build on a platform that clears the vendor-risk review your customers run.
The backbone you build on is independently audited to SOC 2 Type II and ISO 27001. The security and vendor-risk review your enterprise customers run is answered by certifications you inherit, not a questionnaire you scramble through. And the same record stays aligned to the frameworks they file into, OGMP 2.0 and OOOOa/b/c, so framework fit comes with the security posture.
The same backbone
What we build with, you build with
Every SensorUp solution is built in Studio, on the same Warehouse and tools you get. There is no back door we keep for ourselves. Every customer runs the same workflow: catch, prioritize, resolve, on one record.
What we compose, you compose
Every SensorUp solution uses the same surfaces a partner gets.
EPA Subpart W, LDAR, Corporate GHG, and the rest are composed in Studio from the same modules and called through the same typed surfaces available to a partner build. If we could quietly reach past the API, the promise would be marketing. We cannot, so it is architecture.
Your sensor, their operation, one record
Findings reconcile against operational context and become owned work.
A detection company whose findings today land as reports: built on the backbone, those findings enter the Warehouse as typed observations, reconcile against the operating plan, and resolve to owned work with documented closure in the customer workflow. One data model, the same way of working.
Your customer's data stays in your customer's tenant
Tenant isolation in the database; full typed export.
The boundary is fact, not policy: tenant isolation is enforced in the database with row-level security, and the tenant loader gives each tenant a full typed export. Your customer operational data lives inside that customer boundary, theirs to keep and theirs to take.
Talk to partnerships
Bring your offering and the customers you serve. We will map how you plug in, whether you feed the operation, build in Studio, or both, walk the revenue and branding model, and show you where your customers' tenant boundaries sit against the backbone.