Product, customers and distribution
Brand, interface, identity, billing, policy, support and a useful reason for network demand.
Build
Build on UR
Launch or migrate existing products onto UR’s residential privacy network. Network Operators own the customer experience and bring demand; UR provides the infrastructure. UR (SN25) is extending network coordination and incentives to Bittensor.
100K+ providers100+ countries350K+ monthly users on URnetwork
The network is live. Its next product may not exist yet.
Supply, measurement and incentives
100K+ residential providers across 100+ countries, validators, miner UIDs and SN25 settlement.
See the network beneath the product.
Select one of six example products, then reveal the provider network and subnet foundation beneath its interface. Each shows one way builders could use the same shared infrastructure.
Functional teaching model · architecture grounded in the SN25 deckSELECT ONE OF SIX EXAMPLESThe product changes. The network foundation does not.
These are inspiration points rather than a catalogue of what can be built. Choose an example to see its customer proposition and demand profile placed on the same SN25 architecture.
TRAFFICVERIFICATIONECONOMICS
- 01 ROUTE
- 02 VALIDATE
SELECTED LAYER
Product above shared infrastructure
The selected operator product sits above the shared provider network and SN25 foundation. Move the reveal slider to separate the system, then select a plane to understand its role.
ONE OPERATOR PRODUCT · TWO SHARED PLANESSIX PLACES TO BEGINIllustrative opportunities for builders.
OPPORTUNITY 01 / PRIVACY PRODUCT
White-label VPN
A privacy brand keeps the customer relationship and changes the network carrying the traffic underneath.
COMPARE BRIEF TREATMENTS
Launch a VPN for an audience you already serve
A telecom, security company, community or consumer brand may already have the trust and distribution needed to launch a VPN. The infrastructure challenge is providing regional exits, maintaining route diversity and monitoring network quality. A Network Operator could build the VPN experience, subscription and policy layer on top of UR’s provider network. The result could be a standalone VPN, an embedded privacy feature or a travel product designed for a specific audience.
Use UR’s provider network instead of building a private fleet
UR provides access to residential bandwidth contributed by more than 100K providers across 100+ countries. Providers carry encrypted ingress and egress traffic, while the operator matches users to available routes. Independent validators test provider trails for liveness, latency and real-time transit, supplying a network-quality signal without validating each customer session. The operator can focus on the VPN product, distribution and service.
What remains with the operator
Brand, client or SDK integration, identity, accounts, billing, support, route policy, abuse controls, compliance and the promise made to customers. UR supplies network leverage; the operator remains responsible for the service.
What the product could become
Potential customer
A security, telecoms or privacy brand with an audience it already serves.
The problem
Offering private, region-selectable internet access normally requires building and operating a geographically distributed exit fleet.
Product proposition
A branded VPN or privacy feature powered by UR’s measured residential routing layer.
How demand reaches the network
Concrete usage scenario
A customer chooses a region in the operator’s app. The operator authenticates the user and applies policy; SN25 matches a measured miner path to a residential exit and returns the encrypted session.
How demand moves through the network
Customeroperator identity + policyminer chainresidential exitpublic destination. The response returns through the same contracted path.
What you build. What SN25 provides.
What the operator owns
Brand, client or SDK integration, accounts, billing, support, traffic policy, abuse controls and the service promise.
What UR / SN25 supplies
Multi-hop encrypted routing, 100K+ provider supply, 100+ country reach, measured transfer and the subnet incentive market.
Where the value exchange happens
Customer demand can be subscription- or service-led. The operator’s network charge reflects active usage and GB/day; that real usage adds demand to SN25.
Important constraints and open questions
- Regional capacity and latency
- Abuse prevention and destination policy
- Platform integration
- Consumer and privacy compliance
OPPORTUNITY 02 / COMMUNICATIONS
Encrypted communications
A communications product that combines its own application security with independently supplied network transport.
COMPARE BRIEF TREATMENTS
Make transport part of the privacy model
Encrypted communications depend on more than message content. Availability, regional reach and reliance on a single transport fleet also shape the service. A Network Operator could use UR beneath business messaging, field communications or machine-to-machine traffic, pairing its own security model with independently supplied residential network capacity.
Add distributed transport without outsourcing the product
UR gives the Network Operator access to residential routes across multiple markets. The subnet coordinates incentives and validator measurements for that supply. This can broaden regional reach and reduce dependence on a fixed egress fleet, while the operator remains responsible for the communications product and its security model.
What remains with the operator
The communications experience, encryption and key model, identity, storage, deliverability, retention, abuse controls, billing, support and every claim made about metadata. Distributed routing can strengthen the product, but it cannot substitute for sound application security.
What the product could become
Potential customer
Teams, institutions or privacy products buying secure mail, messaging or machine communications.
The problem
Application encryption can protect content while the transport layer still depends on one centrally operated network path.
Product proposition
A communications product that keeps identity, keys and storage in its own security model while UR carries encrypted payloads over distributed routes.
How demand reaches the network
Concrete usage scenario
A team member sends an end-to-end encrypted message. The operator handles identity, keys and product policy; UR carries the ciphertext across an independently supplied and measured path.
How demand moves through the network
Sender appoperator authentication + message servicecontracted miner pathrecipient service. Content keys and application storage remain outside the subnet.
What you build. What SN25 provides.
What the operator owns
The mail or messaging product, key management, storage, deliverability, identity, retention, abuse controls, billing and support.
What UR / SN25 supplies
Distributed encrypted transport, routable provider capacity, per-transfer measurement and network settlement primitives.
Where the value exchange happens
Seat- or service-led customer demand creates recurring network usage. The subnet measures the active demand and data moved underneath the product.
Important constraints and open questions
- Key custody and recovery
- Metadata minimisation
- Deliverability and interoperability
- Regulatory and retention requirements
OPPORTUNITY 03 / AGENT INFRASTRUCTURE
Agent access
Policy-controlled public-web access for autonomous software operating across markets.
COMPARE BRIEF TREATMENTS
Build an accountable network layer for agents
UR already supports authenticated network access and regional route selection for agents. A Network Operator could turn that capability into a dedicated API or browser runtime with workload identity, destination policy, rate limits and usage records for research, monitoring and enterprise automation.
Turn residential reach into a programmable primitive
UR supplies residential egress across markets. Providers carry traffic and validators measure the underlying routing service. The operator packages that reach into a developer product with controls, tooling and a compliance model designed for its customers.
What remains with the operator
Authentication, destination policy, audit records, rate limits, workload isolation, developer tooling, billing, abuse prevention and compliance with the rules of destination services. Network reach is useful only when the product makes its use governable.
What the product could become
Potential customer
Developers and platforms running agents, browsers, retrieval jobs or approved automations.
The problem
Automated workloads need policy, auditability and geographic reach without every developer operating a residential access fleet.
Product proposition
An API or runtime that gives each agent session an approved region, route policy and operator-side audit record.
How demand reaches the network
Concrete usage scenario
An agent requests a public page in a target market. The operator authenticates the workload, records policy and selects constraints; SN25 assembles and measures a provider path before returning the result.
How demand moves through the network
Agent runtimeoperator API + policy logmeasured miner chainresidential originpublic web. Evidence and results return to the operator’s developer surface.
What you build. What SN25 provides.
What the operator owns
Agent authorisation, destination policy, audit records, runtime or browser layer, rate limits, billing, developer experience and compliance.
What UR / SN25 supplies
Geographically distributed residential routes, provider matching, proof-of-transit and measured network usage.
Where the value exchange happens
API sessions and data movement create network demand. The commercial layer can be usage-led while SN25 remains the shared bandwidth market underneath.
Important constraints and open questions
- Destination permission and terms
- Attribution and audit quality
- Anti-abuse controls
- Rate limits and workload isolation
OPPORTUNITY 04 / RESEARCH + INTELLIGENCE
AI answer visibility
Measure how public AI systems represent a brand across prompts, places and time.
COMPARE BRIEF TREATMENTS
Track how AI answers vary across markets and time
Brands and research teams want to understand how publicly accessible AI systems describe them, which sources appear and how answers vary across prompts, markets and time. Credible comparison requires a defined query set, controlled account state and repeated evidence capture. A Network Operator could turn those observations into monitoring, launch reports or issue tracking.
Make geography part of the observation system
UR provides residential access across markets, while the subnet measures the underlying routing supply. This broadens where observations can be collected, but it does not validate an answer or research conclusion. The operator owns the prompts, accounts, sampling, capture method and interpretation.
What remains with the operator
Research methodology, permissions, prompt design, sampling, evidence capture, quality control, analysis, reporting and the customer workflow. The product must distinguish a sampled observation from a universal claim about an answer engine.
What the product could become
Potential customer
Brands, agencies and intelligence teams monitoring public answer surfaces.
The problem
A single data-centre observation cannot show whether answers, sources and recommendations vary across real markets.
Product proposition
A research product that observes public answer surfaces from defined residential markets and compares captured results over time.
How demand reaches the network
Concrete usage scenario
A defined prompt set is dispatched across selected markets. The operator controls sampling and capture; UR supplies the residential vantage points; the product compares answers and sources over time.
How demand moves through the network
Research scheduleroperator sampling + capture serviceregional miner pathspublic AI surfacesevidence store + analysis.
What you build. What SN25 provides.
What the operator owns
Prompt methodology, permissions, sampling, evidence capture, quality control, analysis, reporting, accounts and customer workflow.
What UR / SN25 supplies
Residential geographic breadth, independently supplied paths and measurable transfer across the selected markets.
Where the value exchange happens
This is primarily data-led demand: fewer end users can generate repeated regional observations. UR supplies the reach, not the research method.
Important constraints and open questions
- Platform permissions and terms
- Sampling validity
- Answer volatility and reproducibility
- Evidence retention and privacy
OPPORTUNITY 05 / MEDIA INTELLIGENCE
Ad verification
Collect timestamped residential observations of adverts, listings or prices in selected markets.
COMPARE BRIEF TREATMENTS
Verify delivery from the market where it mattered
Advertisers and brands may need an independent record of what appeared in a specific market. Data-centre requests can be blocked or treated differently from residential traffic. A Network Operator could schedule residential checks, timestamp the returned result and compare it with the placement expected. Repeated samples can show a pattern; no single capture proves campaign-wide delivery.
Treat residential observation as measurable network supply
UR gives the operator residential access across selected markets. Providers carry the requests and independent validators measure the underlying routing supply; neither the network nor the validators verify the advertisement itself. The operator defines the sampling, capture and evidentiary standard.
What remains with the operator
Sampling rules, permissions, capture tooling, timestamps, evidence integrity, anomaly detection, reporting and alerts.
What the product could become
Potential customer
Advertisers, agencies, marketplaces and brand owners buying or protecting regional presence.
The problem
Data-centre checks can be blocked or shown a different experience from the one a real household receives.
Product proposition
A verification product that schedules regional samples, captures evidence and reports discrepancies against an expected result.
How demand reaches the network
Concrete usage scenario
A campaign check requests a market and time window. The operator dispatches a permitted observation through a measured residential route, captures the public result and returns a timestamped sample to the buyer.
How demand moves through the network
Campaign scheduleoperator policy + evidence captureregional miner pathpublic advert or listingtimestamped result + analysis.
What you build. What SN25 provides.
What the operator owns
Measurement rules, evidence integrity, compliance, capture tooling, anomaly detection, reporting, alerts and the enterprise workflow.
What UR / SN25 supplies
Residential regional origin, distributed provider capacity, transfer measurement and validator-scored network quality.
Where the value exchange happens
Verification is data-led and can move substantial observation traffic per customer. Network reach is an input; the operator creates the evidence product.
Important constraints and open questions
- Evidence integrity and audit trail
- Consent, platform rules and legality
- Fraud and manipulation resistance
- Regional availability
OPPORTUNITY 06 / RETRIEVAL PRODUCT
Private search
A focused search or answer product that minimises what its operator records and distributes the network path used for retrieval.
COMPARE BRIEF TREATMENTS
Build search for a defined audience or workflow
Search queries reveal intent. A Network Operator could build a focused retrieval or answer product for a profession, research workflow or privacy-conscious audience without depending on behavioural advertising. UR provides the network access beneath retrieval; the operator owns the index, ranking or model and the customer relationship.
Use distributed routing as one layer of the privacy model
UR can carry retrieval and ingestion traffic through residential routes across markets, while the subnet coordinates the supply behind those routes. Routing can reduce dependence on a fixed access fleet, but it does not hide queries from the search operator, model provider or source systems. Query privacy still depends on the operator’s architecture, logging and retention choices.
What remains with the operator
The index or source relationships, query protections, ranking, model or answer system, retention policy, logs, billing and customer experience. Distributed routing is one useful layer in a private retrieval product, not a complete privacy guarantee.
What the product could become
Potential customer
Privacy-conscious users or applications retrieving information on their behalf.
The problem
Search and answer products can centralise queries, profiles, retrieval paths and behavioural histories in one operator.
Product proposition
A focused search or answer engine with explicit query-handling rules and distributed transport beneath retrieval and ingestion.
How demand reaches the network
Concrete usage scenario
A user submits a query to the operator’s answer product. The operator applies its query-handling and retention policy; UR carries retrieval traffic across distributed routes before the ranked answer returns.
How demand moves through the network
User queryoperator query protection + rankingdistributed retrieval or ingestion pathssourcesanswer surface.
What you build. What SN25 provides.
What the operator owns
Index or search access, query protections, ranking, model or answer system, source policy, logs, billing and the full customer experience.
What UR / SN25 supplies
Distributed routing, residential provider reach, measurable transfer and the shared subnet market beneath retrieval.
Where the value exchange happens
User demand and retrieval volume both matter. The product can differentiate on intent or privacy while drawing on the same network foundation.
Important constraints and open questions
- Index and content rights
- Query-log minimisation
- Model and source provenance
- Latency, abuse and answer quality
BringYour is the first Network Operator.
Its first product, URnetwork, is a consumer VPN available across mobile, desktop and browser. BringYour owns the product experience and customer relationship; UR provides the network that powers it.
URnetwork has more than 350K monthly active users. This shows the model working at consumer scale: operator demand routed across shared provider capacity.
CUSTOMER PRODUCTURnetwork VPNNETWORK DEMANDActive users + data movedSHARED SUPPLY100K+ providers across 100+ countries
EXPLORE THE URNETWORK VPN ↗One demand signal. Three network responses.
Customer demand becomes routed service
The operator authenticates and applies product policy. SN25 coordinates a measured path through miner capacity and residential ingress or egress.
Product → operator → miner path → provider exitValidators test the path independently
Validators walk operator-assigned chains and measure uptime, transfer and proof-of-transit. That quality signal informs consensus.
Validator probes → measured quality → UID scoringDemand and rewards remain separate flows
Operator deposits enter the subnet reserve. Bittensor emission rewards miners and validators for measured useful service; deposits are not passed through as miner payouts.
Operator deposit → reserve · emission → measured supplyYou build the reason to use the network.
SN25 is UR’s Bittensor subnet: the coordination and incentive layer beneath the provider network. It gives builders infrastructure to draw on without deciding what the customer product should be.
The product and customer relationship
Product experience, brand, users, identity, billing, policy, support, compliance and the commercial reason for network demand.
Access to network infrastructure
Distributed residential network providers, encrypted bandwidth, and an incentive system supporting reliable supply.
The next operator
Become a Network Operator
Bring an existing product or explore launching a new one on top of our fleet of network providers. Read the documentation and speak with the UR team about network fit.