Run your meter network from one place, without touching your billing system.
Separate consoles for the distribution company's four units, one sign-in, signed and encrypted meter communication. Meters talk to a separate core server; subscriber and invoice data stays in your system.
Everything the platform sees begins inside the meter.
We design the meter as well. A platform written by people who know what happens in the field — from the measuring cell to the signature, from the valve to the event log — behaves differently from one that receives data from a stranger.
- 1 Ultrasonic measuring cell No moving parts, and no mechanism that drifts as it wears.
- 2 Segment display Index, valve state and warning icons, readable by eye on site.
- 3 Optical service port Local reading, calibration and commissioning — authenticated.
- 4 NB-IoT module Cellular connectivity; several module types, one address.
- 5 Secure element The private key is created here and stays here; it never reaches the MCU.
- 6 Tamper sensors Top cover, battery cover and magnet — each recorded separately.
- 7 Safety valve Remote close and open; it never opens on its own.
- 8 Dual battery A deep-sleep architecture; the battery cover is part of tamper too.
The periodic verification duty is yours; the platform keeps the calendar.
Gas meters carry a periodic verification cycle set by national metrology rules — ten years in Türkiye — and following it is the distribution company’s duty, not the consumer’s. A meter whose period has expired must be removed and replaced with one holding a valid verification. It is an obligation that repeats every year and requires physical work.
Basis in Türkiye: the Ministry of Industry and Technology regulation on the verification of electricity, water and gas meters, and the EPDK Natural Gas Market Distribution and Customer Services Regulation. The platform does not assume the obligation; it makes meeting it traceable.
Three layers, one set of data: from the meter to the console and into your system.
The meter connects to the core
REST or DLMS/COSEM over NB-IoT. Every packet is signed in the meter, and the core accepts nothing it has not verified. The only address a meter ever sees is the core server.
The core processes and stores
Readings, events and valve state are validated, bound to the usage point, and gaps are flagged. Commands are written to a queue from the console and the core passes them to the meter.
Consoles and the API consume
Four units work in their own consoles. Your billing and subscriber applications read through the API by usage point number; master data arrives by file or by API.
Four services, one chain: each unit sees only its own work.
General Operations routes, the unit manager gives it to a team, the chief assigns it to a person, the technician carries it out, and Operations closes it. Every step is in the audit log.
General Operations
- Every notification lands in one pool
- Routing to units and SLA tracking
- Silent-meter and alarm triage
Field Management
- Manager → team → technician
- Installation, removal, faults, inspection
- Result, photo and seal record
Depot Management
- Intake · Inspection · Calibration · Return · Scrap
- A removed meter does not move before examination
- Inspection calendar and evidence retention
Technical Operations
- Valve, clock and parameter commands
- Signed firmware campaigns
- Dual approval on critical actions
In three sentences, what sets this platform apart.
Built for gas
Measured and converted volume, volume correction, the safety valve, the verification period. Not a system written for electricity and adapted to gas — designed for gas from the start.
The field included
We do not read the data and stop there. The work order chain, the team grades, the five depots and the verification calendar are in the same platform; the meter’s physical life is managed here too.
Billing excluded
We do not issue invoices and we do not collect. We are not replacing your billing system, we are feeding it — which is why onboarding is a connection job, not a software migration.
The meter channel and the human channel sit on separate servers.
No person enters the core server and no meter reaches the console server. Every packet from a meter is verified against its signature. Every API call is recorded with who, when and how much.
Security questions- Accounts opened by invitation
No temporary passwords: staff set their own, from a single-use link or code valid for 72 hours.
- Two-step verification
With an authenticator app; company policy can make it mandatory for managers or for everyone.
- Single sign-on
One sign-in valid across every unit console, with idle and absolute limits set per company.
- Separation of duties
Routing, assignment, approval and execution are separate permissions; critical commands need a second approval.
- Audit and usage ledger
Every change and every API call is recorded — ready for tender and certification audits.
Connect without replacing what you already run.
Your subscriber and billing system stays exactly as it is. Three contracts are enough: master data in, period index out, order and result. A company that wants more reaches the same data through the REST API and webhooks.
- Master data in · overnight SFTP, row-by-row validation report
- Period index out · in your existing handheld-terminal file format
- Order and result · disconnection list, valve command under dual approval
GET /v1/usage-points/34-KAD-0001127
Authorization: Bearer …
{
"meter": { "serial": "…", "valve": { "state": "OPEN" },
"lastCommAt": "2026-09-03T07:15:02Z",
"battery": { "percent": 92 },
"index": { "value": 12845.3, "unit": "m3" } }
}The work order in the technician's pocket is the same record as the one in the console.
We are building the mobile app for field crews. It will open with the staff member's existing account; two-step verification, permission rules and the audit log will be exactly those of the consoles. A result entered in the field is not written somewhere else — it is written onto the same work order.
- The staff member's existing account and two-step verification
- Only the jobs that fall to their own team
- Accept, reject, and a result with up to three photos
- Every step written to the same audit log
The app is not in the stores yet; on release day the badges become clickable in the same place. Companies that would like to join the beta can write to us through their system administrator.
Your data and your meter communication are protected end to end.
These seals name the platform's own technical measures; they are not a third-party certification or an independent audit statement. How each one works is explained in the security questions.
From the first meter in the field to a hundred thousand, the same platform.
Pilot installation, master data migration and staff training included; no change is needed in your billing system.