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

Git deployment, applications and WordPress

Connect a repository, set the environment and ship.

Build and deploy Laravel, PHP, Node.js, Python, Vue, Nuxt, React and static applications.

See the roadmapAll features
Git-based deploymentPreview environmentsWordPress toolkit

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

Who it is for

Developers, agencies and anyone deploying from a repository

Deployment

  • GitHub, GitLab and Bitbucket, or a plain SSH repository
  • Branch environments and preview deployments per commit
  • Zero-downtime release with the previous one kept for rollback
  • Deployment approvals before anything reaches production

Build

  • Framework and package-manager detection
  • Locked-dependency installs in an isolated workspace
  • Secret and dependency scanning before the release goes live
  • Build logs, cache control and failed-build diagnosis

Runtime

  • Node, Python, PHP, Go, Java and static sites
  • Workers, queues, scheduled jobs and WebSockets
  • Health checks that gate the upstream switch
  • Rootless containers where isolation matters

WordPress

  • Install, import, clone and stage
  • Transactional updates: snapshot, update, smoke test, roll back
  • Core checksum verification and vulnerability notices
  • Object cache, page cache and scheduled backups

Boundaries

What it deliberately will not do

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

  • AI-generated and imported code is treated as untrusted: it is scanned before it is built, and built before it is served.
  • Updates are transactional. A failed smoke test rolls the site back rather than leaving it broken.
  • Production auto-sync from a local folder is off by default.

Other workspaces

QuroAdmin

Server and fleet administration

QuroReseller

Reseller and master reseller management

QuroControl

Customer hosting control panel

QuroCommerce

Billing, orders, domains and provisioning

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