IXCDN Node Resource Partnership
Recruiting compliant servers, bandwidth and GPU nodes for the IXCDN edge network
IXCDN works with IDC, ISP, cloud, GPU and edge-site partners. After entity and resource review, accepted nodes can take CDN, edge-security, AI token-stream and model-inference traffic.- Reviewed admission
- Non-PCDN
- AI-node priority
- Reconcilable earnings
Recruiting
Which nodes we recruit
We prioritize stable public bandwidth, verifiable facilities, GPU/inference capacity and key regional routes. Stable resources, complete evidence and high uptime improve resource review and routing eligibility.AI inference nodes
GPU servers, inference clusters, model-service pools or AI API upstreams for token streams, image/video generation and private enterprise model ingress.
AI + CDN hybrid nodes
GPU, cache disk, stable bandwidth and public ingress at one site for AI inference, content delivery, downloads and edge security traffic.
IDC / ISP compliant nodes
Data-center, carrier, exchange and local route resources for regional coverage, cross-network optimization, enterprise apps and key-city quality.
Edge cache nodes
Stable public IPs, usable bandwidth, SSD/NVMe cache disks and Linux hosts for websites, downloads, static assets and media delivery.
Not PCDN
How IXCDN differs from PCDN
PCDN focuses on rapid scale-out and low-cost content distribution. IXCDN handles reviewed, accepted and reconcilable workloads for enterprise CDN, edge security, AI token streams and GPU inference. Joining IXCDN is not about selling spare bandwidth; it is about connecting controlled resources to a routing network billed by workload type.PCDN often relies on scattered endpoints or weakly controlled resources.
IXCDN recruits reviewable, contractable and sustainably operated servers, IDC, ISP, GPU and edge-site resources.
PCDN emphasizes rapid scale-out.
IXCDN admits partners through entity, KYC and resource checks, so nodes can take enterprise and AI workloads.
PCDN may prioritize cost over stability.
IXCDN routes by region, carrier, load, GPU capability, health and workload policy; healthy nodes receive more traffic.
PCDN settlement often relies on node-side reports.
IXCDN defines earnings for AI token streams, GPU inference, enterprise CDN and billable traffic, billed by workload type.
PCDN mainly covers content delivery.
IXCDN covers CDN, edge security, AI token streams, GPU inference and model-service ingress.
Settlement
AI nodes get priority for billable workloads
Stable bandwidth handles CDN and edge-security traffic; nodes with GPU and model-service capacity can take AI token streams, inference requests and enterprise model ingress. IXCDN shows node status, load, traffic and earnings, and reconciles actual contribution through audited logs.AI nodes are billed by inference requests, token streams, GPU resources and upstream model-service capacity.
Stable edge nodes handle websites, downloads, media, APIs and edge-security traffic, billed by workload type.
Logs, DNS/GSLB, origin fetches, load and anomaly checks validate contribution, and settlement follows the reconciled result.
Onboarding
Five steps to join IXCDN
Submit resources
Provide entity details, resource type, coverage region, carrier, bandwidth, node count and GPU/facility notes.
Review
Entity, resource authenticity, intended use, regional coverage and operational continuity are checked.
Download and deploy
After approval, em-edge / em-edge-ai binaries, install guide and node claim flow are unlocked.
Node acceptance
After deployment, health, version, load, connectivity and declared resource information are verified.
Track earnings
Accepted nodes enter routing and the portal shows status, load, traffic and reviewed earnings views.
FAQ
Can individuals join?
Yes, but companies, IDC, ISP and AI-service providers with GPU, fixed servers, compliant facilities or stable public bandwidth are prioritized.
Is login required to read this page?
No. This page is public. Submitting materials, downloading binaries and claiming nodes require the affiliate portal.
Do AI nodes submit upstream keys here?
No upstream keys are collected on this public page. Service credentials are configured on the node under the deployment security process and are not returned in plaintext here.
Can AI nodes earn more?
Nodes with GPU, inference service or model-ingress capacity can take higher-billed workloads. Earnings depend on resource quality, uptime, region and actual routing, and are usually above basic cache nodes.
Have sustainably operated servers, bandwidth, GPUs or facility resources?
Submit your resource details first. Complete evidence, clear regions, stable bandwidth and a compliant entity make it easier to move into review and node acceptance.