[WIP] Add additional platform page for third-party vendor by can-gaa-hou · Pull Request #2072 · pytorch/pytorch.github.io

can-gaa-hou · 2026-05-09T09:30:56Z

Description

This PR adds a new page for users to search for guidelines for more PyTorch backends through the official website.

The new page will look like this:

Here is the page entrance: https://cosdt.github.io/get-started/additional-platform/

How it works

If a new backend would like to add to this page, then simply add a json file under the _ecosystem_platform/ directory. The gen_ecosystem_platform.py will automatically read the json file and re-generate the js file needed for rendering the page. Here is an example for the json file:

{
  "name": "NPU",
  "vendor": "Huawei",
  "documentation": "https://www.hiascend.com/document",
  "stable": {
    "linux": {
      "pip": {
        "python": {
          "CANN 8.0": "pip3 install torch torchvision --index-url https://download.pytorch.org/whl/npu/cann80",
          "CANN 9.0": "pip3 install torch torchvision --index-url https://download.pytorch.org/whl/npu/cann90"
        }
      }
    }
  },
  "preview": {
    "linux": {
      "pip": {
        "python": {
          "CANN 8.0": "pip3 install torch torchvision --pre --index-url https://download.pytorch.org/whl/nightly/npu/cann80",
          "CANN 9.0": "pip3 install torch torchvision --pre --index-url https://download.pytorch.org/whl/nightly/npu/cann90"
        }
      }
    }
  }
}

cc @fffrog

netlify · 2026-05-09T09:31:01Z

✅ Deploy Preview for pytorch-dot-org-preview ready!

Name	Link
🔨 Latest commit	`72924bf`
🔍 Latest deploy log	https://app.netlify.com/projects/pytorch-dot-org-preview/deploys/6a031e4d97b19b00086672db
😎 Deploy Preview	https://deploy-preview-2072--pytorch-dot-org-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

fffrog · 2026-05-09T10:29:36Z

@can-gaa-hou Great job, thank you.

fffrog · 2026-05-09T10:36:16Z

Hey @marco-s, sorry to bother you.

The PoC is ready—could you let us know if this provides enough detail for the WP integration? and the rendered version is here

dvrogozh

I am not sure where Intel XPU cmdline comes from as I don't see it being added in this PR, but it's incorrect as it directs to install deprecated intel-extension-for-pytorch. Intel XPU is a platform available in upstream pytorch and should be installed with:

pip3 install torch torchvision --index-url https://download.pytorch.org/whl/xpu

For the same reason, I think we need to clearly separate those platforms which are supported directly by pytorch team (such as CUDA, ROCm, XPU, Vulkan, etc.) and those which are available as pytorch extensions/plugins supported by 3rd parties. I suggest there should be 2 distinct sections on the page which clear separate these 2 group of platforms.

Also, I am not sure that current install selector matrix widget is the best approach we can take as it has potentially limited capacity and quickly becomes bloated with different buttons. A more straightforward and simple way can be considered. For example, having a simple table of content listing platforms one by one with the further links to the platform descriptions and instructions. For example:

PyTorch Platforms

CPU -> link
CUDA -> link
ROCm -> link
XPU -> link
Vulkan -> link
...

PyTorch Extensions

NPU (Huawei) -> link
...

can-gaa-hou · 2026-05-12T02:49:34Z

I am not sure where Intel XPU cmdline comes from as I don't see it being added in this PR, but it's incorrect as it directs to install deprecated intel-extension-for-pytorch.

Hi @dvrogozh, all the content shown on the page is fake. The purpose of this PR is to introduce the secondary page for PyTorch extension installation and to add the installation widget framework. The content in the widget will be added through JSON files (the format is shown in the description) by each vendor in the following PRs.

For the same reason, I think we need to clearly separate those platforms which are supported directly by pytorch team(such as CUDA, ROCm, XPU, Vulkan, etc.) and those which are available as pytorch extensions/plugins supported by 3rd parties.

