docs: replace Pico references with Nano in Supabase for Platforms content (#48958)

apps/studio/components/interfaces/Organization/Usage/ActiveCompute.tsx

@@ -42,7 +42,7 @@ const ActiveCompute = ({ orgDailyStats, isLoadingOrgDailyStats }: ComputeProps)
             ? [
                 {
                   name: 'Learn more',
-                  url: `${DOCS_URL}/guides/integrations/supabase-for-platforms#pico-compute-instance`,
+                  url: `${DOCS_URL}/guides/integrations/supabase-for-platforms#nano-compute-instance`,
                 },
               ]
             : [],

apps/www/_blog/2025-12-05-introducing-supabase-for-platforms.mdx

@@ -41,7 +41,7 @@ You control the entire experience. Your users get the full power of Supabase.
 With **Supabase for Platforms**, you can:
 
 - Offer a complete white-label backend to your users entirely powered by Supabase
-- Pay only for compute hours consumed with our newest Pico instances that scale to zero
+- Pay only for compute hours consumed with Nano instances that scale to zero
 - Access features purpose-built for managing backends on behalf of your users
 - Embed a lightweight Supabase Dashboard directly in your app through Platform Kit, so your users never leave your tooling
 - Let your users "claim" (transfer) their projects to their own Supabase orgs whenever they're ready, while you maintain access to those projects through OAuth integration
@@ -138,9 +138,9 @@ These features are available to a subset of our AI Builder customers. [Contact u
 
 ## Compute that scales to zero
 
-We offer Pico instances that scale to zero when not in use. This is ideal for platforms with many projects that have variable usage. You only pay for what your users actually use.
+We offer Nano instances that scale to zero when not in use. This is ideal for platforms with many projects that have variable usage. You only pay for what your users actually use.
 
-[Docs](/docs/guides/integrations/supabase-for-platforms#pico-compute-instance)
+[Docs](/docs/guides/integrations/supabase-for-platforms#nano-compute-instance)
 
 ## Restore points
 

apps/www/components/Solutions/FeaturesGrid.tsx

@@ -7,7 +7,7 @@ import styles from './features-grid.module.css'
 
 export default function FeaturesGrid(props: any) {
   const hasExtendedCards = props.features.some(
-    (f: any) => f.id === 'claim-flow' || f.id === 'platform-kit' || f.id === 'pico-instances'
+    (f: any) => f.id === 'claim-flow' || f.id === 'platform-kit' || f.id === 'nano-instances'
   )
 
   return (
@@ -43,7 +43,7 @@ export default function FeaturesGrid(props: any) {
         <Content card={props.features.find((f: any) => f.id === 'claim-flow')} />
         <Content card={props.features.find((f: any) => f.id === 'platform-kit')} />
         <Content
-          card={props.features.find((f: any) => f.id === 'pico-instances')}
+          card={props.features.find((f: any) => f.id === 'nano-instances')}
           innerClassName="
             xl:flex-row
             [&_.image-container]:border-b

apps/www/components/Solutions/features-grid.module.css

@@ -17,7 +17,7 @@
     'postgres            mgmt-api'
     'pricing             branching'
     'claim-flow  platform-kit'
-    'pico-instances      pico-instances';
+    'nano-instances      nano-instances';
 }
 
 @media (min-width: 1280px) {
@@ -25,6 +25,6 @@
     grid-template-areas:
       'postgres     mgmt-api            mgmt-api'
       'pricing      branching           claim-flow'
-      'platform-kit pico-instances      pico-instances';
+      'platform-kit nano-instances      nano-instances';
   }
 }

apps/www/data/solutions/ai-builders.tsx

@@ -617,7 +617,7 @@ const data: {
         ),
       },
       {
-        id: 'pico-instances',
+        id: 'nano-instances',
         icon: Timer,
         heading: (
           <>
@@ -657,7 +657,7 @@ const data: {
                 strokeLinejoin="round"
               />
             </svg>
-            Pico instances
+            Nano instances
           </>
         ),
         subheading: (