☁ NexaCloud / NexaLink ⦿ The Next-Generation Minecraft Panel ✅ Velocity, Paper & Folia ⚡ Automation

☁ WHAT IS NEXACLOUD?

NexaCloud is a Minecraft-native infrastructure platform built to manage more than individual server processes.

Instead of treating every Minecraft server as an isolated machine, NexaCloud is designed around your entire network.

• Manage proxies and backend servers
  
  
• Connect multiple Linux nodes
  
  
• Monitor Minecraft and infrastructure health
  
  
• Control instances from one dashboard
  
  
• Organize servers into networks and services
  
  
• Automate repetitive infrastructure tasks
  
  
• Prepare your network for scaling, deployments and recovery
  

NexaCloud is not a generic VPS panel adapted to Minecraft.

It is being built specifically around the way modern Minecraft networks actually work.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

WHAT IS NEXALINK?

NexaLink is the Minecraft-side integration between your servers and NexaCloud.

Install NexaLink on supported Minecraft platforms to provide NexaCloud with information that a traditional hosting panel cannot understand.

Supported targets:

• Velocity
  
  
• Paper
  
  
• Folia
  

NexaLink can provide Minecraft-aware information such as:

• Server availability
  
  
• Player activity
  
  
• TPS
  
  
• MSPT
  
  
• Server readiness
  
  
• Lifecycle state
  
  
• Heartbeats
  
  
• Minecraft-specific health information
  

This allows NexaCloud to understand the difference between:

“The Java process is running.”

and:

“The Minecraft server is actually ready and healthy.”

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

⚙ NEXAAGENT

NexaAgent connects your Linux infrastructure to NexaCloud.

It runs on your VPS or dedicated server and provides the infrastructure layer required by NexaCloud.

NexaAgent is designed to handle:

• CPU monitoring
  
  
• RAM monitoring
  
  
• Disk monitoring
  
  
• Network metrics
  
  
• Docker workloads
  
  
• Instance lifecycle
  
  
• Logs and console streams
  
  
• Health reporting
  
  
• Backup execution
  
  
• Resource reporting
  
  
• Secure communication with NexaCloud
  

NexaLink understands Minecraft.

NexaAgent understands the machine.

NexaCloud connects everything together.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

BUILT FOR NETWORKS

Traditional panels usually focus on individual servers.

NexaCloud focuses on the network itself.

Instead of thinking only in terms of:

• Server 01
  
  
• Server 02
  
  
• Server 03
  

NexaCloud is designed around structures such as:

Network

• Velocity
  
  
• Lobby
  
  • Lobby-01
    
    
  • Lobby-02
    
• Survival
  
  
• SkyBlock
  
  
• Events
  
  
• Development
  

This makes larger infrastructures easier to understand, manage and automate.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

MINECRAFT-AWARE MONITORING

A running process does not always mean a healthy Minecraft server.

NexaCloud is designed to combine traditional infrastructure metrics with Minecraft-specific information.

Infrastructure monitoring can include:

• CPU
  
  
• RAM
  
  
• Disk
  
  
• Network
  
  
• Container status
  
  
• Uptime
  

Minecraft monitoring can include:

• TPS
  
  
• MSPT
  
  
• Players
  
  
• Server heartbeat
  
  
• Readiness
  
  
• Lifecycle state
  
  
• Availability
  

The goal is to provide a much clearer view of what is actually happening across your network.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ONE CONTROL PLANE

NexaCloud is designed to bring your infrastructure together in one place.

Manage:

• Velocity
  
  
• Paper
  
  
• Folia
  
  
• Linux nodes
  
  
• Docker workloads
  
  
• Minecraft instances
  
  
• Monitoring
  
  
• Logs
  
  
• Networks
  
  
• Backups
  
  
• Deployments
  
  
• Automation
  

One network. One control plane.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━


━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

✅ CURRENTLY AVAILABLE

The following features are part of the current NexaCloud ecosystem and are intended to be usable today.

Account & Platform

• NexaCloud accounts
  
  
• NexaCloud dashboard
  
  
• Network organization
  
  
• Node organization
  
  
• Secure authentication
  
  
• Basic account management
  

NexaLink

• Velocity integration
  
  
• Paper integration
  
  
• Folia integration
  
  
• Minecraft server connection
  
  
• Player information
  
  
• Server status reporting
  
  
• Basic Minecraft health information
  

NexaAgent

