About
A software company that came out of a logistics business
VistarX Technologies Pvt. Ltd. builds the kind of software we needed ourselves — an engineering team working from India, for operators who cannot afford software that does not fit.
Why we exist
Vistar Logitek needed software. The options were to buy something built for a different kind of operation and bend the business around it, or to build. We built — and the systems worked well enough that turning the team into a company made sense.
That history is the whole pitch. We have sat on the operations side of the table, which is why we start every project by watching how the work is actually done rather than by asking for a requirements document.
- Daily
- production use in a live logistics operation
- 19
- operational modules live in Vistr CRM
- 2
- systems running in production
- 100%
- of the infrastructure managed by us
We run logistics ourselves
VistarX exists because Vistar Logitek needed software and building it in-house worked better than buying it. Every system we have shipped runs a real operation.
Already delivering outside our own group
VendFlow, a vending machine management ERP, was built for an external client. The same approach works wherever operations are complicated and the software has to match them.
You talk to the people building it
Everyone on the team builds. Your questions reach an engineer who knows the code, not an account manager relaying them onward.
We fit your process
We start from how your operation actually works. Software that forces a new process gets a parallel spreadsheet within a month.
You own what we build
Source code, documentation and infrastructure are yours. No lock-in to us, and no per-seat licence on your own system.
We run the infrastructure too
Our systems run on servers we manage, with automated backups, monitoring, alerting and tested restores. Building the software is half the job; keeping it up is the other half.
How we work
01
Understand the operation
We spend time with the people doing the work before proposing anything. Most bad logistics software comes from skipping this.
02
Scope and estimate
A written scope with a phased plan, so the first useful thing ships early rather than everything shipping late.
03
Build in the open
Short cycles with working software you can use, not status decks. Priorities change between cycles as you learn.
04
Hand over and support
Documentation, code and infrastructure transferred to you. We stay on for support if you want it, not because you are stuck.
Technology
This is what we actually run in production today, not a list of everything we could learn. We adapt to what a client already has rather than insisting on our defaults.
Backend
- Node.js
- NestJS
- Express
- TypeScript
- Fastify
- REST APIs
Mobile and web
- Flutter
- Dart
- Offline-first sync
- React
- Next.js
Data
- PostgreSQL
- PostGIS
- Prisma
- Sequelize
- Redis
- BullMQ
Infrastructure
- Docker
- Coolify
- Hetzner
- Cloudflare R2
- S3
- CI/CD