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

Reseller and master reseller management

Give resellers room to grow without giving away the server.

Give resellers control over customers, packages and branding while keeping provider limits intact.

See the roadmapAll features
Customer and package controlWhite-label brandingParent limits that cannot be exceeded

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

Who it is for

Master resellers, resellers and their staff

Customer management

  • Create, suspend, unsuspend and transfer customers
  • Change package, reset password, schedule termination
  • Customer 360: services, domains, invoices, tickets, usage
  • Login as customer with a fully audited session

Packages and feature sets

  • Resource limits: disk, inodes, bandwidth, CPU, RAM, I/O
  • Feature sets kept separate from resource packages
  • Add-ons, upgrade and downgrade paths
  • Overselling policy set by the provider, not the reseller

White-label

  • Logo, favicon, colours and login screen
  • Customer portal domain and support links
  • Branded email templates and invoices
  • Branded native apps, built from one codebase

Hierarchy

  • Provider → master reseller → reseller → customer
  • Child resellers within the parent's allocation
  • Ownership tree, usage reports and audit history

Boundaries

What it deliberately will not do

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

  • A reseller cannot change host server settings, configure daemons or alter the global firewall.
  • A reseller cannot see another reseller's data, or allocate resources beyond what the parent granted.
  • Nesting is capped at provider → master reseller → reseller → customer. Unlimited nesting is not supported on purpose.

Other workspaces

QuroAdmin

Server and fleet administration

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