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

Billing, orders, domains and provisioning

Sell a service once. Let the platform handle the routine work after that.

Handle products, orders, recurring billing, domains, provisioning and customer accounts in the same resource model.

See the roadmapAll features
Orders through to provisioningRecurring billing and ledgerRegistrar and gateway automation

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

Who it is for

Hosting providers, billing staff and sales teams

Catalog and orders

  • Products, plan variants and configurable options
  • Domain search, transfer or use-an-existing-domain at checkout
  • Coupons, tax, multi-currency and terms snapshots
  • Idempotent checkout with duplicate-payment prevention

Billing

  • Invoices, credit notes, refunds and partial payments
  • Wallet balance, proration and upgrade credits
  • Dunning ladder, grace periods and late fees
  • A transaction ledger, not a single invoice table

Domains

  • Register, transfer, renew and auto-renew
  • Multiple registrar accounts with TLD-based routing
  • Auth codes, WHOIS privacy, DNSSEC and glue records
  • Registrar inventory reconciliation

Provisioning

  • One queueing path from paid order to working service
  • Drivers for QuroPanel, cPanel/WHM, DirectAdmin, Plesk and more
  • Desired-state reconciliation that reports configuration drift
  • Every action queued, idempotent, retriable and audited

Boundaries

What it deliberately will not do

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

  • QuroCommerce never processes card data itself. Payment gateways are plugins, and no gateway credential ships in the core.
  • The billing system never writes directly to a server table. It goes through the service record and the provisioning driver.
  • Usage-based billing aggregates at the end of a period rather than charging per event.

Other workspaces

QuroAdmin

Server and fleet administration

QuroReseller

Reseller and master reseller management

QuroControl

Customer hosting control panel

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