Custom builds · for system integrators and OEMs
We write the software layer. Never the control logic.
Moving data between PLCs, historians, MES and cloud. Protocol bridges. Operator tooling. The connectivity that sits beside the machine — built to order, when the gateway on this site is not the shape of your problem.
No ladder, no motion, no panel design, no machine commissioning. That boundary is deliberate: it is what lets a system integrator hand us the connectivity work and keep the machine, the customer and the control philosophy.
There are no case studies and no testimonials on this page. There is no client quote we can name yet, and an invented one is worse than none — so what we offer instead is further down, under what we can show you.
What we build
Six shapes, and each one is something the two products on this site already do. That is the bound we work inside: we take the jobs our own code proves we can write, not whatever an enquiry happens to ask for.
A driver for a controller nobody sells a connector for
A protocol the off-the-shelf stacks skipped, a vendor's own TCP framing, a serial device family with a PDF for a spec. This is most of what the gateway already is, written again for your device.
Protocol bridges between two systems that will not speak
One side talks OPC-UA and the other wants MQTT, or a file drop, or a REST body with a field order somebody's ERP insists on. The translation, the buffering when one end is down, and the mapping someone can read a year later.
Tag data landed where the business system can read it
PLC values into PostgreSQL, MySQL, SQL Server or a historian, on a schema your own reporting already understands — insert for history, upsert for a live mirror, and no DDL issued against a table that is not ours.
Operator tooling for one job, not a SCADA
A screen that does the one thing the line needs and nothing else: a changeover, a batch record, a station's setup. If you need alarm summaries and trends, keep the SCADA you have — this sits beside it.
The server side of a fleet
Provisioning, licensing, heartbeats, remote commands, an operator console. The control plane this page is served from does exactly that for gateways in the field, and it is the same shape of work.
Extensions to the gateway or to Verdict
A northbound share for a system we do not serve yet, or an inspection job Verdict's library does not cover. Often the cheapest answer on this page, because most of it already exists.
If what you actually need is the gateway with one more driver on it, we will say so — a licence at ₹22,000 a device plus a driver is cheaper than a project, and telling you that costs us a bigger invoice and buys a straight answer.
Where the line is
Stated at the same volume in both directions, because the half we refuse is the half that makes us safe to hire. An SI who hands us the data layer is not handing us the machine, the commissioning or the customer.
We write this
- Software that runs beside the machine, on a PC, an edge box or a Pi
- Drivers, protocol bridges and northbound integrations
- Databases, historian pipelines and the schemas under them
- Operator screens and internal tools for a single job
- Cloud and on-prem back ends: provisioning, licensing, fleet health
- The data model — naming, units, quality, an ISA-95 path that survives a migration
You keep this
- Ladder, structured text and anything else that runs inside the PLC
- Motion, servo and robot programs
- Panel design, EPLAN, wiring and the electrical drawings
- Machine commissioning, FAT and SAT on your line
- Safety: E-stops, light curtains, guard chains, functional safety ratings
- The machine itself, its cycle, and the customer relationship around it
The fit test is move data between systems, never make the machine move. Ask us for the second and you will get a polite no and, where we can, the name of somebody who does it properly.
What we can show you
Not a logo wall. The argument for hiring us is that the two products on this site are our own code — shipped, versioned, and published with their limits written down on the same pages that sell them.
Drivers, an OPC-UA server, a Sparkplug B bridge, SQL logging, REST, licensing and a fleet console. Installers for Windows and Ubuntu, each published with its SHA-256.
See the gatewayOn-prem vision inspection: three engines, a teach loop, a reject pulse on a wire, and every verdict mirrored into the tag store. On pilot benches today, not in a plant.
See VerdictThe console behind the sign-in button, the licence issuing, the download manifest and this page are one Next.js application against Postgres, deployed by us.
See the downloadsRead the parts of those pages that say what has not been proven — the drivers that have never met their vendor's hardware, the plant deployment Verdict does not have. Whatever we build for you will be described the same way, including on the day it is inconvenient.
How it runs
Four steps, and the interesting one is the second.
- 01
You write down the job
Two paragraphs beats a call: what sits at each end, what is in between, who owns the machine, and the date it has to work by. The form below or a plain mail both reach a person.
- 02
We say what we would not take
First reply, in writing, usually the same working day. If part of the job is control logic, panel work or commissioning, we name that part and hand it back rather than quietly quoting it.
- 03
A scope, in writing, before money
What is being built, what it talks to, what counts as done, and what it costs. A build is priced per engagement — there is no list price on this page and it would be a fiction if there were.
- 04
Handover, on terms agreed before the start
Ownership, licensing and what happens after handover are settled in that scope, before work starts, not discovered at the end.
PandaLogix is the product line of Tarini Engineering Works, Gurugram. Work is done remotely, on site in the Haryana region where a bench is needed, and against a written scope either way — the contact page has the registered details a purchase department will ask for.
Describe the job
The useful first message is not a requirements document. It is what sits at each end, what is in between, and the date it has to work by. From that we can usually tell you whether it is a job for us at all.
You will get one reply from a person, in writing, usually the same working day. If the honest answer is that a chunk of it is control logic, panel work or commissioning, that is what the reply says — we would rather lose the enquiry than take the part of it we should not be writing.
Already running the gateway? Say so. An extension to something that exists is a different and much smaller conversation than a build from nothing.