Sentinel is not limited to standalone VPN apps. Developers can integrate decentralized connectivity directly into applications, services, agents, and other internet products while keeping control of the product, pricing, user experience, and distribution. The stack is already there: • Plan Manager for creating and managing subscription-based VPN services • x402 for programmable access and machine payments • Open-source components and developer tooling • Node deployment and management infrastructure • Independent dVPN apps already using the network across multiple platforms The opportunity is to use Sentinel as a connectivity layer, not just as a consumer VPN network. Build with Sentinel: docs.sentinel.co/ Plan Manager: plan.sentinel.co/dashboard x402: x402.sentinel.co/ Open-source ecosystem: github.com/sentinel-official Node Deployer: github.com/sentinel-official… Explore applications: docs.sentinel.co/get-started…

DVPN by NORSE Labs brings Sentinel-powered decentralized VPN access across mobile, desktop, Linux, and TV platforms. Built by the @norselabs team and @alexlitreev, DVPN connects users to independently operated infrastructure across the Sentinel Network, with 2,000+ endpoints spanning 100+ countries. The app supports WireGuard and V2Ray, alongside split tunneling, DNS selection, and obfuscation for users connecting across different network conditions. A free basic tier is available without requiring a credit card or traditional sign-up, while DVPN Plus provides access to the wider network. DVPN has already passed 50,000 downloads on Google Play, but the NORSE contribution goes beyond the main app. The team has also built a browser-based DVPN Proxy, Telegram DVPN Bot, QuickClient, and an SDK that allows other developers to integrate Sentinel-powered connectivity into their own products. That gives NORSE a broader role in the ecosystem: consumer applications, alternative access points, and developer tooling all built around the same decentralized bandwidth network. Explore DVPN by NORSE Labs: norselabs.io/ Explore more applications built on Sentinel: docs.sentinel.co/get-started…

Payments just turned multi-chain ⛓️ For $SOL & USDC, you can pay from any external wallet or connect directly with a Solana wallet such as @Solflare, or a @solanamobile. Native P2P payments remain available through the built-in wallet. All plans are now USD-denominated 💵

In this week's edition of Sentinel's Sunday Morality, we ask: Should governments ever be able to access encrypted data? It could help investigate serious crimes and protect national security, or just be used as excuse for control. Where do you draw the line?

Take a look at Sentinel. We have been saying this from the beginning. With a traditional VPN, you are still trusting one company with the app, infrastructure, policies, and server network. Sentinel separates those layers. Applications are built independently, nodes are operated independently, and the core software is open source. Good OPSEC still matters, but users are not relying on one provider to control the whole stack. Happy to show you how it works: GitHub: github.com/sentinel-official⁠ Docs: docs.sentinel.co/⁠ dVPN apps: docs.sentinel.co/get-started…⁠ Node setup: docs.sentinel.co/dvpn-nodes/…⁠

Building a VPN business does not have to start with renting servers in dozens of countries. Sentinel gives teams access to decentralized bandwidth supplied by independent node operators, allowing them to focus on product, brand, pricing, distribution, and customer experience. Plan Manager turns that infrastructure into something a business can package and sell. Teams can create subscription plans, choose which Sentinel nodes are included, set pricing, manage user access, and control how customers connect to the network. The application, brand, pricing model, and customer relationship remain with the team. Sentinel provides the shared bandwidth infrastructure underneath. Teams can also build with open-source applications, SDKs, node deployment tools, testing utilities, and support for multiple VPN protocols, giving them flexibility across different platforms and markets. The commercial opportunity is straightforward: launch a VPN service on infrastructure that already has active nodes, real users, and applications operating across the network. Create and manage VPN plans: plan.sentinel.co/dashboard Build with Sentinel: docs.sentinel.co/ Explore dVPN applications already using the network: docs.sentinel.co/get-started… Node deployment: github.com/sentinel-official…

