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.
Status & SLA
Check live availability on status.azxa.io . Uptime and response expectations for dedicated deployments are agreed during onboarding — ask us for details before production cutover.
Contact
- Contact form — scoping, architecture, migrations
- Azxa app — endpoints, billing, node status
- Telegram support
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 undersized shared gateways.