Skip to content
Logo: WECORE
Register / Login
QuFabric
In deployment talks

Quantum simulation, on the cloud you already run.

A self-hosted research platform for quantum circuits, many-body physics, open quantum systems, and quantum chemistry. QuFabric assembles mature open-source engines on cloud capacity you already operate: prototype in notebooks, submit Jobs, and keep every input and result inside your boundary.
Mature open-source engines
Batch Jobs and arrays
Notebook-first workflow
Data-resident by design
qsim is a module of the WECORE panel, running on the cloud capacity you already operate.
7
Open-source simulation engines
3
Research lanes
Self-hosted
Runs on your own cloud
Jobs
Reproducible, tracked runs
Workflow

Everything a quantum researcher needs, without leaving your cloud.

QuFabric brings projects, environments, Jobs, and results into one governed, self-hosted workspace.
01

Create a project

Group notebooks, datasets, circuits, Hamiltonians, tags, quotas, and collaborators under one durable research workspace.

02

Choose an environment

Start from curated environments for Cirq + qsim, quimb + cotengra, TeNPy, QuTiP, PySCF, and NetKet.

03

Run interactively or submit Jobs

Prototype in Jupyter, then dispatch the same code as queued Jobs, arrays, or campaign sweeps.

04

Track reproducible results

Store engine versions, resources, input files, result schemas, logs, costs, and run history with every Job.

Research lanes

Curated for the way quantum teams work.

Each lane gets templates, packages, example notebooks, and resource presets tuned to the science.
Circuits

Quantum Algorithmist

Gate-based circuit simulation with Cirq and the qsim statevector engine: amplitudes, sampling, expectation values, and parameter sweeps that fan out as parallel Jobs.

Cirq qsim (qsimcirq)
Tensor networks + dynamics

Many-Body Physicist

DMRG ground states and TEBD/TDVP time evolution with TeNPy, tensor-network contraction with quimb + cotengra, neural-network quantum states with NetKet, and open-system dynamics with QuTiP.

TeNPy quimb cotengra NetKet QuTiP
Molecules

Quantum Chemist

Mean-field / Hartree-Fock chemistry with PySCF on CPU, with optional GPU acceleration through gpu4pyscf under your own NVIDIA license.

PySCF gpu4pyscf (optional)
Platform

A thin control plane over proven open-source engines.

QuFabric is not another simulator. It is the governed product layer of the WECORE panel that assembles mature engines on the cloud capacity you already operate.
qsim-control self-hosted
project: spin-chain-dynamics
engine: TeNPy · TEBD
queue: batch
items: 64 Jobs
status: RUNNING
result: observables + logs

Curated environments

An environment catalog with subject facets, kernel registration, clone-from-curated workflows, and health checks.

Jobs, not raw run IDs

Stable project-scoped Job IDs, status history, cancellation, retries, quota depletion states, and partial-result recovery.

Campaigns and batch fan-out

Parameter sweeps and circuit batches fan out as arrays while staying visible as a single campaign.

Result hub

Normalized counts, statevector, expectation, and artifact outputs with schema versions, logs, metrics, and exportable handles.

Quota preflight

Estimate compute time, memory, storage, and wallet impact before a Job queues.

Self-hosted sovereignty

Run on the cloud capacity you already operate; keep sensitive circuits, chemistry inputs, and results inside your boundary.

Engines

Mature research engines, one governed workspace.

The open-source engines research groups already trust, assembled into one governed workspace on your cloud.

Circuit simulation

Cirq + qsim Gate-based quantum circuit simulation with statevector amplitudes, via qsimcirq.

Tensor networks & many-body

quimb + cotengra Tensor-network state simulation with optimized contraction planning.
TeNPy Matrix-product-state methods: DMRG for ground states, TEBD and TDVP for time evolution.
NetKet Neural-network quantum states and variational Monte Carlo.

Open systems & chemistry

QuTiP Open quantum systems: Lindblad master equation, Monte-Carlo trajectories, and Bloch-Redfield dynamics.
PySCF Quantum chemistry: mean-field / Hartree-Fock methods on CPU.

Optional GPU acceleration

cuTensorNet GPU tensor-network contraction.
gpu4pyscf GPU acceleration for PySCF chemistry.

GPU engines are optional and bring-your-own-license: you provide licensed NVIDIA cuQuantum/CUDA software and your own GPU capacity. WECORE does not bundle or resell proprietary GPU software.

Why WECORE Cloud

Cloud-like workflow, self-hosted execution.

Dimension
Hosted quantum clouds
QuFabric qsim
Deployment
Vendor SaaS account
The cloud capacity you already operate
Data residency
Inputs and results leave your institution
Projects, Jobs, and artifacts stay on your storage
Simulation control
Fixed provider images and credit meters
Curated environments you can clone and reproduce
Scaling model
Provider-specific queues
Interactive notebooks, Jobs, arrays, and campaign sweeps
Value
Access broker
Governed product layer over infrastructure you own
FAQ

Quantum simulation questions, answered

What QuFabric is, what it is not, and how it fits your research workflow

No. QuFabric is a quantum simulation platform: mature open-source engines running on the classical capacity of your own cloud. WECORE does not provide quantum hardware, QPUs, or supercomputers, and nothing on this page runs on real qubits.

Cirq with the qsim statevector engine, quimb with cotengra for tensor networks, TeNPy for DMRG and TEBD/TDVP, QuTiP for open quantum systems, PySCF for quantum chemistry, and NetKet for neural-network quantum states — plus optional GPU paths through cuTensorNet and gpu4pyscf.

No. The engines are CPU-first and run on your existing cloud capacity. cuTensorNet and gpu4pyscf add optional GPU acceleration on a bring-your-own-license basis: you supply licensed NVIDIA software and GPU capacity. WECORE does not bundle or resell proprietary GPU software.

Hosted services run your work on their infrastructure, under their account and credit model. QuFabric brings the same workspace pattern — projects, environments, Jobs, and results — to capacity you operate, so circuits, chemistry inputs, and results never leave your boundary.

Yes. The path is notebook-first: prototype in JupyterLab, then submit the same environment as Jobs or campaigns.

Every Job captures project metadata, input artifacts, engine versions, the selected environment, the resource request, result schemas, logs, timing, and quota impact.

QuFabric

Turn the cloud you already run into a quantum simulation lab.

QuFabric is for research teams that want a modern simulation workflow without sending sensitive circuits, chemistry inputs, or results to someone else's cloud.