In development

QuroPanel is under active development. Follow the roadmap and join the first public testing group.

View roadmap Development updates
QuroPanel
Follow development
Platform overviewAll featuresIntegrationsQuroAdminQuroResellerQuroControlQuroCommerceQuroDeployQuroShieldQuroSupportNative appsQuroDeskQuroCLI
Hosting providersResellersAgenciesDevelopersWordPress hostingApplication hostingMigrating inCompare panels
Why open sourceLicenceContributeRoadmapSecurity overviewArchitectureResponsible disclosureRelease signing
Download and installSystem requirementsDocumentationMigration guideDevelopment updatesChangelogCommunityBrand and press
Pricing
Follow development

Server and fleet administration

See the server before it becomes a problem.

Manage servers, services, accounts and clusters without mixing root tools into the customer panel.

See the roadmapAll features
Fleet and cluster viewAccounts and packagesServices, network and DNS

Illustration of the QuroAdmin interface, drawn from the interface specification. Real screenshots replace this once the software is built.

Who it is for

Platform owners, server administrators and NOC staff

Server overview

  • Load, CPU, memory, swap, disk and inode use
  • Service status, failed services and restart history
  • Network throughput and active connections
  • RAID and SMART health where the hardware reports it
  • Pending updates and reboot-required state

Account functions

  • Create, modify, suspend, unsuspend and terminate accounts
  • Change package, owner, primary domain or username
  • Login as customer, with the original actor kept in the audit log
  • Bulk operations and account notes
  • Disk, bandwidth and resource limits per account

Services and runtimes

  • Nginx, Apache compatibility mode and reverse proxy
  • PHP-FPM pools and a PHP version per domain
  • Node.js, Python, Ruby, Go and Java runtimes
  • MariaDB, MySQL, PostgreSQL and Redis
  • Config validation before every reload, never after

Fleet and clusters

  • Node roles: web, app, mail, DNS, database, cache, backup
  • Drain, cordon and maintenance mode
  • Capacity planning and workload placement
  • Rolling and canary updates with rollback

Boundaries

What it deliberately will not do

Every one of these is a design decision, not a missing feature.

  • Root-level system actions never run in the web process. They are signed jobs handed to the QuroAgent over mTLS.
  • There is no generic run-any-command endpoint, by design.
  • Destructive operations require step-up authentication.

Other workspaces

QuroReseller

Reseller and master reseller management

QuroControl

Customer hosting control panel

QuroCommerce

Billing, orders, domains and provisioning

QuroDeploy

Git deployment, applications and WordPress

QuroShield

Security, monitoring and incident response

QuroSupport

Tickets, knowledgebase and operations

Follow the build

The roadmap shows what is specified, what is being built and what is still only planned.

View the roadmap

Contribute

Drivers, integrations, translations and documentation are all places to start.

How to contribute

Report a security issue

Responsible disclosure, with a stated response commitment.

Disclosure policy