• Linux node registration
  
  
• Secure node connection
  
  
• CPU monitoring
  
  
• RAM monitoring
  
  
• Disk monitoring
  
  
• Basic infrastructure metrics
  
  
• Node status
  
  
• Resource reporting
  

Instance Management

• Minecraft instance detection
  
  
• Basic instance overview
  
  
• Start
  
  
• Stop
  
  
• Restart
  
  
• Server state information
  
  
• Basic logs / console integration
  

Infrastructure

• Multiple node support
  
  
• Linux infrastructure connection
  
  
• Docker-oriented architecture
  
  
• Node health information
  

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

IN DEVELOPMENT / BETA

These systems are currently being developed, integrated or stabilized.

They may be partially available depending on the NexaCloud version.

Advanced Monitoring

• Extended Minecraft health checks
  
  
• Advanced metrics
  
  
• Better TPS / MSPT monitoring
  
  
• Historical metrics
  
  
• Nexa Pulse health states
  

Service Management

• Services
  
  
• Fleets
  
  
• Grouped instance management
  
  
• Service-level operations
  

Dynamic Networking

• Dynamic Velocity backend registration
  
  
• Automatic service discovery
  
  
• Better backend lifecycle synchronization
  

Deployment System

• Plugin deployment
  
  
• Configuration deployment
  
  
• Deployment history
  
  
• Rolling deployments
  

Example:

Upload EssentialsX
→ Select Lobby
→ Deploy
→ Restart safely

Blueprints

• Reusable server templates
  
  
• Software selection
  
  
• Java configuration
  
  
• RAM configuration
  
  
• Plugins
  
  
• Startup configuration
  
  
• Instance creation from blueprint
  

Backups

• Manual backups
  
  
• Scheduled backups
  
  
• Backup retention
  
  
• Restore workflows
  
  
• External backup storage
  

Operations

• Drain mode
  
  
• Rolling restarts
  
  
• Maintenance workflows
  
  
• Better instance lifecycle management
  

Security & Administration

• Advanced permissions
  
  
• RBAC
  
  
• Audit logs
  
  
• Security events
  
  
• Improved node identity management
  

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

PLANNED

These features are part of the long-term NexaCloud vision.

They should not currently be considered production-ready or publicly available unless announced separately.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

⚡ AUTOSCALING

NexaCloud will be able to dynamically start or stop instances according to network demand.

Example:

Lobby reaches capacity
→ NexaCloud starts Lobby-03
→ Health check passes
→ Server becomes available

Possible scaling signals:

• Player count
  
  
• TPS
  
  
• MSPT
  
  
• CPU
  
  
• RAM
  
  
• Capacity
  
  
• Service health
  

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

WAKE-ON-JOIN

Idle servers will be able to sleep instead of consuming resources permanently.

Example:

Player requests Creative
→ Server wakes
→ NexaCloud waits for readiness
→ Player is transferred automatically

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

NEXALIMBO

A lightweight waiting environment designed for:

• Server startup
  
  
• Restart
  
  
• Maintenance
  
  
• Migration
  
  
• Recovery
  

Players will be able to wait safely while NexaCloud prepares the requested backend.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

SMART ROUTING

Future routing will be able to consider more than player count.

Possible signals:

• Player count
  
  
• TPS
  
  
• MSPT
  
  
• CPU
  
  
• RAM
  
  
• Server health
  
  
• Capacity
  
  
• Maintenance state
  
  
• Availability
  

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

SELF-HEALING

NexaCloud is designed to eventually detect problems such as:

• Crashed processes
  
  
• Frozen Minecraft servers
  
  
• Missing heartbeats
  
  
• Failed health checks
  
  
• Repeated crash loops
  

Possible recovery:

Failure detected
→ Instance isolated
→ Recovery workflow
→ Restart or replacement
→ Health check
→ Traffic restored

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ROLLING OPERATIONS

The goal is to perform operations across a fleet without taking everything offline at once.

Example:

Lobby-01
→ Drain
→ Restart
→ Health check
→ Ready

Lobby-02
→ Drain
→ Restart
→ Health check
→ Ready

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

CANARY DEPLOYMENTS

Future deployment workflows will allow updates to be tested on a small part of the infrastructure first.

Example:

New EssentialsX version
→ Deploy to Lobby-03
→ Monitor
→ Healthy
→ Continue rollout

If something goes wrong:

→ Rollback

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

NEXA SHIFT

