Talk to the person who built it
This form reaches Mert Satıcı directly, not a shared inbox. Answered within two business days. If a call is more useful than email, say so on the form and a time comes back in the same reply.
Sent
You will get a reply within two business days, from Mert rather than from an autoresponder. If you asked for a call, a couple of times will come back with it.
In the meantime, the two pages that answer most follow-up questions are how HYDRA OS actually works and how it compares to plant-level software — including where it is the weaker choice.
What a pilot costs you
The software is free during the Founding Pilot Cohort. A pilot is not free of effort, and pretending otherwise wastes everyone's quarter. This is the honest resource ask, so it can be approved against a real number rather than a guess.
- Engineering time
- Roughly 8–16 engineer-hours across weeks 1–2 for the telemetry connection and baseline capture, then 2–4 hours a month. One named contact, not a committee.
- Data access
- Read access to what your SCADA or historian already records — stack voltage and current, temperatures, water flow, gas pressures — over Modbus, OPC-UA, MQTT or REST. Cell voltage monitoring if you have it.
- IT involvement
- One sign-off for an on-premise deployment on standard industrial compute. No firewall exceptions for outbound traffic, because there is none.
- Plant impact
- None. No hardware change, no downtime, no control authority. HYDRA OS observes and reports during a pilot; it does not act on the stack.
- Cost
- Zero. No licence fee, no capital expenditure, no obligation at the end of 90 days.
- What you get back
- A written report with the Physics Engine validation logs, measured efficiency change against your week-1 baseline, and the observed accuracy and lead time of the failure predictions — including if the answer is unflattering to us.
The questions procurement asks
Is HYDRA OS ISO 27001 or SOC 2 certified?
No, and neither is claimed. The architecture is designed to make that question narrower rather than to answer it with a certificate: HYDRA OS is deployed on-premise, all sensor data and model inference stay inside the plant network, and no plant telemetry leaves the site. There is no multi-tenant cloud, no shared datastore and no third-party subprocessor touching operational data — so the security review surface is your own infrastructure, not a vendor's cloud. Full architecture documentation is provided for security review on request. If your process requires a certificate regardless of architecture, say so early and we will tell you honestly whether the timing works.
What happens to the software if Polestar Technology ceases trading?
Source code escrow is available on request as part of any commercial agreement. The company was incorporated in 2023; counterparty risk over a twenty-year asset life is a legitimate objection and there is no clever answer to it other than the standard one. Escrow is offered rather than waited for.
How quickly do you respond?
Within two business days, from the person who built the physics engine rather than from a shared inbox. If a call makes more sense than email, select "Book a call" and a time will be proposed in the same reply.
Can we run a technical evaluation before any commercial discussion?
Yes, and it is the preferred order. The five free tools use the same electrochemical and finance engine as the product and require no signup — running your own numbers through them is a legitimate first evaluation step. The platform page documents the models, and every published performance figure carries the basis it was derived from.
Company details
Polestar Technology — Diyarbakır, Türkiye. Incorporated 2023.
Email: info@polestartech.co
LinkedIn: Mert Satıcı · company page
Security contact: /.well-known/security.txt
Not affiliated with Polestar Technologies, Inc. of Needham, Massachusetts (optical sensing, founded 1993, polestartech.com), with Polestar Technologies GmbH, or with the Polestar automotive brand. This company is at polestartech.co.