Meile dVPN is one of the longest-running applications built on the Sentinel Network, giving desktop users direct access to decentralized bandwidth through Windows, macOS, and Linux. Built by @MathNodes , @MeileDVPN supports monthly plans through Bitcoin Lightning alongside off-chain payments with XMR, PIVX, FIRO, and ARRR. Users can access the service without a traditional signup or KYC process. The latest v2.7.1 release adds improved UI dialogs, signed Windows builds, better payment precision, scannable payment QR codes, and a fix for WireGuard connections on Linux following the v2.7.0 release. Meile shows how an independent team can build its own application, payment model, and user experience while using Sentinel’s shared network of independently operated dVPN nodes. Explore Meile dVPN: mathnodes.com/index.php/meil… Explore more dVPN applications built on Sentinel: docs.sentinel.co/get-started…

Decentralized infrastructure needs visibility, not just nodes. For a dVPN network to scale, operators and builders need clear data on health, coverage, performance, connectivity, and network activity. Sentinel already has that operational layer. SentNodes, SuchNode, P2PScan, node testing utilities, and CQAP reporting help operators monitor infrastructure, evaluate performance, and understand how the network is being used. The numbers are increasingly meaningful. More than 800,000 people have used a Sentinel-powered dVPN in 2026 alone. SentNodes is currently showing around 10,000 users per day, while SuchNode shows Sentinel infrastructure across 232 cities. Encrypted dVPN sessions recorded during 2026 are also close to exceeding the combined total from 2023, 2024, and 2025. As Sentinel prepares to migrate to Solana, it is bringing that existing activity with it: active applications, independent node infrastructure, real users, and tooling that already measures what is happening across the network. The migration is not about starting again on a new chain. It is about plugging an already-used decentralized bandwidth network into Solana’s larger ecosystem of applications, developers, payments, liquidity, and infrastructure. For Solana, that means new users and existing real-world activity arriving from day one. For Sentinel, it means a much larger environment to build, integrate, and grow within. Sentinel is bringing usage to Solana, not waiting for @solana to create it. Explore Sentinel infrastructure and applications: docs.sentinel.co/get-started… Node tools and ecosystem resources: p2pscan.com sentnodes.com nodes.suchnode.net

VeilDVPN brings Sentinel-powered dVPN access to Android. Built by @Bitveilofficial, VeilDVPN gives mobile users access to independent peer-to-peer nodes through the Sentinel Network, instead of relying on one centralized VPN provider or closed server fleet. The app supports WireGuard, V2Ray, AmneziaWG, Xray, and Hysteria2, with node browsing, location selection, wallet creation or import, subscriptions, and pay-as-you-go access directly from Android. VeilDVPN also supports a free monthly subscription plan for users holding a @BluefrensNFT, giving the community another way to access decentralized bandwidth. Another example of independent teams building real products on Sentinel, while node operators provide the bandwidth layer underneath. Explore VeilDVPN: bitveil.com/veildvpn Explore more dVPN applications built on Sentinel: docs.sentinel.co/get-started…

Sentinel x402 lets AI agents and automated systems purchase dVPN access directly, without creating accounts, managing subscriptions, holding P2P for gas payments, or relying on human setup. Using USDC on Base, with Solana support upcoming, an agent can request access, receive HTTP 402 payment instructions, authorize the payment, and receive the connection details needed to use Sentinel dVPN infrastructure. Most VPN infrastructure was designed around a human user opening an app, entering payment details, choosing a location, and pressing connect. Autonomous systems need a different model, where connectivity, routing, and privacy-preserving access can be requested, paid for, and used programmatically. Sentinel’s architecture makes this practical because nodes can be discovered, authenticated, and accessed through on-chain infrastructure, RPC access, and CLI-based workflows. That gives software a direct path to find available dVPN nodes and connect without manual setup. For developers, the opportunity isn't just to build another VPN app. It is building products, agents, APIs, and services that can use decentralized bandwidth as a programmable resource, with access available from as low as $0.033 per day. Check out Sentinel x402: x402.sentinel.co/ Build with Sentinel: docs.sentinel.co/

Why does this matter? Commercially available location data has become so revealing that parts of the US military have disabled advertising trackers amid concerns it could be used to track or target personnel. reuters.com/business/media-t…

