Salesforce to Acquire Rune for Military Logistics AI

When a disconnected military unit regains a network, headquarters has to catch up with the decisions made in the meantime. Rune Technologies builds logistics technology for that difficult interval, when a useful plan still needs people, equipment and supplies even though the connection has disappeared.

Salesforce signed a definitive agreement to acquire Rune, according to its October 29, 2026 announcement. The proposed acquisition would extend its Missionforce defense portfolio into frontline logistics. Financial terms were not disclosed, and closing is expected in Salesforce's fiscal Q4 2027, subject to customary conditions.

The combination would give an enterprise software supplier a wider assignment inside military operations. For the buyer using the technology, the attraction is continuity: local decisions need to remain useful when they reach the institution responsible for maintenance, personnel and the next movement of supplies.

What Salesforce would acquire in Rune Technologies

Rune's current leadership and company timeline identify David Tuttle as co-founder and CEO and Peter Goldsborough as co-founder and CTO. The company was founded in July 2024. Both founders previously worked at Anduril, bringing command-and-control experience into a business organized around sustainment. Rune's announcements use an Arlington, Virginia dateline.

Their product addresses a deceptively demanding question: what can a formation actually do with the resources it has? Inventory alone cannot settle that. Supplies need transport, transport needs available personnel, and an intended route has to fit the operation. Bringing those constraints together makes logistics information relevant to a commander's choices before an operation begins and as circumstances change.

Rune calls its platform TyrOS and describes it as a system for tracking supply, anticipating demand and coordinating distribution. Its October 7 announcement says the Army selected TyrOS for I Corps under the Next Generation Command and Control program as that effort moves into production. Rune says the selection followed prototypes with the 4th and 25th Infantry Divisions and also identifies its role in the Marine Corps' Project Dynamis.

That deployment history gives the planned acquisition a specific context. Salesforce would inherit work already shaped around military users, including the feedback and practical requirements that accompany field deployment. The transaction's value to those users will depend on how that work continues as it joins a larger supplier.

Why disconnected operation changes the software assignment

Rune's TyrOS product documentation describes software that caches critical inventory, route and vehicle information locally. It detects opportunities to communicate, prioritizes data and adjusts transmissions to bandwidth and mission requirements. Those are the company's descriptions of product behavior, rather than an independent assessment of performance in combat.

The design has consequences for how a buyer should evaluate the software. An application can remain available on a device while the information around it ages. A logistics user therefore needs to understand what the software knows, which updates it has received and what must be reconciled later. Disconnected operation creates a continuing information responsibility for the supplier.

Rune's broader product family reaches into collecting that information. The company describes TyrSense sensors and tags, TyrTac mobile tools and an Autonomy Development Kit for connecting vehicle systems to TyrOS. These components put the logistics platform closer to the places where a shipment changes hands or a field status gets recorded. The software assignment starts before a headquarters user opens a screen.

For Salesforce, the proposed addition expands the meaning of an enterprise workflow. A process can begin outside a reliable enterprise connection and still need to arrive inside an institutional record. Joining those environments requires the local tool and the receiving system to agree on something useful after conditions have changed.

The financing history behind the proposed acquisition

Rune's earlier backers financed a young company building for that operating constraint. Its timeline records a $6.2M seed round led by Andreessen Horowitz's American Dynamism fund in February 2025. A July 21, 2025 Series A announcement disclosed another $24M, led by Human Capital.

The Series A participants included Pax VC, Washington Harbour Partners, Andreessen Horowitz, Point72 Ventures, XYZ Venture Capital and Forward Deployed VC. Rune said the financing would support broader deployment across the military services. That capital history explains part of the company's development; the undisclosed acquisition consideration leaves the investors' sale economics outside the public record.

The proposed buyer arrives with a different operating history. Salesforce's corporate timeline begins in 1999 with cloud CRM and now describes a platform spanning enterprise applications, data and AI agents. Rune brings a specialized environment into that portfolio, with requirements defined by the people trying to sustain a military operation.

The commercial interpretation is that a specialist can become important to a platform well beyond its original product boundary. A supplier already serving enterprise workflows has a reason to care about where the underlying information originates. In this acquisition, the consequential information may first exist with a field user who cannot assume the network will cooperate.

The handoff that continues after a supply decision

Kendall Collins, President and CEO of Missionforce and Government Cloud at Salesforce, describes Rune's addition as an extension of Missionforce into frontline logistics. The announcement outlines a prospective connection between operational decisions and the enterprise processes supporting military readiness. It provides no separate timetable for completing that integration.

A military customer would have practical questions to bring to that work: how local updates appear in enterprise records, how teams understand an interrupted connection and how a user corrects information after a formation reconnects. These are implications of the proposed architecture, rather than newly announced product commitments. They are also a useful way to examine the deal beyond the familiar acquisition language.

An acquisition can put those responsibilities inside one supplier relationship, but military users will encounter them through ordinary actions: recording a quantity, assigning a vehicle and changing a route. For a commander reviewing an I Corps sustainment plan, the useful result would be a coherent account of what the formation can support as its information changes.