














































Confirm is an enterprise asset management system for linear and infrastructure assets such as highways, street lighting, drainage, and green spaces. It handles asset inventories, inspections, defect reporting, works ordering, and contractor payments for councils and public agencies.
Have any questions? We’re here to help You
Yes, Confirm is sold by Siemens Asset Management Software, the new name Brightly Software adopted on 15 July 2026, four years after Siemens acquired Brightly in 2022. The product itself is still called Confirm, and release notes from v22.10 through the current v26.1 carry Siemens branding with no change to functionality. Older documents, tenders and the makini.io page still say Brightly Confirm, so expect both names for some time.
Confirm is an enterprise asset management system for public infrastructure: highways and roads, bridges and structures, street lighting, drainage and gullies, parks, trees and waste assets. Its records run from asset Features and Inspections through Defects, customer Enquiries, Jobs and Works Orders to contractor Payment Batches, with modules such as ConfirmConnect Mobile, Confirm Scheduler, Confirm Stock Management and Street Manager integration for UK street works permits.
Yes, the Confirm Web API offers REST endpoints that create or update Features, Jobs, Defects, CentralEnquiries and Payment Batches, plus a GraphQL query API for reading feature data, authenticated with an OAuth API key and secret or a per user API key from the User Security screen. Siemens also lists CRM Connector, Contractor Interface, Financial Interface and Mapping Link (GIS) APIs. Whatever Makini returns depends on the access the council's Confirm administrator grants.
Makini normalizes Confirm records into its unified models, so Features become assets and locations, Jobs and Works Orders become work orders, and stock, vendors, customers, accounts and sites appear under those names, where the connection exposes them. A predictive maintenance or inspection product reads them through one REST API without learning the Confirm schema. Fields outside the unified model can be fetched as is through Makini's Custom Field Mappings add-on.
Confirm is offered as Confirm OnDemand, a SaaS deployment fully hosted on Amazon Web Services with a 99% availability SLA, so most councils connect to Makini without firewall work. A customer that still runs Confirm on its own servers would need IT to allow Makini's five fixed IP addresses or set up a VPN. In both cases the connection is created through Makini Link, so Confirm credentials never pass through the vendor's product.
Start with reading Confirm, because it drives statutory inspections, contractor payments and public enquiries, so a wrongly raised Job or Defect has audit consequences. Where the connection and the API user's Confirm permissions allow, a vendor product can raise a Defect or Job through Makini with the Feature, location and finding attached, while council engineers keep approval, contractor allocation and payment inside Confirm, whose user security settings define what that API user may touch.
