Core Capabilities
Spider Protocol operates as a transparent overlay network on top of your CloudNexus VPS, Kubernetes, or Bare Metal deployments.
⚡ Sub-5ms Routing
Anycast-aware path selection with real-time latency probing. Dynamically routes traffic through optimal mesh nodes without DNS propagation delays.
🔁 Self-Healing Mesh
Continuous health checks at 100ms intervals. Automatic circuit breaking and traffic rerouting when nodes drop below SLA thresholds.
🔐 Zero-Trust Tunneling
mTLS enforced across all control-plane and data-plane communications. Session keys rotate every 15 minutes. Fully audit-logged.
Mesh Architecture
Distributed control plane with edge-optimized data plane. No single point of failure.
🌐
Client / LB
🕏
Spider Core
Routing Engine + Service Mesh
📦
App Cluster
🗄️
DB / Cache
Configuration
Define routing rules, health checks, and failover policies using `spider.yaml` or the CloudNexus CLI.
spider.yaml
apiVersion: spider.cloudnexus.io/v2
kind: MeshConfig
metadata:
name: production-mesh
region: global
spec:
routing:
strategy: latency-optimized
failover: automatic
timeout: 3000ms
health:
interval: 100
threshold: 3
security:
mTLS: enforced
rotation: 900s| Parameter | Default | Description |
|---|---|---|
| routing.strategy | latency-optimized | Path selection algorithm |
| health.interval | 100ms | Node probe frequency |
| security.mTLS | enforced | Transport encryption mode |
| scaling.limit | 5000 | Max concurrent connections |
API Endpoints
Programmatic control over mesh topology, routing tables, and node lifecycle.
REST API v2
GET /api/v2/spider/mesh/nodes # List active mesh nodes
POST /api/v2/spider/routes/create # Inject custom routing rule
PUT /api/v2/spider/config/override # Apply runtime configuration
DELETE /api/v2/spider/sessions/{id} # Revoke active tunnel
// Example Request
curl -X POST https://api.cloudnexus.io/v2/spider/routes/create \\
-H "Authorization: Bearer $CN_TOKEN" \\
-d '{"match": ".*.api.example.com", "backend": "pool-us-east-1", "weight": 100}'Live Status
Real-time metrics from your active Spider Protocol deployment.
99.998%
Uptime (30d)
3.2ms
Avg. Route Latency
14,829
Active Connections
0
Failovers (24h)