IOTA’s TWIN Trade Infrastructure Moves Under 3Sixty as Kenya Rollout Targets Q1 2027

IOTA’s Trade Worldwide Information Network (TWIN) appears to be entering a new operational phase, with its software development continuing under the British company 3Sixty Trade Ltd. Information shared by the Iota Feed account on October 20 points to a shift in how the trade infrastructure is developed, maintained, and commercialized, while its code remains open source and connected to the original IOTA repositories.

The reported change could be significant for IOTA’s ambitions in international trade, where digital infrastructure must serve ports, freight forwarders, customs authorities, and businesses across different jurisdictions. Rather than relying exclusively on a single ecosystem, the emerging model separates the underlying infrastructure from a commercial operator responsible for implementation and customer relationships. However, the precise agreements between the organizations involved have not been publicly established in the material provided.

3Sixty Takes Over TWIN Development and Commercial Operations

According to the information shared by Iota Feed, 3Sixty has published dozens of GitHub repositories and software packages since early October. The new repositories describe themselves as derived from the original iotaledger/twin-* codebase, providing a visible connection between the previous TWIN development work and the new software organization. The packages cover areas including telemetry, automation, hierarchies, and the broader framework.

The reported transition also extends to software distribution. Packages under the 3Sixty name began appearing in the npm registry on October 9, while several earlier TWIN packages reportedly became unavailable there from the same date. The IOTA integration packages continue to use IOTA’s software development toolkit, suggesting that the technical connection to the network remains relevant even as development moves under a different organizational name.

The commercial model described by 3Sixty centers on operating TWIN as a service. The company says it will integrate the infrastructure into the systems used by ports, freight forwarders, and public authorities, while generating revenue through shipment-based fees, company subscriptions, and service contracts with authorities. Under this arrangement, the underlying TWIN infrastructure is described as remaining open, with the TWIN Foundation responsible for maintaining it.

Company ownership is another important part of the story. The information cited by Iota Feed states that Jens Munch Lund-Nielsen holds 80% of 3Sixty’s voting shares, while the Tangle Ecosystem Association (TEA) holds the remaining 20%. Lund-Nielsen is associated with the IOTA Foundation’s global trade and supply-chain work, while TEA is linked to the wider IOTA ecosystem. The reported shareholding establishes a connection between the parties, but it does not, by itself, clarify all contractual, licensing, or revenue-sharing arrangements.

Kenya and UK Rollouts Could Test the Model in Practice

The timing matters because TWIN and related trade digitization efforts have been targeting practical deployments rather than remaining purely experimental projects. According to the information shared, 3Sixty took over a British pilot project and its partner relationships in October. The pilot is expected to continue within a closed group until the end of 2026, with additional companies potentially joining in the first quarter of 2027.

Kenya is also part of the reported rollout timeline through the Trade Logistics Information Pipeline (TLIP). Preparations for a nationwide rollout are reportedly targeting the first quarter of 2027. If that schedule holds, the coming months could offer a clearer indication of whether the operating model can support broader adoption by businesses and public institutions. The dates remain targets rather than confirmation that either rollout has been completed.

The shift raises questions about how an open infrastructure project can sustain commercial operations. A dedicated company could take responsibility for customer support, integrations, contracts, and ongoing product development, while an open-source foundation maintains the underlying technology. That division may make it easier for organizations to adopt TWIN without depending on a single closed software provider, although its success will depend on governance, licensing, service quality, and transparent commercial arrangements.

For IOTA, the continuing use of its developer toolkit is a relevant technical connection, but it should not be confused with proof that all revenue generated by 3Sixty will flow to IOTA or directly benefit IOTA token holders. The available information does not establish how commercial income will be distributed, what agreements govern the code, or precisely how responsibilities are divided between 3Sixty, the TWIN Foundation, the IOTA Foundation, and TEA.

The next major milestone is whether the planned UK and Kenyan deployments expand as expected in early 2027. Public clarification of the organizations’ agreements, the TWIN Foundation’s future role, and the relationship between commercial services and open-source governance would also help stakeholders understand the arrangement. For now, the reported transition suggests that TWIN is pursuing a more defined commercial operating structure while retaining technical links to the IOTA ecosystem, but the full implications remain to be confirmed.