Skip to main content

Quantum Computing Qiskit Connector For Quantum Backend Use In Realtime

Project description

qiskit-connector

Python Qiskit Connector Quality Check DOI Qiskit Connector Code Coverage Analysis Qiskit Connector Latest Release PyPI Downloads License Monthly Downloads

⚛️Quantum Computing Qiskit Connector For Quantum Backend Use In Realtime

The Qiskit Connector transforms how quantum developers connect to IBM Quantum backends by automating every step of the authentication, plan detection, and backend selection process. Instead of writing extensive boilerplate setup code for each project, developers can now seamlessly authenticate, dynamically detect whether they are using an Open or Paid plan, and instantly access the optimal backend QPUresource which is least-busy using a single intuitive keyword: backend. The connector intelligently manages quantum computing plan environment variables and Qiskit runtime service configuration for sticky reusability of QPU resources from the backend, allowing quantum developers to streamline connection workflows and immediately focus on building, testing, and scaling quantum applications.

By eliminating manual configurations and connection complexities, Qiskit Connector empowers developers to reduce onboarding time, minimize human error, and accelerate quantum solution delivery. The tool is especially valuable for production-grade quantum development where agility, repeatability, and secure backend access are critical. Whether working in research environments, building enterprise-grade quantum solutions, or designing novel quantum algorithms, developers can now concentrate on high-value tasks without being slowed down by infrastructure setup challenges.

This package performs the following:

  • Loads environment variables from config file (e.g. .env) to configure your IBM Quantum account plan and make the backend object available within your quantum application code for reuse in real-time.
  • Detects your active plan (Open, Standard, Premium, Dedicated) and sets up the correct channel/instance.
  • It has functions to save your account using its (qiskit_smart), to verify QPU resources using (qpu_verify, is_verified), and retrieve a ready-to-use backend using (connector()). Presents you with the least-busy backend to run your quantum application code in realtime instead of you using simulators.
🐍 Software built and maintained by Dr. Jeffrey Chijioke-Uche, IBM Quantum Ambassador & Research Scientist.

📋 Built-in functions

These functions are available after you import the module:

from qiskit_connector import (
    connector,
    plan_type
)
  • connector()
    Primary Integration Point: Seamlessly initializes your IBM Quantum account, selects the optimal QPU (or the first available device for open/paid plans), and emits a clear diagnostics summary. It returns a fully configured backend object that you can immediately pass to Qiskit’s sampler, estimator, transpiler, or any circuit execution API—so you can focus on your quantum workflows rather than connection boilerplate.

  • plan_type()
    Subscription Plan Resolver: Automatically evaluates your environment configuration (via .env or system variables) to identify whether you’re operating under the Open Plan or a Paid Plan. This guarantees that your code consistently targets the correct IBM Quantum service tier, eliminating manual plan management and minimizing configuration drift.


🔧 Installation

It is recommended that you use pip for installation - a common best practice.
pip install qiskit-connector

This will also pull in functionalities powered by Qiskit SDK:

  • qiskit>=2.0.0

and any other Qiskit dependencies. (Qiskit 1.x is not supported).


🗂️ Variable Setup

🔐 Security Practices: Do not check-in to version control any environment variable config file or any variable setup file. The best security practice is to add it to your .gitignore or to accessible vault. During local development, create a file named .env at your project root and ensure it is named on your .gitignore. The connector will automatically load it. Use the template below as the content of your .env file or variable setup config file. Copy and paste it then supply the values.

# General Purpose:                                            (Required)
#--------------------------------------------------------------------------------------
IQP_API_TOKEN="<PROVIDE_YOUR_API_TOKEN>"  


# Channels:                                                   (Required)
#--------------------------------------------------------------------------------------
OPEN_PLAN_CHANNEL="<PROVIDE_YOUR_CHANNEL>"  
PAID_PLAN_CHANNEL="<PROVIDE PAID PLAN CHANNEL>"  


