Solver Workbench

DocsLog inBook a demo

Solver Workbench

From code to running solver, without the plumbing

Start from a template or connect your repository. The platform builds, validates and runs your solver across providers.

Book a demoRead the docs
Repository page of a connected solver with its builds history and the entrypoint check (qcentroid.py, run() and signature) passed
  • Telefónica
  • Mahou San Miguel
  • MasOrange
  • GSMA
  • Moeve
  • Moody's
  • Sabadell BStartup
  • BiQain
  • BackFund
  • QAI Ventures
  • CDL
  • Telefónica
  • Mahou San Miguel
  • MasOrange
  • GSMA
  • Moeve
  • Moody's
  • Sabadell BStartup
  • BiQain
  • BackFund
  • QAI Ventures
  • CDL

Start fast

Ready-made templates for each provider and SDK.

Keep your workflow

Connect Git; the platform builds and runs your code.

Fail early, not late

Code checked before the build, not after a failed job.

Features

Everything a solver needs, from first commit to catalog

Four tools to take an algorithm from code to a solver others can run: start from a template, connect your repository, validate the build and publish it.

Solver Templates & Runtime

Start from a ready-made template for your provider and SDK. A versioned runner handles libraries and hardware calls.

  • Templates per provider and SDK
  • One entry point: a single run() function
  • Versioned runtime for reproducible runs

Why it mattersDevelopers write the algorithm, not the integration code.

Add a new solver: choose the implementation method (code repository, container repository, external worker or external service)
Add a new solver: choose the implementation method (code repository, container repository, external worker or external service)

Repository-Connected Solvers

Connect a Git repository and the platform builds and runs your solver. Push a change, rebuild, run.

  • Connect your Git repository in a few clicks
  • Automatic build from your code and dependencies
  • Rebuild after every change

Why it mattersKeep your usual tools and version control. No copying code into a web form.

Connected Git repositories with their status, number of solvers and the time of the last build
Connected Git repositories with their status, number of solvers and the time of the last build

Build-Time Code Validation

The solver's code contract is checked before the build, so errors show up in seconds, not after a failed job.

  • Entry point and signature checked before build
  • Clear errors that point to the fix
  • No compute wasted on broken builds

Why it mattersFailed jobs on real hardware cost time and money. Catch errors before they run.

Repository page of a connected solver with its builds history and the entrypoint check (qcentroid.py, run() and signature) passed
Repository page of a connected solver with its builds history and the entrypoint check (qcentroid.py, run() and signature) passed

Solver Catalog

Publish solvers as documented, branded entries others can find and run, with control over who sees them.

  • Documentation shipped with every solver
  • Branding for partner and vendor solvers
  • Visibility: private, organisation or public

Why it mattersOne team's work becomes a reusable asset across your organisation or ecosystem.

Organisation solver catalogue with type, lifecycle stage, use case and estimated cost of each solver
Organisation solver catalogue with type, lifecycle stage, use case and estimated cost of each solver

Solver Workbench

Put your algorithms to work.

Template, repository, validated build, catalog.

Book a demoRequest early access

Read the docs →

QCentroid platform home: your quantum journey with the tools of each phase