diff --git a/docs/reference/metadata-schemas.md b/docs/reference/metadata-schemas.md
index e75d82e..e5d398a 100644
--- a/docs/reference/metadata-schemas.md
+++ b/docs/reference/metadata-schemas.md
@@ -160,4 +160,7 @@ So, how can you make an NFT dynamic? Here are a few options, each with certain t
     3. However, this is not only adds complexity but can also be rather expensive because changing on-chain data requires users to pay gas fees, which isn’t scaleable for NFTs that dynamically change often. For instance, imagine requiring a user to pay gas fees just to change the background color of a PFP, purely for aesthetic purposes? That isn’t ideal.
 4. Augment [nft.storage](http://nft.storage) with additional tools that add a layer of indexing and querying *to the metadata,* thereby, enabling dynamism and composability of your NFT assets.
     1. This solution is more efficient than on-chain solutions and works *with* decentralized storage providers, like [nft.storage](http://nft.storage), for the assets themselves, ensuring the benefits of decentralized storage remain intact. For example, [Tableland](https://tableland.xyz) offers a structured relational data solution that can index off-chain data & state (e.g., pointers to a JPEG’s CID) as rows & columns and bring them to on-chain assets (using SQL & gateways). Namely, it enables relational, dynamic metadata while also helping add composability & query-ability to any NFT project.
-    2. Similar to the above, this approach also comes with nominal gas fees when changing table states (e.g., when updating attributes of an NFT) on EVM-compatible L1/L2s. Plus, the ability to leverage L2s allows for a very efficient solution that provides a new level of dynamism, composability, and access control.
\ No newline at end of file
+    2. Similar to the above, this approach also comes with nominal gas fees when changing table states (e.g., when updating attributes of an NFT) on EVM-compatible L1/L2s. Plus, the ability to leverage L2s allows for a very efficient solution that provides a new level of dynamism, composability, and access control.
+5. Use [Polybase](https://polybase.xyz/docs/dynamic-nft-metadata) to store your NFT metadata where you can pre-define fields which you would like to change dynamically after deploying the NFT. 
+    1. Polybase is web3 replacement for Firebase, Postgres and Supabase with native support for wallet-based permissions, token gating and zk proofs. 
+    2. Polybase can store any kind of structured data: user data, app state and metadata. Compose it with smart contracts (using oracles) and file storage (like Filecoin) for truly decentralized applications.