# API Url:                                                    (Optional)
#--------------------------------------------------------------------------------------
IQP_API_URL=<PROVIDE_YOUR_API_URL>  
IQP_RUNTIME_API_URL=<PROVIDE_YOUR_RUNTIME_API_URL>  


# Quantum Url:                                                (Optional)
# The API URL. Defaults to https://cloud.ibm.com (when channel=ibm_cloud) 
# The API URL:Default to:  https://auth.quantum.ibm.com/api (when channel=ibm_quantum)"
#---------------------------------------------------------------------------------------
CLOUD_API_URL="<PROVIDE_YOUR_CLOUD_API_URL>" 
QUANTUM_API_URL="<PROVIDE_YOUR_QUANTUM_API_URL>"  


# Instance:                                                  (Required)
#---------------------------------------------------------------------------------------
OPEN_PLAN_INSTANCE="<PROVIDE_YOUR_OPEN_PLAN_INSTANCE>"  
PAID_PLAN_INSTANCE="<PROVIDE_YOUR_PAID_PLAN_INSTANCE>"  


# Default (Open plan) - free                                   
#---------------------------------------------------------------------------------------
OPEN_PLAN_NAME="open"


# Optional (Upgrade) - Standard                               
#----------------------------------------------------------------------------------------
STANDARD_PLAN_NAME="standard"


# Optional (Upgrade) - Premium                                
#----------------------------------------------------------------------------------------
PREMIUM_PLAN_NAME="premium"


# Optional (Upgrade) - Dedicated                               
#----------------------------------------------------------------------------------------
DEDICATED_PLAN_NAME="dedicated"


# Switch "on" only one plan:                                       (Required)
#----------------------------------------------------------------------------------------
OPEN_PLAN="on"        # [Default & switched on]  
STANDARD_PLAN="off"     
PREMIUM_PLAN="off"      
DEDICATED_PLAN="off"    

⚠️ Only one of OPEN_PLAN, STANDARD_PLAN, PREMIUM_PLAN, or DEDICATED_PLAN may be set to "on" at a time.


📖 Usage

Open Plan and Paid Plan
from qiskit_connector import connector, plan_type
from qiskit_ibm_runtime import SamplerV2 as Sampler, Session

# QPU execution mode by plan: Use of 'backend' object.
current = plan_type()
backend = connector()

if current == "Open Plan":  # session not supported
    sampler = Sampler(mode=backend)
    print("Your Plan",current)
    print("Least Busy QPU:", backend.name)
    if isinstance(backend, IBMBackend):
        print("This is a real & live QPU device")
    else:
        print("This is a simulator")
    print(f"\n")
elif current == "Paid Plan":  # supports session
    with Session(backend=backend.name) as session:
        sampler = Sampler(mode=session)
        print("Your Plan",current)
        print("Least Busy QPU:", backend.name)
        if isinstance(backend, IBMBackend):
            print("This is a real & live QPU device")
        else:
            print("This is a simulator")
        print(f"\n")
else:
    raise ValueError(f"Unknown plan type: {current}")

# --- do other things below with backend, quantum circuit, sampler & transpilation ------

Output Sample

 ⚛️ Connecting (Open Plan) to least-busy QPU....
 --------------------------------------------------------------------------------
 ⚛️ Connected [Open Plan] -> Realtime Least Busy QPU:: [ibm_torino]
  - ibm_brisbane
  - ibm_sherbrooke
  - ibm_torino


🖥️Least Busy QPU Now: ibm_torino
🖥️Qubit Version:   2
🖥️Qubits Count:   133
🖥️Backend [ibm_torino] ready for use: Yes
================================================================================

Your Plan:       Open Plan
Least Busy QPU:  ibm_torino
This is a real & live QPU device


#-------- remaining code below ------

📜 Citation

