Guides
Operations & support
What happens after go-live — maintenance, incidents, and agreements.
Ongoing operations
Azxa keeps the chain client synced, applies stable releases, and coordinates network upgrades. You focus on application logic; we handle disk growth, peering, and node health on the infrastructure side.
Monitoring
Nodes are monitored for sync status, resource usage, and availability. If something affects your endpoint, we work the issue on the infrastructure layer and keep you informed according to your support channel.
Service level agreement
Uptime and response expectations are defined in our Service Level Agreement . Review it before production cutover.
Contact
- Book a meeting — scoping, architecture, migrations
- Azxa app — endpoints, billing, node status
- Blog — product and infrastructure notes
Scaling
Need more chains, archive tiers, redundant nodes, or a move from public RPC providers? Open a new request with current and target load — we resize or add deployments without forcing you onto shared gateways.
Telegram
Instagram
LinkedIn
TikTok
'%20/%3e%3cpath%20fill-rule='evenodd'%20clip-rule='evenodd'%20d='M205.843%20538L267.624%20271.015L270.176%20259.985L258.861%20259.985L-0.000128295%20259.985L-0.000129868%20277.984L247.545%20277.984L187.399%20538L205.843%20538Z'%20fill='url(%23paint1_linear_835_1234)'%20/%3e%3cdefs%3e%3clinearGradient%20id='paint0_linear_835_1234'%20x1='376.119'%20y1='2.17877e-06'%20x2='312.095'%20y2='277.971'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%23FF3131'%20stop-opacity='0'%20/%3e%3cstop%20offset='1'%20stop-color='%23FF3131'%20/%3e%3c/linearGradient%3e%3clinearGradient%20id='paint1_linear_835_1234'%20x1='205.889'%20y1='538'%20x2='269.914'%20y2='260.029'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%23FF3131'%20stop-opacity='0'%20/%3e%3cstop%20offset='1'%20stop-color='%23FF3131'%20/%3e%3c/linearGradient%3e%3c/defs%3e%3c/svg%3e)
