Blicker
Blicker is an AI meter readout assistant that turns one photo of an analogue or digital water, gas or electricity meter into structured data, delivered to utilities and grid operators as a REST API and web portal.
What is Blicker?
Blicker is an AI-based meter readout assistant: a cloud SaaS service, hosted on Microsoft Azure and exposed as a REST API, that takes a photo of a utility meter and returns structured data in real time. It handles water, gas and electricity meters, analogue and digital alike, including smart meters that are not yet communicating, and it reads serial numbers, barcodes, QR codes and data matrices as well as the register itself, single-tariff or dual-tariff.
The company is explicit that this is not just another OCR: the core is a house-built stack of deep neural networks and computer vision. Blicker claims it brings the typical human reading error rate of five to ten percent down to 0.2 percent, and that a request is processed in roughly 400 milliseconds, on images as small as 100 kB. The models are presented as resistant to real conditions: dirt, poor light, awkward angles, condensation, meters recessed in cabinets. Every reading carries a high, medium or low confidence indicator, and a feedback loop asks the user for another photo when image quality is not sufficient.
Around the API sits the Blicker web portal, which holds the documentation, API key management, sorting and downloading of readings and photos, analytics, and branding in the customer's own colours and domain. The privacy statement also mentions Kite, a meter management portal for operators, as a component rather than as a separate product.
On the commercial side, the homepage claims 25 organisations, five countries, more than 15 million readings a month and over 3,000 field technicians, while the support page mentions more than 50 million readings processed to date. None of these figures is dated. Named customers are Brabant Water, Stedin and Morrison Water Services.
Blicker is developed by Clockworks, a computer vision and AI specialist, and is also distributed through the Microsoft Azure Marketplace under the publisher Clockworks Data Innovation B.V. Its accuracy was measured by NMi, the Dutch metrology institute, in a Technology Accuracy Evaluation rather than a certification. No price is published anywhere, and the site carries no general terms and conditions.
What it does
- Read a water, gas or electricity meter from a single smartphone or tablet photo
- Extract the reading, the serial number and the barcode from that same image
- Identify the meter type: water, gas or electricity, analogue or digital
- Validate readings in real time against the CRM, using GPS, serial number and expected consumption
- Return a confidence score on every reading and prompt the user to retake the photo when needed
- Browse, sort and download photos and extracted data in the web portal
- Upload existing pictures from a gallery to process a backlog of older images in batch
When to use Blicker / When not to
A quick filter to help you decide if Blicker is the right fit.
When to use Blicker
- Utilities and water, gas or electricity distributors still operating a large fleet of analogue meters
- Field teams: meter readers and technicians installing or replacing smart meters, recording readings on site
- Product teams embedding meter capture into a customer app, a chatbot or a billing portal
- Back-office teams validating metering data and resolving consumption or billing disputes
- Organisations whose volumes fit the published self-service tiers, up to 300,000 API requests a year
When not to use Blicker
- Consumers looking for a standalone app: Blicker is a B2B service that requires developer integration
- Teams working offline, since processing is cloud-based and the only workaround is caching the photo for a later upload
- Buyers expecting a ready-made mobile app to install, as the integrating organisation has to supply the interface itself
- Sites with unusual meter types, where accuracy should be checked during a trial before any commitment
- Buyers who need to budget from a published price list, since no amount is public and a sales or Azure Marketplace route is unavoidable
How to use Blicker
A typical end-to-end flow, from setup to results.
- Create an account on the Blicker portal, where the documentation, examples and API access management live
- Alternatively, subscribe from the Microsoft Azure Marketplace with Get It Now, then continue on the portal
- Move from a personal account to an organisational one, invite colleagues and assign their rights
- Create separate subscriptions for testing, development and production, and restrict access with an IP allowlist
- Set the rate limits you need, per second, minute, hour, day, month or year
- Add a photo button to your app or web interface and configure the API call that sends the image
- Let the user take a picture of the meter; the image is sent straight to the Blicker API
- Receive the structured result instantly, together with its confidence indicator
- Ask the user to check and approve the reading, or to retake the photo when confidence is low
- Push the approved data back into your own billing, CRM or workforce systems
Pros & Cons
Pros
- Accuracy measured by an independent third party: NMi reported 99.79% on high-confidence readings
- A confidence indicator on every reading, which makes quality control workable at industrial scale
- Light integration through a REST API, with no application for the end user to install
- Azure hosting in the Western Europe region, with the hosting region chosen by the customer
- Subprocessors published by name with their role, location and transfer basis, a DPA available, and a 12-month default retention for metering data
- Self-service purchase through the Azure Marketplace, billed on the existing monthly Azure invoice
- Quantified customer results, with Stedin reporting 85% fewer errors and 70% fewer site visits
Cons
- No public pricing: neither the plans page nor the Azure Marketplace listing shows an amount to a visitor who is not signed in
- No general terms and conditions: the General terms link in the footer points at '#'
- API documentation is not public, sitting inside the portal behind registration
- No documented opt-out from training, although the system is presented as self-learning
- Inconsistent legal identity: Blicker B.V. in the privacy statement, Clockworks Data Innovation B.V. on the Azure Marketplace
- Broken links across the site: /contact-us returns 404 while being linked from every page, /how-it-works returns 404, /demo returns 401
- An obsolete footer is still served on the homepage, dated 2020 with a privacy policy pointing at clockworks.co
Pricing & Plans
No price is published. Neither the plans page nor the Microsoft Azure Marketplace listing, consulted without signing in, shows an amount for Blicker, so no starting price, currency or billing unit can be stated. What is published is the structure: a ladder of tiers based on the monthly volume of API requests, one request corresponding to one meter photo. Starter covers up to 250 requests a month and Professional up to 1,000; Enterprise-5, Enterprise-25 and Enterprise-100 cover up to 5,000, 25,000 and 100,000 respectively; Pay-as-you-go is billed per request. Above those volumes, Enterprise Premium is a bespoke private offer arranged through sales@blicker.ai, and Partner Premium is reserved for distributors through partners@blicker.ai. Together the self-service tiers cover up to 300,000 API requests a year. There is no permanently free plan: the Professional plan comes with a first month free, which is a trial rather than a free tier, the registered card being charged afterwards. Requests beyond a tier's quota are billed under the pay-per-use component, and rate limits can be configured. A level 1 SLA is included in every plan except Pay-as-you-go, while level 2 is a paid option taken in the portal. Purchases made through the Marketplace fall under the Microsoft Customer Agreement and appear on the monthly Azure invoice, with a distribution restriction of at most three third-party entities and/or 100,000 API requests a month. Budgeting therefore requires a sales contact or an Azure account.
- up to 250 API requests per month
- price not published
- up to 1
- 000 API requests per month
- first month free
- price not published
- billed per request
- without the level 1 SLA
- up to 5
- 000 API requests per month
- price not published
- up to 25
- 000 API requests per month
- price not published
- up to 100
- 000 API requests per month
- price not published
- higher volumes
- bespoke private offer through sales@blicker.ai
- for distributors
- with additional partner benefits
- through partners@blicker.ai
Data, GDPR & hosting
A consolidated view of how Blicker handles your data.
GDPR overview
GDPR implementation is documented in concrete terms. The privacy statement is versioned April 2026, last updated 21 April 2026, and sets out the Article 15 to 21 rights plus withdrawal of consent in a table. Requests go to privacy@blicker.ai with an answer announced within four weeks; identity may be verified, but no ID document is systematically requested. The supervisory authority named is the Dutch Autoriteit Persoonsgegevens. Transfers outside the EEA, to Sentry and Cloudflare in the United States, are covered by standard contractual clauses. No Article 27 representative is appointed, the company being established in the EU. A named privacy contact is given, V. Westerwoudt, although he is never described as an Article 37 data protection officer. The benefits page claims the service is Fully GDPR compliant.
Who owns the data?
Blicker's privacy statement splits its role in two. For its own website visitors, contacts and account holders, Blicker is the data controller. For the metering data processed through the API, the business customer is the controller and Blicker acts as its processor, operating strictly on documented instructions under Article 28 GDPR. A separate data processing agreement governs that relationship. Control therefore stays with the utility, not with Blicker and not with the person photographing the meter: an individual customer of an energy supplier must address rights requests to that supplier rather than to Blicker. Blicker states that it does not sell personal data to third parties.
Reuse rights
Blicker publishes no general terms and conditions, so the privacy statement is the only public document framing data use. As a controller, Blicker processes account, billing, support, security and notification data, and lists improvement of Blicker's services, platform performance, and AI accuracy among its purposes, on the legal basis of legitimate interests under Art. 6(1)(f). The system is described as self-learning, constantly optimised as it learns from new, hard examples coming in, and no opt-out from training is documented anywhere on the site. Metering data handled as a processor may only be used for the purposes the business customer sets, as fixed in its data processing agreement. Blicker declares that its AI components fall outside Article 22 GDPR, no automated decision producing legal effects, and that human oversight is kept for billing and regulatory use. It also claims compliance with Regulation (EU) 2024/1689, the AI Act, through documentation supplied to customers, technical measures and notification of material changes.
Data retention & training
Hosting summary
Blicker states that its primary data processing takes place within the European Economic Area, on Microsoft Azure infrastructure in the Western Europe region. The customer selects its region in the Blicker portal, and API requests and images are then stored in that region. No individual hosting country is named: only the region, and the ability to choose a Microsoft data centre, are declared. Three subprocessors are disclosed by name: Microsoft for Azure hosting, Sentry (Functional Software, Inc.) for error monitoring, and Cloudflare (Turnstile) for bot protection, the latter two in the United States. Transfers outside the EEA are covered by the standard contractual clauses approved by the European Commission. Data is encrypted at rest and in transit, and backups are encrypted on separate Azure Blob servers. One point of attribution matters: the ISO/IEC 27001:2013 certification referred to in the privacy statement is Microsoft Azure's, covering the infrastructure, and is not a certification held by Blicker.
Where Blicker works
Country-level availability.
Not available in
Things to keep in mind
Risks and trade-offs to weigh before adopting Blicker.
- Legal identity is unsettled. The April 2026 privacy statement names Blicker B.V., but no entity of that name appears in the Dutch trade register. The registered entity at the same Rotterdam address is Clockworks Data Innovation B.V. (KVK 68148240, VAT NL857321353B01), where Blicker is a registered trade name. The Azure Marketplace publisher is Clockworks Data Innovation B.V. and the footer reads Developed by Clockworks. Establish which entity signs the contract.
- The ISO/IEC 27001:2013 certification mentioned in the privacy statement is Microsoft Azure's, covering the hosting infrastructure. It is not a certification held by Blicker, and no security certification of Blicker's own is disclosed on the site.
- NMi carried out a Technology Accuracy Evaluation of the reading accuracy. NMi is a notified body for MID and NAWI, but that does not make Blicker MID-certified: the exercise covers technology accuracy, not legal metrology conformity.
- There are no general terms and conditions. The General terms link in the footer is inert on every page, so the privacy statement is the only public document framing the relationship.
- The system is presented as self-learning and improving AI accuracy is a stated processing purpose, yet no opt-out from training is offered anywhere on the site, nor declared unavailable.
- Homepage marketing figures (25 organisations, five countries, more than 15 million readings a month, over 3,000 field technicians) are undated and cannot be cross-checked. An obsolete 2020 footer still served on the homepage shows that the site carries layers that were never updated.
- Site hygiene deserves attention before relying on public pages: /contact-us returns 404 although it is the get in touch link on every page, /how-it-works returns 404 and /demo returns 401. And with no price published, no budget can be assessed without a sales contact or an Azure account.
Setup & Integrations
Technical difficulty
Moderate, and developer work is required: this is not a no-code product. Blicker exposes a standard REST API and announces integration within hours to days, the benefits page claiming the API can be implemented in less than a day. You need an existing front-end or back-end able to send a photo, a portal account, API keys, per-environment subscriptions and, if wanted, an IP allowlist. Documentation and a Quick Start Guide sit in the portal after registration, not publicly. For teams without a suitable environment, Blicker offers a fully customisable web application as an alternative.
Deployment
Behind Blicker
Social
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
Which meters can Blicker read?
Do I need to install an app?
How accurate is Blicker, and who measured it?
How long does one reading take?
Where is the data hosted?
How long is the data kept?
Is there a free plan or a free trial?
Are the prices public?
What happens when there is no internet connection?
Does Blicker train on customer data?
Should you pick Blicker?
Blicker does one thing: it turns a photo of a utility meter into a structured reading, and it does it with an accuracy that an independent third party has measured. NMi's evaluation of 1,000 photos, 99.79% on high-confidence readings, is a rarer credential than most AI vendors can show, and the confidence indicator attached to every result is what makes that number usable in production rather than merely impressive. The maturity signals line up too: a company registered since 2017, a domain live since 2019, and named reference customers in Brabant Water, Stedin and Morrison Water Services.
The obstacles are commercial rather than technical. No price is published anywhere, on the plans page or on the Azure Marketplace listing, so no buyer can size a budget without talking to sales or opening an Azure account. There are no general terms and conditions at all, the footer link being inert, which leaves the privacy statement as the only public document framing the relationship. And the legal identity needs clearing up before any contract is signed, since the privacy statement names Blicker B.V. while the Dutch register and the Marketplace publisher both point to Clockworks Data Innovation B.V.
None of this is disqualifying, but it does shape who Blicker suits. This is a tool for a utility, network operator or metering service provider that already has a team able to integrate a REST API and the appetite to negotiate terms directly. Organisations wanting a packaged, priced, self-serve product with published conditions will find the evaluation path frustrating. Those with analogue fleets, field crews and a self-reading channel to improve will find a narrow tool that is unusually well evidenced for what it claims.
- Choosing a selection results in a full page refresh.
- Opens in a new window.