Tech stacks

The target stack defines your migrated application's tech stack.

Both supported stacks use Next.js and Supabase. They differ in the provider that runs backend workflows. We will be expanding the list of supported stacks in future.

Shared foundation

Both stacks use Next.js App Router for the web application and Supabase for data, authentication, and storage.

The selected stack controls the generated code and setup work.

Recommended stack: Vercel Workflows

Use Next.js + Supabase + Vercel Workflows as the default choice.

Vercel Workflows provides durable backend workflows on the same platform as the Next.js app. This keeps the application and its workflow runtime together and avoids an additional dependency for background taks.

Use Trigger.dev for specific requirements

Choose Next.js + Supabase + Trigger.dev when the project has a specific long-term requirement for a separate workflow runtime, such as long-running jobs or scheduled workflows that need Trigger.dev.

Use this option when that requirement is clear. It adds a separate service to operate and maintain.

Select a stack

Select a stack for a migration:

buildprint migration stack select nextjs-supabase-trigger my-app

You can select a different stack while the migration is being prepared. After buildprint migration init succeeds, the stack is fixed for that migration.