Earlier this year, AWS and Vercel announced a collaboration with AWS Databases now available on v0. Read the Vercel blog!

 

Getting Started

Everything you need to go from zero to a running full-stack app on the AWS + Vercel stack.

  1. Sign up for AWS 
  2. Sign up for v0
  3. Request credits for AWS and v0 by June 26th at 12pm PT.
  4. Prompt v0 to build with AWS Databases
AWS

Aurora PostgreSQL

DynamoDB

Aurora DSQL

Vercel

AI-powered frontend generation. Describe what you want, v0 generates production-ready React/Next.js code with Tailwind CSS. Deploy to Vercel in one click.

 

FAQs

Getting Started

Q: Do I need to use v0 to build my frontend?

You must deploy on Vercel, but v0 is one of several ways to do that. You can also build your frontend manually (Next.js, Nuxt, SvelteKit, Astro, Remix, etc.) and deploy via the Vercel CLI or GitHub integration. v0 is recommended for speed, not required.

Q: Can I start with an existing project?

Yes. If it existed before May 27, 2026, it must have been materially updated to use AWS databases and the Vercel integration after the submission period begins. Judges may request evidence of work completed during the hackathon.

Q: Can I use AI tools to help build my project?

Yes, you may usev0, Copilot, Cursor, or AI coding assistants/IDEs. Judges evaluate the quality of your submission based on the defined criteria, not whether AI generated your UI components. Submissions with no meaningful engineering decisions will score poorly on Technical Implementation.

The Databases

Q: How do I connect my AWS Databases to my Vercel app?

Simply prompt v0 to build with an AWS database. You may also connect to AWS Databases from the Vercel marketplace. Check out the Vercel blog with instructions.

Q: Can my project use more than one AWS database?

Yes. Judges evaluate your application architecture including the choice of database for your application.

Vercel and v0

Q: Does using v0 affect how my project is judged?

v0 is an officially encouraged part of the stack. Judges evaluate your database integration, architecture, and product quality. The Technical Implementation criterion rewards genuine engineering decisions — a submission that is purely “I prompted v0 and submitted” without thoughtful database work will score poorly.

Q: How do I deploy from v0 to a live Vercel URL?

In v0, click Deploy. This creates a Vercel project linked to your account and gives you a *.vercel.app URL. Add your AWS credentials as environment variables under Settings → Environment Variables in your Vercel project dashboard.

Q: How do I keep my AWS credentials secure in a Vercel deployment?

Never commit credentials to your repository (which must be public for submission review). Use Vercel Environment Variables for AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_REGION. The Vercel Marketplace OIDC integration is the most secure option — it uses IAM roles with no stored keys. See the Starter Kits for working examples.

Q: How do I find my Team ID?

Go to vercel.com → select your team → Settings → General → scroll to "Team ID" and copy it or

This helpful article will show you where to find your team ID in Vercel.

Credits and Costs

Q: How do I get my free AWS and v0 credits?

Complete the credit request form linked on the hackathon page after registering. You’ll receive $100 in AWS promotional credits and $30 in v0 credits. Credits are distributed while supplies last.

Q: What if I run out of credits before the deadline?

Credits are sized to cover typical development usage. Additional costs are your responsibility. You are not required to spend beyond the provided credits to build a competitive submission. We recommend you monitor your AWS spend in the AWS Cost Explorer.

Q: When do the credits expire?

AWS promotional credits expire July 31st, 2026. v0 credits expire July 13, 2026.

Submissions and rules

Q: Can I submit to more than one track?

Each project can only be submitted to one Track. However, if you find you have enough time to build more than one project, you can submit to another, but each submission must be a unique and substantially different project.

Q: What should an architecture diagram look like? 

It should be clear and show your front end, backend, APIs/connections, and optionally, any components you plan to add later to ensure your application is ‘well architected’ for operational excellence, security, performance, reliability, cost optimization, etc.

Tips:

  • Label every box with both what it is (the component type, like "PostgreSQL" or "Lambda function") and what it does.
  • Show direction of calls with arrows — bidirectional only when it's actually bidirectional.
  • Group cloud-provider services if they're using one (e.g. a dashed box around "AWS" containing the components hosted there). The AWS Well-Architected page and the AWS Architecture Icons set are great references — many participants use those official icons.
  • Tools that work well: draw.io / diagrams.net (free, has AWS icon libraries built in), Excalidraw, Lucidchart, or Figma. Any of these can export to PNG/JPG/SVG.

Q: How do I prove I used one of the three required databases? 

Screenshot the Storage configuration page from within v0 or Vercel

 

Q: How do I get Bonus Points? 

Publish a piece of content (blog, podcast, video): Cover how you built your project using one of the specified AWS databases and Vercel. You can submit more than one piece of content. The content must be published publicly (e.g., on builder.aws.com, LinkedIn, medium.com, dev.to, YouTube, etc.) and not unlisted. You must include language that says you created the piece of content for the purposes of entering this hackathon. When sharing on social media, use the hashtag #H0Hackathon.