This primary page will manage the platforms which are supported directly by pytorch team, and the secondary page will manage those pytorch extensions/plugins supported by 3rd parties.

Also, I am not sure that current install selector matrix widget is the best approach we can take as it has potentially limited capacity and quickly becomes bloated with different buttons.

The format inherits from the primary page. We can discuss more about it in the Slack channel and the Accelerator Working Group.

can-gaa-hou · 2026-05-12T15:06:37Z

Hi there, I have update the link: https://cosdt.github.io/get-started/additional-platform/

changing the name from ecosystem-platform --> additional-platform

albanD · 2026-05-12T15:21:49Z

@dvrogozh I don't think I agree on this. There should not be any distinction between in-core vs out-of-core backends from the end user perspective.
The code lives in-core or out-of-core only for technical reasons related to ease of development and maintenance.

We have many workstreams done and in flight working toward ensure the two can match and reach the same level of integration and stability.

albanD · 2026-05-12T15:23:29Z

  </div>
 </div>

+<div class="bg-light-grey">


I would suggest removing the light gray as it makes it look like a formatting bug with the background above.

Got it, thank you.

albanD · 2026-05-12T15:25:48Z

@@ -0,0 +1,115 @@
+<p>Select your compute platform and configuration to get the installation command. These platforms provide alternative hardware acceleration options beyond NVIDIA CUDA.</p>


Suggested change

<p>Select your compute platform and configuration to get the installation command. These platforms provide alternative hardware acceleration options beyond NVIDIA CUDA.</p>

<p>In the following selector, you can find compute platform and configuration supported by partners and community members. Select your preferences and run the install command provided.</p>

This is closer to the language of the main page and makes it clear what's the difference between the two.

I would also suggest adding a note in the selector for each platform with details on where to provide feedback and report issues (which github repo, which label to use there, etc).

@albanD , can you, please, suggest where Intel XPU should be placed - in the primary page or on this additional platforms page. I do argue that Intel XPU is in-tree backend and Intel provides the necessary infrastructure to the Pytorch team to validate, develop and support XPU backend. Effectively Intel Pytorch team is a part of the greater Pytorch team who makes Pytorch releases.

I would also suggest adding a note in the selector for each platform with details on where to provide feedback and report issues (which github repo, which label to use there, etc).

Besides that I think it's reasonable to add information on how to install drivers to make pytorch actually runnable on the specific hardware. This might be just a link to the platform documentation or a link to the pytorch side page with the details such as https://docs.pytorch.org/docs/2.11/notes/get_start_xpu.html.

I would also suggest adding a note in the selector for each platform with details on where to provide feedback and report issues (which github repo, which label to use there, etc).

@albanD Thank you for this valuable suggestion, I will copy that.

Besides that I think it's reasonable to add information on how to install drivers to make pytorch actually runnable on the specific hardware. This might be just a link to the platform documentation or a link to the pytorch side page with the details such as https://docs.pytorch.org/docs/2.11/notes/get_start_xpu.html.

Thank you@dvrogozh, yes, we will reserve a spot to display this info.

albanD · 2026-05-12T15:33:27Z

+<div class="row">
+  <div class="col-md-3 headings">
+    <div class="col-md-12 title-block">
+      <div class="option-text">PyTorch Build</div>


We might actually want to reshuffle this. To be platform-first?
As I don't expect all platform will support all types of build and OS.

Great point! We'll update the PR along those lines.

albanD · 2026-05-12T15:34:07Z

+      <div class="option-text">Package</div>
+    </div>
+    <div class="col-md-12 title-block">
+      <div class="option-text">Language</div>


I would suggest removing Package and Language tbh. libtorch + C++ is not really used and I don't think it is a good use of time for new bakends to focus on maintaining these.

Got it,we will copy that.

dvrogozh · 2026-05-12T16:00:47Z

