Self-Hosted
Deploy the CMX Protocol in your own environment with complete control - from simple node deployment to enterprise-grade infrastructure.
What Is Self-Hosting?
Self-hosting means running the CMX Protocol stack in your own environment. You have two main options:
๐ Open Source Deployment (Free)
Deploy the CMX Protocol however you want using our open-source components:
CMX geth node from GitHub - The core blockchain client
Connect to Ethereum L1 - Attach to any Ethereum node
Your infrastructure - Use any cloud, on-premise, or hybrid setup
Community support - GitHub issues and Discord community
๐๏ธ Recommended Architecture (Battle-Tested)
Use CapSign's production-ready infrastructure blueprints:
Terraform modules - AWS VPC, EKS, security configurations
Kubernetes Helm charts - Production-ready deployment manifests
Monitoring stack - Prometheus, Grafana, AlertManager
Security hardening - SOC compliance configurations
Step-by-step guides - From setup to production operations
Core Requirements (All Deployments)
Regardless of how you deploy, every CMX Protocol deployment needs:
Essential Components
CMX geth node - Download from GitHub
Ethereum L1 connection - Mainnet, Sepolia, or your preferred testnet
Database storage - For blockchain state and transaction data
Network connectivity - P2P networking for blockchain sync
Basic Architecture
[Your Application]
โ
[CMX geth node] โ Your Infrastructure Choice
โ
[Ethereum L1 node] โ Can be external provider
Deployment Options
Option 1: Simple Node Deployment
Perfect for: Development, testing, small applications
What you need:
Linux server (cloud or on-premise)
Docker or direct binary installation
Connection to Ethereum L1 (can use Infura, Alchemy, etc.)
Getting started:
Download CMX geth from GitHub releases
Configure connection to Ethereum L1
Start the node and sync blockchain state
Connect your application via RPC
Cost: Infrastructure only (typically $50-200/month)
Option 2: CapSign Recommended Architecture
Perfect for: Production applications, enterprise deployments, compliance requirements
What you get:
Production-ready Terraform - AWS VPC, EKS, security groups, IAM
Kubernetes Helm charts - Scalable, monitored, highly available
Security configurations - SOC compliance, encryption, access controls
Monitoring & alerting - Full observability stack
Documentation - Step-by-step deployment and operations guides
What you need:
AWS account and DevOps expertise
Kubernetes and infrastructure management skills
2-4 weeks for initial setup and customization
Cost: Infrastructure only (typically $1,000-3,000/month depending on scale)
Enterprise Support (Optional)
For organizations wanting additional support beyond community resources:
Support Packages
๐ฅ Professional Support - $500/month
Email support with 48-hour response SLA
Documentation access and updates
Best practices consultation
๐ฅ Enterprise Support - $2,000/month
Private Slack channel with engineering team
Priority bug fixes and feature requests
Architecture review and optimization
Compliance consultation (SOC, regulatory)
๐ฅ Strategic Partnership - Custom Pricing
Dedicated customer success manager
Custom development and integrations
On-site training and workshops
24/7 incident support
Why Use Our Recommended Architecture?
Battle-Tested Components
Our Terraform and Kubernetes setup has been proven in production with:
99.99% uptime across customer deployments
SOC 2 Type II compliance ready configurations
Security best practices built-in from day one
Cost optimization through right-sizing and automation
Enterprise Features
High availability across multiple AWS availability zones
Auto-scaling for both infrastructure and blockchain nodes
Monitoring & alerting with Prometheus and Grafana
Backup & disaster recovery automated procedures
Security scanning with Checkov and other tools
Operational Excellence
Infrastructure as Code - All changes tracked and versioned
CI/CD integration - Automated testing and deployment
Secrets management - Secure handling of keys and credentials
Documentation - Comprehensive guides for all operations
Getting Started
๐ Quick Start (Open Source)
Download CMX geth: Visit GitHub releases
Configure L1 connection: Point to your Ethereum node or provider
Start the node: Follow README instructions
Connect your app: Use standard JSON-RPC interface
๐๏ธ Production Deployment (Recommended Architecture)
Prerequisites - AWS account, tools setup
Quick Start Guide - 30-minute deployment overview
Repository Setup - Fork our templates
Secrets Configuration - Configure credentials
Full Installation - Complete production setup
๐ฌ Get Support
Community Support (Free):
GitHub Issues - Bug reports and features
Discord - Community discussion
Enterprise Support (Paid):
[email protected] - Support package pricing
[email protected] - Strategic partnerships
Migration and Flexibility
Start Simple, Scale Up
Many customers follow this progression:
Development: Simple node deployment for testing
Staging: Recommended architecture for pre-production
Production: Full enterprise setup with support
Hybrid Options
Self-hosted development + Managed production
Multiple regions: Self-hosted in some, managed in others
Gradual migration: Move workloads as needs change
Compare Your Options
Control
Complete
Complete
Shared
Setup Time
Hours
2-4 weeks
Minutes
Expertise Required
Basic Linux
DevOps/Kubernetes
None
Infrastructure Cost
$50-200/month
$1-3K/month
Included
Support
Community
Optional paid
Included
Compliance
DIY
SOC-ready
SOC certified
High Availability
DIY
Built-in
Guaranteed
๐ Detailed comparison: Self-Hosted vs Managed Analysis
Ready to Deploy?
For Simple Deployment:
๐ Download CMX Node from GitHub and follow the README
For Production Architecture:
๐ Start with Infrastructure Overview to understand the full setup
Need Help Deciding?
๐ Try our Interactive Demos to experience CMX Protocol without any infrastructure
The CMX Protocol gives you the flexibility to deploy however fits your needs - from simple development setups to enterprise-grade production infrastructure.
Last updated
Was this helpful?