Riptide Networking
github.com
- Free plan
- Windows
- macOS
- Linux
- iPhone and iPad
- Android
- Self-hosted
What Riptide Networking is
Riptide Networking is a free C# library for handling connections and data exchange in multiplayer games. It provides the networking layer for establishing connections and sending data, while developers decide what information to send and when. The library can be used with Unity or other .NET environments, including console applications. Its listed transports are UDP, TCP, and Steam. Documentation describes Reliable, Unreliable, and Notify message modes; reliable messages are resent until delivery is confirmed. Riptide uses a client-server model that supports dedicated servers, relay servers, and a client acting as host. True peer-to-peer use requires source changes. The default UDP transport works on PC, Mac, Linux, iOS, and Android, while VR and consoles have not been officially tested. Browser-based games are unsupported because the library has no web transport. Player capacity depends on data needs per player and available server hardware and bandwidth. Distributed under the MIT license, the project welcomes bug reports, feature requests, and pull requests, and links to a Discord server. Independently maintained Python and Dart/Flutter ports are also listed; they are not officially affiliated and may not interoperate across versions.
Who it suits
Riptide suits developers building multiplayer games in Unity or other .NET environments who want to choose how their game sends data. It is not suited to browser-based games, and peer-to-peer use requires source changes.
Good to know, and what to watch
- Free to use under the MIT license.
- Works in Unity and other .NET environments.
- Includes UDP, TCP, and Steam transports.
- Reliable messages are resent until confirmed.
- No web transport for browser-based games.
- True peer-to-peer use requires source changes.
- VR and consoles have not been officially tested.
Plans
Every plan and priceRiptide Networking
Free plan
The verdict
Riptide gives .NET game developers connection and message-delivery building blocks while leaving data choices to them. Check its transport and network-model limits against your target platforms and architecture.
What the maker publishes
- Architecture
- The FAQ says it supports dedicated servers, relay servers, and a client that also acts as the host; true peer-to-peer requires source changes. source
- Browser limitation
- The FAQ says there is no web transport, so Riptide does not work in browser-based games. source
- Capacity
- The FAQ says supported player count depends on per-player data needs and available server hardware and bandwidth. source
- Installation
- The project links installation instructions and says it can be used outside Unity in other .NET environments. source
- Message delivery
- Its documentation describes Reliable, Unreliable, and Notify message send modes; reliable messages are resent until delivery is confirmed. source
- Other-language ports
- The repository lists Python and Dart/Flutter implementations, noting that independently maintained ports are not officially affiliated and may not interoperate across versions. source
- Platform compatibility
- The FAQ says the default UDP transport works on PC, Mac, Linux, iOS, and Android; VR and consoles have not been officially tested. source
- Purpose
- Riptide is a lightweight C# networking library primarily designed for multiplayer games. source
- Security and compliance
- The opened maker pages state that Riptide is distributed under the MIT license and do not specify security certifications or compliance programs. source
- Support and community
- The repository welcomes bug reports, feature requests, and pull requests, and links to a Discord server. source
- Transports
- The project lists built-in UDP and TCP transports and a Steam transport. source
- Unity and .NET
- The library can be used in Unity and other .NET environments, including console applications. source
- What it does
- It provides functionality for establishing connections and sending data while leaving developers to choose what data to send and when. source
Checked against the maker's pages on 7 Oct 2026.