Yahoo

Building real-time systems without servers

TL;DR:

  • Centralized backends add cost, latency, and single points of failure for real time systems, agents, and online games.

  • A DePIN mesh using leaderless DAG aBFT consensus turns coordination into a peer native service with median finality below 30 milliseconds in benchmark tests.

  • On-chain attribution and automated settlement convert bandwidth and coordination work into verifiable earnings for operators.

  • Teams can pilot in hybrid mode and measure cost per gigabyte, p95 latency, rebuffer rates, and downtime before scaling.

Every time a drone swarms in formation, an AI agent reacts in milliseconds, or a multiplayer game syncs thousands of players, machine‑to‑machine (M2M) communication is at work. It is the silent network fabric that lets devices communicate, interpret, and act together in real time.

The global market for M2M connections already exceeds $20B and is expected to reach $33.2B by 2032 . Yet most coordination still flows through centralized cloud APIs, which creates a structural bottleneck. Built on AWS, Azure, or Google Cloud, these APIs form the unseen backbone connecting clients, agents, and devices, and their limits are becoming clear.

High latency, sudden outages, and rising costs have become common, particularly for systems that need sub-second synchronisation or run across multiple regions. A single point of failure can ripple through the global digital backbone. In July 2024, a faulty CrowdStrike update disabled about 8.5M Windows machines, grounding flights and disrupting hospitals worldwide.

In October 2025, a misconfigured DNS update at AWS caused DynamoDB and S3 endpoints to become unreachable , which took parts of Slack, Epic Games, and Coinbase offline for hours. The incident highlighted the fragility of modern coordination when it depends on centralized naming and routing systems.

The challenge isn't that coordination is complex. It is that the digital ecosystem was built on the assumption that only centralized clouds can do it.

Tashi's Peer Mesh: A New Approach to Coordination Without Servers

Tashi offers a different backend model. It is a decentralised protocol that lets machines coordinate directly in real time across a peer-to-peer mesh network. Instead of polling a remote server to determine the state of a game, swarm, or simulation, devices reach consensus locally. Whether it is a fleet of delivery drones, players in a multiplayer arena, or AI agents executing at the edge, coordination occurs without a central authority.

Tashi's leaderless, gasless consensus engine combines a Directed Acyclic Graph (DAG) architecture with asynchronous Byzantine Fault Tolerance (aBFT) to achieve deterministic sub‑30 ms finality under typical network conditions. Because peers agree locally and only anchor signed snapshots to a monitor for validation and on‑chain attestations, the protocol eliminates server bottlenecks, regional failover logic, and most egress exposure.

In practice, that means lower tail latency, fewer single‑vendor dependencies, and predictable unit economics for continuous synchronization workloads. For developers, the MeshNet SDK drops into existing game, robotics, or IoT stacks, so teams can start in hybrid mode and progressively remove centralized coordination without rewriting their entire backend.

Achieving Median Finality Under 30 Milliseconds with DAG and aBFT

Tashi's consensus replaces ordered blocks and leader rotations with a DAG structure and virtual voting among peers. Multiple nodes propagate updates at the same time, which avoids sequential block proposals and the re-election stalls common in leader-based systems.

Once a two-thirds quorum acknowledges an update, it is final. There are no block intervals, no gas fees, and no centralized schedulers involved. For latency-sensitive domains such as drone swarms, robotic coordination, and live multiplayer systems, this design prioritizes speed and reliability rather than asset settlement semantics.

A monitor node validates state proofs and anchors snapshots on chain, which provides auditability for attribution and automated settlement without reintroducing a server as a runtime dependency. The result is a coordination layer that is composable, edge-local, and fault-tolerant by design.

Participants reach consensus, select a reporter, and submit a signed snapshot. The monitor node validates the state and anchors it on-chain, which removes the need for servers.

This design makes Tashi fundamentally different from consensus systems built for financial transactions. Tashi is not designed to settle assets. It is built to sync state quickly and reliably.

Tashi's DePIN Applications: Coordination Across Machines, Agents, and Robotics

Robotics and IoT Coordination

Cloud polling remains a weak fit for physical systems that require low-latency coordination or operate under limited connectivity. Whether it is autonomous vehicles, delivery drones, or warehouse robots, most still rely on centralized control loops that introduce latency and single points of failure. Tashi replaces that fragile relay model with local coordination.

