Skip to main content

CLI Architecture & Node Management

� Current Phase: Node Provider Onboarding

Current Focus

QuikDB is currently in the Node Provider Onboarding Phase. Our CLI architecture is focused on enabling infrastructure providers to join and manage their participation in the network.

Node Provider CLI (quikdb-nodes)

┌─────────────────────────────────────────────────────────────────┐
│ QuikDB Nodes CLI (quikdb-nodes) │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ • Authentication and token management │ │
│ │ • Node listing and marketplace integration │ │
│ │ • Resource validation and capability checks │ │
│ │ • Heartbeat monitoring and status reporting │ │
│ │ • Earnings tracking and payout management │ │
│ └─────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘

🔧 Node Provider CLI Commands

Essential Commands

# Authentication
quikdb-nodes auth # Interactive authentication
quikdb-nodes auth --token TOKEN # Direct token authentication
quikdb-nodes auth status # Check authentication status

# Node Management
quikdb-nodes list # List node in marketplace
quikdb-nodes validate # Validate node capabilities
quikdb-nodes status # Check node status

# Monitoring & Maintenance
quikdb-nodes heartbeat --daemon # Start heartbeat monitoring
quikdb-nodes heartbeat --status # Check heartbeat status
quikdb-nodes metrics # View performance metrics
quikdb-nodes test-connection # Test network connectivity

# Earnings & Payouts
quikdb-nodes earnings # View earnings dashboard
quikdb-nodes payouts # Check payout history

Workflow Examples

Initial Node Setup

# 1. Install CLI
npm install -g quikdb-nodes

# 2. Authenticate
quikdb-nodes auth

# 3. Validate system
quikdb-nodes validate

# 4. List node in marketplace
quikdb-nodes list --type compute --tier standard

Daily Operations

# Check node status
quikdb-nodes status

# View earnings
quikdb-nodes earnings

# Ensure heartbeat is running
quikdb-nodes heartbeat --status

🚧 Future CLI Architecture (Planned)

The following CLI tools are planned for future development phases:

Developer CLI (Phase 2)

  • Database deployment commands
  • Application hosting tools
  • Multi-region management
  • Performance optimization

Enterprise CLI (Phase 3)

  • Team management
  • Advanced monitoring
  • Custom integrations
  • Enterprise security

📋 Current Documentation

For detailed command usage:


This architecture will expand as QuikDB moves through development phases.


🏗️ Node Agent CLI (quik-node)

Node Provider Installation

# Install node agent on server
curl -sSL https://install.quikdb.com | bash

# Or manual installation
npm install -g @quiknodes/node-agent

# Initialize node configuration
quik-node init

# Start node agent service
quik-node start --daemon

Node Agent Functions

Container Runtime Management

# Receive deployment request (triggered by platform API)
quik-node deploy \
--image registry.quikdb.com/user/app:latest \
--config deployment-config.json \
--network-config network.json

# Monitor running containers
quik-node ps

# Check container health
quik-node health-check --container app-container-id

# Collect performance metrics
quik-node metrics --export

Resource Management

# Report available resources
quik-node resources --report

# Set resource limits
quik-node limits --cpu 4 --memory 8Gi --storage 100Gi

# Update availability status
quik-node availability --status available --until "2024-12-31T23:59:59Z"

Network Configuration

# Configure container networking
quik-node network setup \
--container app-container-id \
--port 3000:80 \
--domain app.node-us-east-001.quik.run

# Update DNS records
quik-node dns update --domain app.node-us-east-001.quik.run --ip 192.168.1.100

# Configure SSL/TLS
quik-node ssl setup --domain app.node-us-east-001.quik.run

🔄 Deployment Execution Flow

Manual Deployment Process

  1. Developer Action:

    quik deploy --node node-us-east-001
  2. Platform Coordination:

    • Validate node availability
    • Build and push Docker image to node-accessible registry
    • Generate deployment configuration
    • Establish secure connection to node
  3. Node Execution:

    # Executed on node-us-east-001
    quik-node deploy \
    --image registry.quikdb.com/user/myapp:latest \
    --config /tmp/deployment-abc123.json
  4. Container Lifecycle:

    • Pull Docker image
    • Create container with specified configuration
    • Configure networking and SSL
    • Start health monitoring
    • Report deployment success

