#marketplace

BestCodes I love this @damilareoo :) I'm curious - why did you name it that?

Damilare Haha!! Thank youuu. It's just a nick name my friends call me lol

Rahmankazemi87 4375 اینا متعلق به کنه ایا

Joecelaster @abhivarde , This is cool. I'd love to contribute. Is this open source ?

Abhivarde thanks! not open source currently, maybe later 🙂 curious though, what would you want to contribute or improve!?

Abhivarde **update on snipply** shipped offline support. here's how it works: → supabase anonymous auth gives every visitor a silent identity the moment they land. no form ever appears → supabase rls lets anyone read components but only you can edit your own → every save hits supabase and indexeddb at the same time → go offline, saves still work locally. come back online, header dot turns green and you're synced → shared links load from local cache if you've opened them before. a small "cached" badge tells you full local-first with supabase doing the hard parts live: snipply.abhivarde.in

Pauline P. Narvas Great work! Thanks for sharing, Edu

BestCodes Yes it works great! Side-note: I searched up 8bitcn by OrcDev. Cool to see that listed there I tried this exact query and I'm not sure how relevant the results were... I did just search "portfolio" and it brought up some portfolios though, so that's working! Very interesting idea. Isn't this something that Google Stitch introduced already? Seems to be great performance-wise. Can't think of anything off the top of my head! Overall the UI is solid and it seems pretty featureful. Maybe, um, list my website (just kidding) Great job @educalvolpz

BestCodes I like how you have an "AI info" page for AI agents to read. I've been meaning to do that on some of my sites but I haven't thought of a good way to go about it yet.

Amy Egan I love seeing so many awesome things people have build with shadcn/ui! Thanks for sharing this dashboard toolkit

Vaibhav Gupta Glad to see you liked it!!

system Hi there! I'm just a bot here to share some info that might help you before a human arrives. If your account is eligible, you can use our new self-service recovery flow: 1. Go to vercel.com/login 2. Choose to sign in using the email + one-time password (OTP) option. 3. Select Use another sign-in method 4. Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account 5. Follow the remaining prompts to complete the recovery process If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yourself. You can also use recovery codes if you've stored those in a safe place that you can still access. If you are unable to access your account using the steps above, you can open a support case using the Start 2FA recovery option on the Two-Factor Authentication login screen. **Please do not publicly post account details, like your email address, that could help an attacker gain access to your account in the future.** There's no need to open an additional case if you already have one open. Thanks for your patience while the team works to resolve all cases as quickly as possible while keeping everyone’s accounts safe and secure. A human should be here soon to help.

Amy Egan If you're using the Supabase integration, you can delete it from the Vercel dashboard in integration settings. If you're using a separate Supabase account, you can manage that in your account or organization settings at supabase.com

Pauline P. Narvas This should be fixed now!

Joe Weston Ok, so I found that I probably needed to install the Supabase Integration for Vercel, and then grant permission for a specific vercel project to a specific database project in Supabase. Now that I've done that...I thought I'd be good, but it turns out I still see the same "You don't have permission to connect this integration.". Thoughts?

Pauline P. Narvas Hey, Rob! I recommend checking out: https://vercel.com/partners/solution-partners

Pauline P. Narvas We also have folks in the community who are always looking for their next gig: https://community.vercel.com/t/hire-me-april-2026/37458

yasoob Hi eric, thanks for letting us know. Could you please try again? The Prisma team has just pushed out a fix.

Eduardo Pavez Hi @amyegan, Any thoughts on this? Thanks!

Amy Egan Hey @epavez, sorry I missed your earlier post! For the database filter, I believe those are typically related to Vercel Marketplace integration options. I'd be happy to get you connected with the team if you want to explore adding Backblaze B2 to the marketplace. Just lmk if you're interested in that As for the full-stack deployment, it looks like you already configured Services in a `vercel.json` file to deploy everything in a single Vercel project. That's the right approach for all-in-one deployment. Let me ask the templates team if they have any other info or recommendations

