diff --git a/tutorials/advanced_features/Backends for Sequence Execution.ipynb b/tutorials/advanced_features/Backends for Sequence Execution.ipynb
index 00170c733..8c9a5f9cc 100644
--- a/tutorials/advanced_features/Backends for Sequence Execution.ipynb	
+++ b/tutorials/advanced_features/Backends for Sequence Execution.ipynb	
@@ -431,6 +431,23 @@
    "source": [
     "The same could be done with the results from `EmuTNBackend` or even from `QPUBackend`, as they all share the same format."
    ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "## 6. Alternative user interfaces for using remote backends"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "Once you have created a Pulser sequence, you can also use specialized Python SDKs to send it for execution:\n",
+    "\n",
+    "- the [pasqal-cloud](https://github.com/pasqal-io/pasqal-cloud/) Python SDK, developed by PASQAL and used under-the-hood by Pulser's remote backends.\n",
+    "- Azure's Quantum Development Kit (QDK) which you can use by creating an [Azure Quantum workspace](https://learn.microsoft.com/en-gb/azure/quantum/provider-pasqal) directly integrated with PASQAL emulators and QPU."
+   ]
   }
  ],
  "metadata": {