Through its mesh network, robots can form local clusters, share state, and reach consensus on routing, formation, and collision avoidance, all without relying on a central system. In practice, this allows delivery drones to adjust mid-flight, warehouse bots to optimise pick paths, and agricultural fleets to respond to changing conditions in the field.

By reducing reliance on a central controller, Tashi keeps decisions closer to the edge. This reduces latency and bandwidth costs while preserving the deterministic behaviour required for real-time robotics. Each device can act as both participant and coordinator within a distributed intelligence network.

AI Agents and Edge Compute

Cloud APIs have become the default coordination layer for AI agents, but they add latency, centralize control, and introduce failure risks. As AI models shift from cloud inference to execution at the edge, coordination among multiple agents becomes critical.

Tashi provides a shared, lightweight state layer that lets agents act collaboratively without central brokers. Agents using Tashi's protocol exchange state updates within the mesh and agree on actions, task ownership, or sensor data streams in milliseconds. This shifts coordination from a central scheduling model into a peer native process. Because it can run on minimal hardware, Tashi supports multi-agent collaboration in environments where internet access is intermittent or costly, from edge devices in manufacturing to autonomous systems in remote areas.

The result is a coordination layer that scales across agents, devices, and local networks, and remains resilient even when upstream connections fail.

The same architectural principles that allow robots and agents to coordinate in real time also extend to digital environments. Multiplayer games and virtual environments share the same challenge, which is the need to synchronise thousands of state changes each second without relying on centralized relay servers.

DePIN Applications: Serverless Gaming and Multiplayer Worlds

Real-time multiplayer gaming has long relied on centralized relay servers to manage synchronisation and matchmaking. These backends handle everything from player positioning to session state, but they come with significant expense.

Studios spend heavily to maintain low-latency global infrastructure and often over-provision to ensure smooth gameplay during traffic spikes. Even then, cross-region lag and downtime remain persistent problems.

Tashi replaces this dependency with peer-native coordination. In a Tashi-powered game environment, clients act as peers within a mesh and agree on world state through DAG asynchronous consensus.

This approach removes the need for centralized relays, cuts egress exposure, and stabilizes tail latency across regions. In benchmarked deployments, games built on Tashi's SDK achieved 99.99% uptime and median finality under 30 milliseconds, which is enough to support large-scale multiplayer sessions without server fleets. For indie studios, this reduces operational overhead. For large studios, it expands the ability to scale player concurrency while keeping infrastructure costs predictable.

Tashi also preserves the attributes that studios value, which include deterministic consistency, verifiable state transitions, and auditability. Signed snapshots are anchored to a monitor node and validated on-chain, which supports fairness and integrity in competitive environments without reintroducing centralized control.

Beyond cost savings, the impact is architectural. By enabling peer-to-peer synchronization as a protocol primitive, Tashi turns coordination into a service layer. This creates space for new genres, persistent worlds, simulation titles, and collaborative creation environments that can run without cloud backends.

Why This Architecture Matters Now

Demand for real-time autonomous coordination is rising. AI agents, AI‑assisted robotics, and billions of IoT devices are moving decision-making to the edge. These systems need continuous communication rather than eventual consistency, and they cannot tolerate the latency, cost, and broad failure risk of centralized backends.

The economics and reliability of centralized coordination do not scale in a linear way. As concurrent agents expand in number, so does the cost of brokered messaging, cross-region replication, and especially data egress. In many hyperscaler invoices, egress is the hidden cost that dominates the runtime bill. At the same time, the systemic risk of a single provider outage rises as dependency becomes more concentrated.

Tashi's peer native approach distributes coordination, limits failure domains, and reduces egress by keeping most traffic local to the mesh and anchoring only succinct proofs to a chain for attribution and settlement. For agentic systems, robotics, and online worlds, this shift marks the difference between experimental pilots and viable production.

Today's infrastructure remains fragmented. Coordination sits behind proprietary APIs, cloud regions, and siloed networks. Each robotics fleet, game backend, or agent cluster often builds its own bespoke orchestration layer. This approach is costly, fragile, and difficult to scale.

Tashi serves as a shared coordination layer for the DePIN stack, in the same way that Akash supports compute, Filecoin supports storage, and Helium provides bandwidth. It fills a critical gap by offering decentralised coordination that is real-time, composable, and protocol agnostic.

Tokenized Coordination & Incentives