API-Triggered Deployment

  1. API Call to Platform:

    curl -X POST https://api.quikdb.com/v1/deployments \
    -H "Authorization: Bearer $TOKEN" \
    -d '{
    "image": "myapp:latest",
    "nodeId": "node-us-east-001",
    "config": {...}
    }'
  2. Platform Processes Request:

    • Validate authentication and authorization
    • Check node availability
    • Queue deployment job
  3. API Call to Node Agent:

    # Platform calls node agent API
    curl -X POST https://node-us-east-001.quik.run/api/deploy \
    -H "Authorization: Bearer $NODE_TOKEN" \
    -d '{
    "image": "registry.quikdb.com/user/myapp:latest",
    "config": {...}
    }'
  4. Node Agent Executes CLI:

    # Node agent triggers local CLI
    quik-node deploy --from-api /tmp/deployment-request.json

📊 Node Reputation System

Reputation Calculation

Performance Metrics (40%)

  • Uptime: Historical availability percentage
  • Response Time: Average container startup time
  • Resource Utilization: Efficient resource usage
  • Health Check Success Rate: Container health monitoring

User Feedback (30%)

  • Star Ratings: 1-5 star ratings from developers
  • Written Reviews: Qualitative feedback
  • Repeat Usage: Developers choosing the same node again
  • Support Responsiveness: Node provider communication

Operational Excellence (20%)

  • Update Frequency: Node agent and system updates
  • Security Posture: Security scanning and compliance
  • Documentation Quality: Setup and troubleshooting guides
  • Community Participation: Forum activity and contributions

Business Reliability (10%)

  • Payment History: Consistent pricing and billing
  • Capacity Planning: Avoiding overcommitment
  • Transparency: Clear communication about maintenance
  • Geographic Coverage: Reliable location-based service

Reputation Display

quik nodes info node-us-east-001

Node: node-us-east-001
├── Reputation: ⭐⭐⭐⭐⭐ (4.8/5.0)
├── Reviews: 127 reviews (98% positive)
├── Uptime: 99.7% (last 30 days)
├── Avg Response: 12 seconds
├── Performance: 92/100
├── Last Updated: 2 days ago
└── Pricing: $18/month (your config)

🔐 Security & Trust

CLI Security Features

Authentication & Authorization

# Developer CLI authentication
quik auth login --provider github
quik auth token create --name "production-deployments"

# Node agent authentication
quik-node auth register --provider-key $PROVIDER_KEY
quik-node auth verify --certificate /etc/quik-node/cert.pem

Secure Communication

  • TLS 1.3: All CLI-to-platform communication encrypted
  • Certificate Pinning: Prevent man-in-the-middle attacks
  • Token-based Auth: Short-lived tokens for API access
  • SSH Key Management: Secure key exchange for node access

Container Security

# Image security scanning
quik-node security scan --image myapp:latest

# Runtime security monitoring
quik-node security monitor --container app-container-id

# Compliance reporting
quik-node compliance report --standard SOC2

📈 Monitoring & Observability

CLI-Based Monitoring

Real-time Monitoring

# Stream logs from container
quik logs --follow --container app-container-id

# Monitor resource usage
quik monitor --metrics cpu,memory,network

# Watch deployment status
quik watch --deployment deployment-abc123

Node-Level Monitoring

# Node agent monitoring
quik-node monitor --export-to platform

# Performance benchmarking
quik-node benchmark --duration 300s

# Health checks
quik-node health --comprehensive

Centralized Logging

  • Log Aggregation: All CLI operations logged centrally
  • Audit Trail: Complete history of deployment actions
  • Performance Analytics: CLI command timing and success rates
  • Error Tracking: Automated error detection and reporting

🎯 Go-to-Market Strategy Alignment

CLI-First Approach Benefits

  1. Developer Familiarity: CLI tools are standard in developer workflows
  2. Automation Friendly: Easy to integrate into CI/CD pipelines
  3. Transparency: Developers see exactly what's happening
  4. Flexibility: Manual control when needed, automation when desired
  5. Troubleshooting: Direct access to logs and container state

Node Provider Value Proposition

  1. Simple Setup: Single CLI installation to become a provider
  2. Automated Management: Node agent handles complex deployment logic
  3. Transparent Earnings: Clear visibility into utilization and payments
  4. Reputation Building: System rewards reliable service delivery
  5. Community Integration: CLI tools connect providers with developers

Market Differentiation

  • No Black Box: Full transparency in deployment process
  • Direct Relationships: Developers can build relationships with trusted nodes
  • Flexible Pricing: Market-driven pricing rather than fixed tiers
  • Community-Driven: Success depends on community trust and reputation
  • Open Architecture: CLI tools can be extended and customized

This CLI-driven architecture ensures that Quik Nodes maintains transparency, flexibility, and developer control while enabling a thriving marketplace of infrastructure providers.