Qiskit Connector software invention was inspired by IBM Research on Quantum Computing Qiskit Software, which led the authoring, design, development of Qiskit Connector based on the persistent research studies and tests carried out by Dr. Jeffrey Chijioke-Uche(IBM Quantum Ambassador & Research Scientist) in the lab. This software is expected to continue to metamorphose with the help and work of existing quantum computing academic scholarly & peer reviewed research at different levels in the Information Technology industry. If you use Qiskit for Quantum computing, please cite this software as per the provided BibTeX file. Also, citation is available in the following formats: Harvard, APA, MLA, IEEE, Chicago, & Vancouver


📜 Software Author

Dr. Jeffrey Chijioke-Uche
IBM Computer Scientist
IBM Quantum Ambassador & Research Scientist
IEEE Senior Member (Computational Intelligence)


📜 Copyright

Qiskit Connector is proprietary software developed by Dr. Jeffrey Chijioke-Uche © 2025 for enhancing development, usability,and workflows in IBM Quantum Computing by customers and global users. This software is protected under copyright laws and applicable intellectual property statutes. Unauthorized reproduction, distribution, or derivative use of the software in part or whole is strictly prohibited without express written permission from the author. This software may be used under the terms outlined in the accompanying licenses by (Apache 2.0 and Creative Commons Attribution 4.0 international). Use of this software signifies your agreement to comply with the license terms and to attribute the original author when incorporating the package into your work or systems. For other question(s), please contact the maintainer directly through the official project repository or email channel provided on PyPI. All Rights Reserved.


📜 Acknowledgment

The development of the Qiskit Connector has been made possible through the support, inspiration, and technical contributions of several leading institutions and communities. The author would like to express deep gratitude to IBM Research & IBM Quantum Ambassadors Group for their pioneering efforts in democratizing quantum computing and providing the infrastructure and collaborative ecosystem that fostered the development of this tool. Their continued support has significantly accelerated progress in real-world quantum application development.

Additional appreciation is extended to the IEEE Computational Intelligence Society for their thought leadership in intelligent systems, and to the Harvard Program for Research in Science and Engineering for its role in shaping early research directions. The author also acknowledges Walden University Research for providing a strong academic and methodological foundation throughout the software development lifecycle. These institutions have collectively influenced the innovation and rigor reflected in this project.


📜 Licenses

This software uses these licenses for distribution:

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

qiskit_connector-2.2.1.tar.gz (25.1 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

qiskit_connector-2.2.1-py3-none-any.whl (17.4 kB view details)

Uploaded Python 3

File details

Details for the file qiskit_connector-2.2.1.tar.gz.

File metadata

  • Download URL: qiskit_connector-2.2.1.tar.gz
  • Upload date:
  • Size: 25.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for qiskit_connector-2.2.1.tar.gz
Algorithm Hash digest
SHA256 af5a7ba1939c0eab448008596e3ad198d3a27d78f441fc6566fe72201e9bbbef
MD5 2a7c5dceb9f255d3b6f9392ac1ca52cf
BLAKE2b-256 b2169adb6523219f8c3ae39114884cd3fd877529a4e3189cd850de9a6970414e

See more details on using hashes here.

Provenance

The following attestation bundles were made for qiskit_connector-2.2.1.tar.gz:

Publisher: workflow.yml on schijioke-uche/qiskit-connector

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file qiskit_connector-2.2.1-py3-none-any.whl.

File metadata

File hashes

Hashes for qiskit_connector-2.2.1-py3-none-any.whl
Algorithm Hash digest
SHA256 fdc0b6b1c1dbf53c0cf30e15e93643faaa7d310ab72a87decd1a891a0c02039b
MD5 5e5b8e94fc8d709f6c2b935c12d7798e
BLAKE2b-256 88bd5bf1cfbd4c0b18f0fb29b917fa2f90530b6a2b82d466f4b02d678b345f55

See more details on using hashes here.

Provenance

The following attestation bundles were made for qiskit_connector-2.2.1-py3-none-any.whl:

Publisher: workflow.yml on schijioke-uche/qiskit-connector

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page