Lavish Enterprises Unveils the Security Foundation Built to Take FleetPath From Platform to Road
With a Company-controlled Kenworth T680, technology being perfected for an initial three-truck beta and a full-system
Press Release Disclaimer: This is a press release distributed through the XPR Media network. It has not been independently verified by our newsroom.
With a Company-controlled Kenworth T680, technology being perfected for an initial three-truck beta and a full-system carrier simulation under development, Lavish is preparing to show carriers how FleetPath can connect the freight lifecycle while protecting the data, relationships and decisions that make each business valuable
LAS VEGAS, NV / ACCESS Newswire / September 24, 2026 / Lavish Enterprises, Inc. (OTC PINK:VXIT) (formerly known as VirExit Technologies, Inc.) (“Lavish” or the “Company”) today disclosed the security, privacy and accountability foundation built beneath FleetPath, marking the 11th installment in the Company’s 12-part technology disclosure series. Over the previous 10 releases, shareholders have been shown individual pieces of the platform: documents, routing, compliance, billing, fraud prevention, maintenance, exception handling and autonomous operations. Today’s disclosure addresses the foundation that allows those capabilities to become something much larger than a collection of features: a connected operating system that can move information across an entire freight operation without exposing the business behind it.
A trucking company does not simply move freight. It builds customers, negotiates rates, learns profitable lanes, develops operating knowledge, manages drivers and creates relationships that can take years to establish. For many carriers, that information is part of the value of the company itself. Brokers face the same reality with the carrier networks and shipper relationships they have spent years developing. FleetPath was designed around a simple principle: connecting those businesses through one platform should not require them to give up control of what they built. Each customer’s loads, rates, documents, customer records and driver information are designed to remain separated from other operators on the platform, allowing information to move through FleetPath without making one company’s business visible to another.
The significance goes beyond cybersecurity. FleetPath is being built to connect an industry that depends on information while preserving the commercial boundaries that allow the companies inside that industry to compete. A carrier should be able to use FleetPath without another carrier seeing its negotiated rates or customers. A broker should be able to provide shipment visibility without automatically exposing the carrier relationship behind the load. A driver should not have to surrender unrestricted location information simply because a shipment is being tracked. FleetPath is designed so the right information can reach the right people without turning the entire freight operation into an open book.
That same principle extends to accountability. FleetPath preserves a durable record of significant activity so an operator can look back and understand what happened, when it happened and how an outcome developed. Instead of reconstructing an important event from text messages, emails, GPS records, spreadsheets and several disconnected applications, the system is designed to keep the operating history together. That can provide a clearer record when reviewing a dispute, investigating an issue, documenting an event, understanding a delay or determining how a decision was made.
Automation adds another layer to that responsibility. FleetPath Ace is designed so the operator decides what the system is permitted to do, what requires human approval and where its authority ends. Important automated actions are designed to remain tied to the authority that allowed them. The concept is straightforward: if technology is going to act on behalf of a business, that business should remain in control. An operator should be able to determine what the system was allowed to do, what it actually did and whether the action remained within the limits that had been established.
FROM BUILDING FLEETPATH TO SHOWING FLEETPATH
FleetPath is now approaching a stage where the Company intends to make the complete system easier to see, test and understand under real operating conditions. Lavish recently acquired a Kenworth T680 that gives the Company control of a Class 8 truck for FleetPath deployment, testing and demonstration. The technology is being perfected for a planned initial three-truck controlled beta, where drivers, freight documents, routes and day-to-day operating activity can begin moving through the platform in real-world conditions. In parallel, the Company is building a simulation of the complete FleetPath experience so prospective carriers can understand how the system would work inside their operation before deciding whether to use it.
The simulation is being designed to show something a traditional software presentation cannot: an entire freight job moving through FleetPath from beginning to end. A carrier will be able to see a load enter the system, watch documents become usable information, follow the assignment of the load, see how information reaches the driver, understand how routing and compliance interact with the trip, watch the operating record develop as the load moves and follow the process through delivery, final documentation and billing. Rather than asking a carrier to imagine how dozens of capabilities connect, FleetPath intends to let the carrier see the complete workflow as one continuous operation.
That is an important step because the technologies disclosed throughout this series were never intended to stand alone. A document entering FleetPath can become information the rest of the system can use. That information can affect the load, the route and the driver. Activity during the trip can become part of the operating record. Documents collected along the way can support what happens after delivery. Information already captured during the job can support billing instead of requiring the back office to start over at the end. FleetPath Ace can assist along the way within the authority the operator chooses to give it. The larger value of FleetPath is not simply what each capability can do individually. It is what becomes possible when those capabilities understand and build upon what happened before them.
That is also why the security foundation disclosed today matters now. The more of an operation FleetPath connects, the more valuable the information moving through it becomes. Growth cannot require carriers and brokers to become more exposed simply because the system becomes more useful. FleetPath is designed so carriers, brokers, shippers, receivers and drivers can participate in a connected platform while maintaining control over the information that belongs to them. Location information can be shared in a controlled manner rather than automatically becoming an unrestricted live feed, and carrier identity can remain protected where appropriate. The goal is not connectivity at the expense of control. The goal is to deliver both.
For shareholders, the transition is becoming easier to see. The Company has spent months documenting the technology piece by piece. The focus is now beginning to move from explaining those pieces to demonstrating how they operate together. The Kenworth provides a Company-controlled vehicle. The initial beta is intended to place FleetPath into operating trucks. The simulation is being built to allow prospective carriers to experience the system before adoption. Each represents a different part of the same progression: taking FleetPath from something that can be described on paper and demonstrated feature by feature into something that can be seen, tested and understood as a complete operating environment.
The individual technologies are now a system. The system is moving toward trucks. And the Company is building a way for carriers to see the entire operation work before asking them to trust FleetPath with their business.
FROM THE FOUNDERS
Kevin Pachacki, Founder and Co-Chairman of Lavish Enterprises, Inc., said:
“You can build incredible routing, compliance, billing and automation technology, but none of it matters if an operator does not trust the platform with their business. Their customers are theirs. Their rates are theirs. Their documents, drivers and operating history are theirs. We designed FleetPath around that reality from the beginning. As more of the operation becomes connected, protecting those boundaries becomes even more important. We wanted that foundation in place before scale because trust is not something you can wait until later to build.”
Steffan Dalsgaard, Founder and Co-Chairman of Lavish Enterprises, Inc., said:
“For months, shareholders have watched us show FleetPath one piece at a time. What excites me now is that we are getting closer to the point where people will not have to imagine how those pieces fit together. We have the Kenworth. We are finalizing the technology for the initial three-truck beta. We are building the simulation so a carrier can sit down and actually watch an entire load move through FleetPath before deciding whether this belongs in their operation. That changes the conversation. We are moving from explaining FleetPath to showing FleetPath, and when people can finally see the complete system work from beginning to end, I believe they will understand why we spent so much time building the foundation correctly.”
The Sept. 24 release represents the 11th installment in Lavish Enterprises’ 12-part FleetPath technology disclosure series. Across the series, the Company has documented the individual systems that make up FleetPath and how those systems are designed to work together inside a larger operating platform. The security and data-isolation architecture disclosed today establishes the foundation beneath those capabilities as the Company approaches the next stage of FleetPath’s deployment.
One technology disclosure remains.
ABOUT FLEETPATH
FleetPath is a transportation technology platform designed to connect major parts of the freight lifecycle inside a single operating environment. The platform includes load management, route computation, dispatch, compliance, automated document processing, shipment tracking, billing and driver tools. FleetPath is designed to replace the fragmentation created by separate systems and disconnected applications with a more connected operating environment for freight transportation. FleetPath is operational in development and is being prepared for its initial controlled beta. FleetPath Technologies, Inc. is a wholly owned subsidiary of Lavish Enterprises, Inc. Additional information is available at fleetpath.co.
ABOUT LAVISH ENTERPRISES, INC.
Lavish Enterprises, Inc. (OTC PINK:VXIT) is a publicly traded diversified holding company building, acquiring and scaling businesses across three core verticals: infrastructure, entertainment and technology. FleetPath represents the Company’s technology initiative focused on the American freight transportation industry. Additional information is available at www.LavishEnterprises.net.
FORWARD-LOOKING STATEMENTS
This press release contains forward-looking statements within the meaning of Section 27A of the Securities Act of 1933, as amended, and Section 21E of the Securities Exchange Act of 1934, as amended. Forward-looking statements include statements regarding the design and intended operation of FleetPath’s security, privacy and accountability architecture, the planned carrier simulation, FleetPath’s initial controlled beta and subsequent commercial deployment, future development, market acceptance, scalability, commercialization plans and the Company’s business strategy.
Forward-looking statements involve known and unknown risks, uncertainties and other factors that may cause actual results, performance or achievements to differ materially from those expressed or implied. Descriptions of how a system is designed to operate are statements of design intent and are not guarantees of performance, and no security or privacy architecture can prevent all unauthorized access, misuse or data loss. Other factors include, among others, the timing, scope and success of the Company’s beta and any commercial deployment; the Company’s ability to capitalize and operate FleetPath Technologies, Inc.; market acceptance of the FleetPath platform; competitive responses; regulatory developments affecting the trucking industry; the Company’s ability to retain key personnel and obtain sufficient capital; the substantial doubt regarding the Company’s ability to continue as a going concern disclosed in its most recent Quarterly Report; the Company’s historical lack of revenue; the fact that the Company’s financial statements are unaudited; and general economic and capital-markets conditions.
The Company has no paying customers and has generated no revenue from FleetPath. Any beta engagement is provided at no charge and does not constitute traction, a customer, a contract or revenue. The Company is not representing that it is currently an SEC reporting company or that its Shell Risk designation has been removed or modified.
This press release does not constitute an offer to sell or a solicitation of an offer to buy any securities of the Company. Investors are cautioned not to place undue reliance on forward-looking statements, which speak only as of the date of this release. Except as required by applicable law, the Company undertakes no obligation to update or revise forward-looking statements as a result of new information, future events or otherwise. Investors should review the Company’s filings and disclosures available through OTC Markets Group.
Contact Information
Lavish Enterprises, Inc.
info@lavishenterprises.net
www.LavishEnterprises.net
SOURCE: VirExit Technologies Inc.
View the original press release on ACCESS Newswire
Media gallery