There should not be any distinction between in-core vs out-of-core backends from the end user perspective. The code lives in-core or out-of-core only for technical reasons related to ease of development and maintenance.

If there are just technical reasons distinctions, then yes. However, if code resides in a separate github org, has distinct workflow processes set, stand alone ci coverage and maintenance, separate release process, etc., then there is clear distinction between in-core and such out-of-core backends.

dvrogozh · 2026-05-12T16:09:56Z

The content in the widget will be added through JSON files (the format is shown in the description) by each vendor in the following PRs.

@can-gaa-hou , where such JSON file is located for XPU? I could not actually find it in the repo. Unfortunately I don't understand where current version is pulling information for XPU from.

fffrog · 2026-05-13T04:41:11Z

@can-gaa-hou , where such JSON file is located for XPU? I could not actually find it in the repo. Unfortunately I don't understand where current version is pulling information for XPU from.

@dvrogozh, this PR is strictly focused on the infrastructure of the secondary page and does not include any specific accelerator data. The XPU and Ascend entries seen in the demo were generated in our local environment using local files; we intentionally excluded them from this PR to keep the focus on the framework.

fffrog · 2026-05-13T04:49:53Z

Hi @albanD, sorry for the ping again. We are drafting a comprehensive mockups that includes both the primary page updates and the creation of the secondary pages, fully aligned with the TAC consensus.

We will also incorporate some minor adjustments based on the discussions and suggestions from other vendors in the Accelerator WG. Once finalized, I’ll send it over to you for final feedback and confirmation. We expect to complete this in about three days. Thank you for your patience and support!

cc @can-gaa-hou

can-gaa-hou force-pushed the site branch from e0c876c to f39ec3d Compare May 11, 2026 02:18

dvrogozh reviewed May 11, 2026

View reviewed changes

can-gaa-hou changed the title ~~[WIP] Add ecosystem platform page for third-party vendor~~ [WIP] Add additional platform page for third-party vendor May 12, 2026

can-gaa-hou force-pushed the site branch from a9ba40e to 776fdcf Compare May 12, 2026 12:33

can-gaa-hou added 2 commits May 12, 2026 20:34

Add ecosystem platform page for third-party vendor

323f25f

Add additional platform quick start module and update related workflows

72924bf

can-gaa-hou force-pushed the site branch from 776fdcf to 72924bf Compare May 12, 2026 12:34

albanD reviewed May 12, 2026

View reviewed changes

		@@ -0,0 +1,115 @@
		<p>Select your compute platform and configuration to get the installation command. These platforms provide alternative hardware acceleration options beyond NVIDIA CUDA.</p>

	<p>Select your compute platform and configuration to get the installation command. These platforms provide alternative hardware acceleration options beyond NVIDIA CUDA.</p>
	<p>In the following selector, you can find compute platform and configuration supported by partners and community members. Select your preferences and run the install command provided.</p>

Conversation

can-gaa-hou commented May 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

How it works

Uh oh!

netlify Bot commented May 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for pytorch-dot-org-preview ready!

Uh oh!

fffrog commented May 9, 2026

Uh oh!

fffrog commented May 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dvrogozh left a comment

Choose a reason for hiding this comment

PyTorch Platforms

PyTorch Extensions

Uh oh!

can-gaa-hou commented May 12, 2026

Uh oh!

can-gaa-hou commented May 12, 2026

Uh oh!

albanD commented May 12, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

dvrogozh commented May 12, 2026

Uh oh!

dvrogozh commented May 12, 2026

Uh oh!

fffrog commented May 13, 2026

Uh oh!

fffrog commented May 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

can-gaa-hou commented May 9, 2026 •

edited

Loading

netlify Bot commented May 9, 2026 •

edited

Loading

fffrog commented May 9, 2026 •

edited

Loading

fffrog commented May 13, 2026 •

edited

Loading