diff --git a/source/guides/writing-pyproject-toml.rst b/source/guides/writing-pyproject-toml.rst
index 318fe0d51..1d035a384 100644
--- a/source/guides/writing-pyproject-toml.rst
+++ b/source/guides/writing-pyproject-toml.rst
@@ -314,11 +314,13 @@ backend>` now support the new format as shown in the following table.
      - flit-core [#flit-core-pep639]_
      - pdm-backend
      - poetry-core
+     - uv-build
    * - 1.27.0
      - 77.0.3
      - 3.12
      - 2.4.0
      - `not yet <poetry-pep639-issue_>`_
+     - 0.7.19
 
 
 .. _license:
diff --git a/source/shared/build-backend-tabs.rst b/source/shared/build-backend-tabs.rst
index 7fc3a61da..608fcaddd 100644
--- a/source/shared/build-backend-tabs.rst
+++ b/source/shared/build-backend-tabs.rst
@@ -32,3 +32,11 @@
         [build-system]
         requires = ["pdm-backend >= 2.4.0"]
         build-backend = "pdm.backend"
+
+.. tab:: uv-build
+
+    .. code-block:: toml
+
+        [build-system]
+        requires = ["uv_build >= 0.7.19, <0.9.0"]
+        build-backend = "uv_build"
diff --git a/source/tutorials/managing-dependencies.rst b/source/tutorials/managing-dependencies.rst
index db3b82533..bb67a60e3 100644
--- a/source/tutorials/managing-dependencies.rst
+++ b/source/tutorials/managing-dependencies.rst
@@ -177,3 +177,5 @@ and techniques, listed in alphabetical order, to see if one of them is a better
   structured as a distributable Python package with a valid ``pyproject.toml`` file.
   By contrast, Pipenv explicitly avoids making the assumption that the application
   being worked on will support distribution as a ``pip``-installable Python package.
+* `uv <https://docs.astral.sh/uv/>`__ for a single tool that covers the entire project
+  management workflow, including dependency management, packaging, and publishing.