In this week's edition of Sentinel's Sunday Morality, we ask: Do you think it's moral for companies to sell data about your location, what you search for, and what you do online because you clicked "I agree"? Is accepting a privacy policy really meaningful consent?

A VPN provider can promise “no logs,” but users still have to ask a harder question: can any of that be independently verified? TechRadar recently reported that SplitVPN, formerly NotVPN, was accused of breaching its no-log policy after a leaked database allegedly included around 58 million connection records. SplitVPN denies those records are genuine and maintains that it does not keep connection logs. According to the report, the disputed data allegedly showed which device connected to which server and when. SplitVPN confirmed that leaked subscription metadata was authentic, including email addresses, country of origin, subscription status, masked credit card information, and device names. The wider issue goes beyond one provider. With a centralized VPN, users ultimately depend on one company to operate its infrastructure, secure its systems, and uphold its privacy promises. Sentinel was designed around a different model. Independent teams build dVPN applications, independent operators provide nodes, and open-source infrastructure supports a distributed network rather than a closed server fleet controlled by a single VPN provider. Privacy should not depend entirely on trusting one company’s marketing claims. It should be possible for builders, operators, and users to inspect more of the systems underneath. Use a decentralized VPN powered by the Sentinel Network: docs.sentinel.co/get-started…

Katacomb VPN shows how specialized dVPN applications can be built on top of Sentinel by independent teams, while still giving users direct access to the same decentralized bandwidth network underneath. Built by @proofoftrinity, a long-time Sentinel community member, Katacomb is an open-source Linux desktop client designed for users who want more control over how they connect. It supports six protocols, including WireGuard, V2Ray, OpenVPN, Xray, AmneziaWG, and Hysteria2, with node discovery by location, protocol, and price. Katacomb also supports multi-hop connections across compatible nodes, direct on-chain payments to node operators, latency and download-speed testing before connecting, plus controls for kill switch, DNS, and split tunneling. The latest v1.6.0 update improves the nodes dashboard, adding more polish to the operator and user experience. Katacomb also includes provider tooling for creating plans, leasing nodes, and monitoring subscriber activity, making it more than a basic VPN client. This is the value of an open dVPN ecosystem. Independent teams can build applications for different users, platforms, and use cases, while Sentinel provides the shared network layer powered by independent peer-to-peer nodes. Explore Katacomb VPN: trinitystake.github.io/websi… View the source code: github.com/trinitystake/kata… Explore more dVPN applications built on Sentinel: docs.sentinel.co/get-started…

Sentinel is approaching 2 million total unique users across the network, with multiple independently built dVPN applications already using the same decentralized bandwidth layer. Applications built on Sentinel include @Independentdvpn, @MeileDVPN, @norselabs "DVPN", ChibaTunnel by @TkdAxel , VeilDVPN by @Bitveilofficial , Katacomb VPN by @proofoftrinity , @VALTdata , and the DVPN Telegram Bot by @norselabs The important part is not only the number of apps, but the usage behind them. With current activity, Sentinel would rank inside the top 20 most-used Solana applications by daily active users after migration, bringing real consumer demand into the Solana ecosystem. Each application can serve its own users, brand, interface, payments, and distribution while connecting to independent peer-to-peer nodes underneath. Sentinel provides the shared network layer, while independent teams build products on top. As Sentinel prepares for its migration to @solana, the network is bringing more than protocol infrastructure. It is bringing real users, active applications, independent node infrastructure, and consumer-facing products that can support a wider Sentinel economy inside one of crypto’s strongest builder ecosystems. Explore the Sentinel ecosystem, use a decentralized VPN, build your own dVPN application, create subscription plans, or host a node: dVPN applications: docs.sentinel.co/get-started… Build with Sentinel docs: docs.sentinel.co/ Create and manage VPN plans: plan.sentinel.co/dashboard Host a dVPN node: docs.sentinel.co/dvpn-nodes/… Node Deployer: github.com/sentinel-official… Open-source ecosystem: github.com/sentinel-official