Ryu Hi JorgY\_, Given your diagnostic output, I’d focus on the Supabase connection type rather than the PHP env vars. The suspicious part is: ``` Database: Supabase Postgres Direct connection Port: 5432 pdo_pgsql_loaded: true sslmode=require Works locally, fails on Vercel ``` Supabase direct database connections use IPv6 unless you have the IPv4 add-on enabled. Vercel serverless functions are commonly the case where the direct `db.<project-ref>.supabase.co:5432` connection fails, even though the same credentials work locally. I’d switch the deployed PHP API to the Supabase **Shared Pooler / Supavisor** connection string instead of the direct connection string. In Supabase: ``` Project → Connect → Connection string → Pooler ``` For serverless functions, try the transaction pooler first: ``` host: aws-<region>.pooler.supabase.com port: 6543 user: postgres.<project-ref> database: postgres sslmode: require ``` So your PDO DSN would be shaped more like: ``` $dsn = "pgsql:host={$host};port=6543;dbname={$database};sslmode=require"; $pdo = new PDO($dsn, $username, $password, [ PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION, ]); ``` Make sure the username changes too. For the pooler it is usually `postgres.<project-ref>`, not just `postgres`. Supabase explains the IPv4/IPv6 difference here: https://supabase.com/docs/guides/troubleshooting/supabase--your-network-ipv4-and-ipv6-compatibility-cHe3BP One more thing: temporarily log the real PDO exception message, but not the password or full connection string. The difference between `connection refused`, `timeout`, and `password authentication failed` will confirm whether this is network/IPv6 or credentials.

Pauline P. Narvas Hey! I'll check with our Marketplace team. In the meantime, which other community posts have you seen which are similar?

Pauline P. Narvas Could you check your Edge Requests for suspicious user agents, IP addresses, or referrers? I recommend enabling Attack Challenge Mode just in case. Go to your project settings → Firewall → Bot Management → Enable Attack Challenge Mode. This is FREE and won’t count blocked requests against your usage. I recommend: * Set up Spend Management to prevent future surprises (even on Hobby) * Consider custom firewall rules to block specific bad actors you identify * Enable Vercel’s Bot Protection managed ruleset for ongoing protection

Ryu Hi Vsme, I’d treat this as a potentially risky env/branch-mapping issue and disable any automatic migration-on-start behavior until you confirm which database the v0 chat is actually using. A safe way to debug it is to log only the environment and Neon host/branch, not the full connection string or password: ``` console.log({ vercelEnv: process.env.VERCEL_ENV, publicVercelEnv: process.env.NEXT_PUBLIC_VERCEL_ENV, databaseHost: process.env.DATABASE_URL ? new URL(process.env.DATABASE_URL).host : "missing", }) ``` If the v0 chat/preview shows `production` or points at the same Neon host/branch as production, then I would not run migrations from that environment. In Vercel, I’d also check: ``` Project Settings → Environment Variables ``` and confirm whether `DATABASE_URL` / `POSTGRES_URL` have separate values for Production and Preview. Preview env vars are used for non-production branches, and branch-specific Preview values can override the general Preview value. Neon’s Vercel preview integration is supposed to create a `preview/<git-branch>` branch and inject the connection string into that deployment, so if that branch is not being created, I’d check the Neon integration events and branch limit first: https://neon.tech/docs/guides/vercel-previews-integration For now, I’d make the app defensive: ``` if (process.env.VERCEL_ENV === "production") { // never run dev/reset/auto migrations here } ``` and only allow destructive or auto migrations when an explicit non-production flag is set, for example `ALLOW_PREVIEW_MIGRATIONS=true`. Can you share whether the v0 chat is connected to a Git branch that creates a normal Vercel Preview Deployment, or whether it is running only inside the v0 preview/chat environment?

Pauline P. Narvas Yes, you should be able to! Let us know if you run into any problems

Kadu I’m having a serious problem with this and I can’t solve it. I’ve been trying to fix it for 3 days, but nothing seems to work. Can you give me some support?

Pauline P. Narvas What serious problem is it? What error messages are you seeing?