Operating model
Partners can always choose to run their own Canton validator node in their own infrastructure. That path gives maximum internal control, but it also requires the partner to own DevOps, monitoring, weekly release updates, traffic management, and operational support. With C8 Validator as a Service, C8 takes responsibility for the technical setup and ongoing operation of the validator environment.Partner-managed
The partner runs the validator in its own infrastructure and owns updates, monitoring, traffic, and incident response.
C8-managed
C8 prepares, deploys, monitors, updates, and operates the validator as part of the managed service.
Onboarding flow
1
Confirm validator scope
C8 and the partner confirm operating requirements, expected usage, and whether the validator supports a wallet, token, settlement, or custom workflow.
2
Prepare isolated environment
C8 creates an isolated infrastructure environment for the partner validator and configures the required deployment baseline.
3
Complete registration steps
C8 supports the registration process and collects the technical details required for network access.
4
Submit IPs for allowlisting
Because Canton is a permissioned network, C8 submits the required IP information to the Foundation for whitelist approval.
5
Deploy and validate the node
C8 deploys the validator, verifies connectivity, checks service health, and confirms the node is ready for partner workflows.
6
Move into managed operations
After launch, C8 manages monitoring, alerts, updates, traffic handling, and ongoing infrastructure support.
Operational responsibilities
The managed service is designed to cover the validator responsibilities that usually require a dedicated infrastructure team.- Release management — applying required regular updates and keeping the validator aligned with network expectations.
- Monitoring and alerting — tracking node health, service availability, and operational signals.
- Traffic management — ensuring the validator can handle expected network and partner traffic patterns.
- Environment isolation — separating partner validator infrastructure from other operational environments.
- Production support — responding to issues and coordinating follow-up where network or infrastructure dependencies are involved.
Partner responsibilities
The partner remains responsible for the business and product workflows that use the validator. This typically includes:- Defining the product or institutional workflow that depends on Canton
- Providing required business and registration information
- Confirming expected usage patterns and operational requirements
- Integrating applications, wallets, token services, or back-office systems with the C8 stack
- Managing end-user, compliance, and business process requirements outside the validator infrastructure layer
Production readiness
Before a validator is considered ready for production use, C8 verifies the core operational requirements.The node should be deployed in the isolated environment, registered for the network, allowlisted where required, monitored, and connected to the partner workflow that depends on it.
When to contact C8
Contact the C8 team when your product or institution needs Canton validator connectivity and you want C8 to manage the setup and operation path.Discuss validator scope
Reach out to discuss your requirements, product workflow, and expected launch timeline — we’ll guide you through the next steps.
Plan production launch
Coordinate registration, allowlisting, infrastructure setup, and operational readiness.
Get in touch
Interested in Validator as a Service or have any other questions? Drop us a line at integrations@cantor8.io — we’re happy to help.