A traditional VPN company usually measures scale by its server fleet size. Sentinel uses a different model: independent node operators provide bandwidth to applications using the network. Those operators form the supply side of the Sentinel Network. They run nodes, contribute bandwidth, expand geographic coverage, and create the connectivity layer that decentralized VPN apps can use without each builder operating a global server network from scratch. For users, the experience can remain simple. Open an app, connect, and use the internet. Underneath, connectivity is supplied by independent peer-to-peer nodes rather than a closed server fleet owned and controlled by one VPN provider. The distinction matters as privacy tools face pressure from platform rules, app stores, payment systems, datacenter policies, and jurisdiction-specific regulation. A traditional VPN company still depends on its own corporate structure and server relationships, while Sentinel distributes participation across operators, applications, and builders. Sentinel is not a single VPN provider operating a closed server fleet. It is shared decentralized bandwidth infrastructure where applications, node operators, and developers can participate in the same network. Explore decentralized VPN applications built on Sentinel: docs.sentinel.co/get-started…

Most people think VPN privacy starts and ends with encryption. The harder question is who controls the network your connection moves through. A VPN can reduce what your ISP sees, but it also introduces a new trust layer. The provider, app, server network, analytics stack, payment system, and operating model all shape the privacy outcome. Many VPN products look similar from the outside. Users open an app, press connect, and expect private internet access, but the infrastructure model underneath can be very different. Sentinel separates the application layer from the decentralized bandwidth network underneath. Multiple independently built VPN applications can use shared infrastructure powered by independent peer-to-peer node operators, rather than relying on one company’s closed server network. For users, the product can still feel simple. For builders, Sentinel provides open-source infrastructure, developer integrations, and a network model that can be inspected and built on rather than accepted as a marketing claim. VPN privacy is not only about whether the tunnel is encrypted. It is also about who operates the network, what data the app collects, and how much control sits with one provider. Explore decentralized VPN applications built on Sentinel: docs.sentinel.co/get-started…

In this week's Sentinel's Sunday Morality: Which matters more online: protecting children or protecting privacy? Age checks can block harmful content, but anonymous access protects adults from having their identity linked to what they read, watch or search.

Independent dVPN has grown to 500,000+ downloads on Google Play, making it one of the clearest examples of what can be built on the Sentinel Network: a consumer VPN application that gives users a familiar Web2 experience while using decentralized infrastructure underneath. Most users do not care which protocol, chain, node, or routing system sits behind the app. They care whether the VPN works, whether it connects reliably, and whether it gives them private access to the internet when they need it. Independent dVPN has turned Sentinel’s decentralized bandwidth into a product mainstream users can understand and use, including people who may have never heard of crypto, DePIN, or decentralized infrastructure. For users, @Independentdvpn is simply a VPN application. For builders, it shows how Sentinel can support real consumer products using independent node operators, open-source infrastructure, and a shared bandwidth network instead of forcing every team to build a global network from scratch. Sentinel does not own the application, the brand, the customer relationship, or the user experience. Independent dVPN is built and operated by an independent team, while Sentinel provides the decentralized network layer underneath. The separation between application and infrastructure matters. Teams can build their own brand, payment flow, distribution, and customer base while using open infrastructure that can be inspected, integrated, and improved by builders across the ecosystem. Mainstream users do not need to understand decentralized infrastructure to benefit from it. They need products that work, with infrastructure that can be verified. Try Independent dVPN, powered by the Sentinel Network: independentdvpn.com Explore more decentralized VPN applications built on Sentinel: docs.sentinel.co/get-started…

Through Plan Manager, builders can turn Sentinel nodes into a subscription-based VPN product without building the full management stack from scratch. They can create plans, attach selected nodes, manage user access, control pricing, and offer customers a familiar VPN subscription experience while building their own brand, app, and customer relationship on top. For a new VPN business, that means less time spent building backend management tools and more time spent on product, distribution, support, and growth. Builders can build on: • A global network of independently operated nodes • Existing decentralized bandwidth infrastructure • Subscription and plan management • Node selection and access controls • Open-source SDKs and APIs • Node deployment and management tools • Infrastructure already used by more than 1.9 million unique users The application, brand, pricing, and customers remain with the builder. Sentinel provides the network layer underneath. Build and manage plans on Sentinel: plan.sentinel.co/