diff --git a/docs/developer-docs/smart-contracts/write/overview.mdx b/docs/developer-docs/smart-contracts/write/overview.mdx
index 8468ac1317..bd16d537ba 100644
--- a/docs/developer-docs/smart-contracts/write/overview.mdx
+++ b/docs/developer-docs/smart-contracts/write/overview.mdx
@@ -115,5 +115,5 @@ Since users are controllers of their canisters, they can install their own code,
 These user benefits come at large development costs because the main canister needs to be programmed in such a way that it can handle all possible actions of potentially malicious user canisters.
 This is a new and unprecedented way of programming.
 There hasn’t been a successful implementation of this vision yet.
-A couple of projects that opted for this architecture have not given the ownership of canisters to the users yet.
+A couple of projects that opted for this architecture, but only [NFID Vaults](https://nfidvaults.com) have given the ownership of canisters to the users.
 A common misconception is that the canister-per-user architecture is the most scalable, actually canister-per-subnet is more performant because it can utilize multiple subnets without having the overhead of too many canisters.