To build and sustain a broad, geographically distributed network, Tashi uses a simple token model. Node operators stake to join the network and earn most of the protocol's revenue for providing low-latency coordination. Because hardware requirements range from data centres to desktops and small embedded devices, the network encourages diversity of participation rather than a race toward high specification validators. For developers, this means capacity grows with demand, and incentives align directly with usage and uptime.

Risks, Challenges, and the Road Ahead

Tashi introduces a new coordination layer, although scaling it brings real-world complexity. Large mesh networks, particularly in volatile environments such as urban robotics or IoT, can strain latency targets and consensus stability. Although median finality below 30 milliseconds holds in current deployments, testing at more than 250K nodes will be critical.

Regulatory uncertainty also remains. Autonomous devices that earn and distribute revenue challenge existing frameworks for liability and financial compliance. Most real-world applications still depend on cloud APIs, so Tashi will need hybrid models and interoperability layers to bridge the gap. Developer onboarding remains a further challenge. Peer-first coordination requires a shift in approach, and adoption will depend on strong tooling, education, and SDK support.

With its upcoming TGE, CEX listing, and plans for GPU-accelerated consensus that aims for below 5 milliseconds, Tashi is positioning itself as essential infrastructure for the machine native internet.

The Coordination Layer Gap Across DePIN and Edge Systems

The shift toward decentralised physical infrastructure is expanding across multiple sectors. DePIN projects such as Helium for bandwidth, Filecoin for storage, and Akash for compute have established themselves as foundational layers.

However, coordination remains the least developed layer. Tashi complements the stack by providing a real-time state layer that other DePIN services can build upon. As enterprises spend billions on relay servers, orchestration, and multiplayer middleware, a cheaper and faster decentralised alternative that keeps data local and verifiable is well timed.

As DePIN expands into sub-verticals such as IoT networks, AI, serverless gaming, and cloud-connected devices, demand continues to grow. The market capitalization for DePIN projects was about $50B in 2024 and is expected to reach $3.5T by 2028 , driven by growing demand for assisted systems and serverless computing through locally controlled infrastructure. DePIN projects raised more than $250M across pre-seed, seed, and series A rounds during the past year.

Tashi complements the existing DePIN stack while opening new opportunities for real-time coordination. With industries spending billions on server infrastructure, backend orchestration, and multiplayer middleware, the appetite for cheaper and faster decentralised alternatives is growing.

The Team Behind Tashi

Tashi's founding group brings technical depth in distributed systems, long experience in institutional finance, and hands-on execution across Web3, enterprise platforms, and high-growth marketplaces.

Co-Founder and CEO Amar Bedi is an entrepreneur with more than 15 years of experience. He has led strategy and growth across startups and multinationals. At Grab, Uber, and KPMG, he managed enterprise partnerships and multi-million dollar revenue streams across Asia. He co-founded AVA, a global freelance marketplace, and BridgePort Group, which focuses on blockchain infrastructure and Web3 gaming. His background spans business development, operations, and technology venture scaling.

Co-Founder and CTO Ken Anderson is a technologist with two decades of experience in distributed systems and blockchain design. He created SQLx, an open source database tool adopted by more than 30,000 developers. He previously served as Lead Developer Advocate at Hedera Hashgraph and co-founded LaunchBadge, a firm focused on custom peer-to-peer systems. His work at QPQ Limited and Mingo focused on scalable infrastructure for decentralised applications.

Chief Business Officer Jay McCarthy brings 30 years of experience in capital markets, venture funding, and early-stage growth. He is a co-founder of SparkLabs, where he has backed more than 300 startups globally. Through Pacific Advisors, he has led financing and advisory work across fintech, deep technology, and emerging infrastructure sectors. He links institutional finance with frontier technology ecosystems.

Building the Future of Decentralised Coordination

Coordination has become a central bottleneck. Centralized backends are too slow, fragile, and costly for the machine native internet. Tashi provides a mesh-based layer with deterministic finality below sub-30 milliseconds, which removes server dependence from the core loop while preserving auditability and automated settlement. It does not compete with existing DePIN layers. Instead, it complements them by answering the practical questions of who moves, who acts, who syncs, and when and where those decisions occur, at the speed real-time systems require.

For further details, the architecture, SDK, and documentation are available here .

This story was originally published by TheStreet on Dec 16, 2025, where it first appeared in the Innovation section. Add TheStreet as a Preferred Source by clicking here.

Mobilize your Website
View Site in Mobile | Classic
Share by: