About Us
This technology is a brainchild of Vlad Grigorian. Vlad has more than 30 years of IT experience, specializing in Oracle databases, replication and hyper automation.
He has worked for many US blue-chip companies and enterprise software makers, including Oracle's elite consulting division ATS (Advanced Technology Services) for many years.
His most recent position was with JP Morgan Chase as a VP / Lead of Infrastructure Engineering.
Vlad had the honor of serving on the president Clinton's CDC Federal Immunization Registry initiative as an expert witness. His prior inventions include the AI vector database engine patent, allowing for semantic searches based on the meaning of data, rather than just RDBMS keywords. Vlad submitted the patent application more than 20 years ago, when the terms "vector", "database" and "AI" weren't even used in the same thought or sentence, much less so in the same product. Now this technology powers most of AI engines, not just Oracle's. Vlad's application was abandoned due to lack of financial support, otherwise he would have been a multi-billionaire by now.
But then Replayable wouldn't have been born.
Why Replayable Exists
Vlad watched this happen once already. He filed the patent behind vector databases more than 15 years before "vector," "database," and "AI" ever shared a sentence — and watched the idea reach the industry without him, once the market finally caught up. That's not a grudge. It's a lesson: valuable technical insight is only worth something if someone commits to building it into the future before the future arrives on its own.
Replayable is that lesson applied deliberately. System, database, and network administration are following the same path as electricity, and before that, the lamplighter and the telegraph operator: work that was once physical and manual becomes codified once the underlying infrastructure does. Servers, routers, and databases are now JSON, not hardware — which means the expertise that once required a full-time team can be encoded, automated, and delivered on demand. What remains isn't the labor. It's the judgment: ITIL-aligned, risk-mitigated, cost-contained best practice, applied consistently regardless of vendor or platform.