Nexa Shift is a planned replacement-based deployment system.

Instead of modifying a production instance directly:

Lobby-02
→ Build Lobby-02-next
→ Apply blueprint
→ Apply plugins
→ Start
→ Health check
→ Drain old instance
→ Activate replacement

The goal is safer and more predictable infrastructure changes.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

NEXA AUTOPILOT

Planned automation modes:

• OFF
  
  
• SUGGEST
  
  
• SAFE
  
  
• FULL
  

Nexa Autopilot will eventually be able to assist with:

• Recovery
  
  
• Scaling
  
  
• Rebalancing
  
  
• Draining
  
  
• Backups
  
  
• Cleanup
  
  
• Instance replacement
  
  
• Capacity management
  

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

☁ NEXAGRID — PLANNED NATIVE HOSTING

NexaGrid is the planned infrastructure layer for NexaCloud.

Instead of buying a separate VPS for every Minecraft server, users will be able to purchase infrastructure capacity and distribute it however they want.

Example:

NexaGrid Performance 32

• 32 GB RAM
  
  
• 8 vCPU
  
  
• NVMe storage
  

Then allocate resources:

• Velocity — 1 GB
  
  
• Lobby — 3 GB
  
  
• Survival — 10 GB
  
  
• SkyBlock — 12 GB
  
  
• Development — 4 GB
  

You choose how your infrastructure is built.

NexaGrid is planned and is not currently part of the public production offering.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

BACKUP STORAGE — PLANNED

NexaCloud is also being designed to offer independent backup storage.

Planned backup destinations include:

• NexaCloud Backup Storage
  
  
• S3-compatible storage
  
  
• Cloudflare R2
  
  
• Backblaze B2
  
  
• MinIO
  
  
• SFTP
  

Potential backup types:

• Full instance
  
  
• Worlds
  
  
• Configurations
  
  
• Plugins
  
  
• Databases
  

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

SECURITY FIRST

NexaCloud is designed around the principle that the client-side components should never be the source of authority.

Security architecture includes or is being built around:

• Secure node enrollment
  
  
• Machine identities
  
  
• Encrypted communication
  
  
• Revocable node credentials
  
  
• Signed commands
  
  
• Server-side authorization
  
  
• Role-based access
  
  
• Audit logging
  
  
• Credential rotation
  

NexaAgent and NexaLink do not decide what an account is allowed to use.

NexaCloud Core remains the source of truth.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

OPEN CLIENT COMPONENTS

The NexaCloud ecosystem is designed with transparency in mind.

Public components include:

• NexaLink
  
  
• NexaAgent
  

The commercial NexaCloud control plane remains private.

This allows administrators to inspect the software running on their Minecraft servers and infrastructure while keeping sensitive cloud-side systems protected.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

SUPPORTED ENVIRONMENT

NexaCloud is being built primarily for:

• Velocity
  
  
• Paper
  
  
• Folia
  
  
• Linux
  
  
• Docker
  
  
• Modern Minecraft networks
  
  
• Multi-node infrastructures
  

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

NEXACLOUD ACCOUNT

A NexaCloud account is required to connect NexaLink and NexaAgent to the platform.

A free plan is intended to make NexaCloud accessible to smaller networks and development environments.

Paid plans unlock additional capacity and advanced functionality.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

HOW IT WORKS

1. Create your NexaCloud account

2. Connect your Linux infrastructure with NexaAgent

3. Install NexaLink on Velocity / Paper / Folia

4. Add your Minecraft network

5. Manage your infrastructure from NexaCloud

No need to treat every server as an unrelated machine anymore.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

WHY NEXACLOUD?

Managing a Minecraft network should not mean manually maintaining dozens of disconnected Java processes.

NexaCloud is being built around a different approach:

• Minecraft-aware
  
  
• Network-aware
  
  
• Infrastructure-aware
  
  
• Automation-ready
  
  
• Multi-node by design
  

Traditional panels manage servers.

NexaCloud is being built to manage Minecraft infrastructure.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

IMPORTANT DEVELOPMENT NOTICE

NexaCloud is under active development.

The roadmap shown above represents the direction of the project.

Features marked:

✅ AVAILABLE
are intended to be usable in the current public ecosystem.

IN DEVELOPMENT / BETA
may be incomplete, experimental or available only in certain builds.

PLANNED
describe future functionality and must not be considered currently available.

Always check the latest changelog and documentation for exact version compatibility.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━