Built as infrastructure, not a product demo.

Yantrika is an open-source, MIT-licensed fleet-operations platform for autonomous mobile robots (AMRs) — the software layer that sits between robots on the floor and the humans responsible for them.

Robots increasingly speak a shared, vendor-neutral language: VDA 5050, an open protocol for AMR-to-fleet-management communication. Yantrika exists to give teams a real, working operations layer on top of that protocol — one they can run themselves, inspect, and modify — rather than depending on a single vendor's closed dashboard.

The platform is composed of independent, testable components that share one Postgres schema: a VDA 5050 connector, a deterministic warehouse simulator (so you can evaluate the whole system without a single physical robot), a single-file web console, an incident detector, a predictive-maintenance engine, a notification service, and an AI copilot ("Sarathi") that answers fleet questions grounded in the fleet's own live data. Every component ships with its own offline, no-network test suite — 10 suites, 500+ tests, all passing — because an operations platform that manages physical machines has to be trustworthy first.

Yantrika also treats access control as a first-class feature rather than an afterthought: it ships open for quick evaluation, with a documented, migration-driven path to a hardened, role-based-access-control posture for production use — because a platform that can send commands to real robots needs a real permission model when it matters.

The project is MIT licensed and developed in the open. The code, the architecture documentation, the security posture, and the test reports are all in the repository — nothing here is marketing-only.

Multi-vendor AMR fleets need an operations layer that speaks the open protocol they already use, that you can run on your own infrastructure, and that you can actually read the source code of. That's what Yantrika is.

Links

• View the source on GitHubThe full codebase — every component, every test suite.
• Read the architecture referencedocs/ARCHITECTURE.md — what was built and how.
• Read the security & RBAC modeldocs/SECURITY.md — demo, hardened, and role-based modes.
• LicenseMIT — see the LICENSE file in the repo root.