Dispatched: The Missing Background Queue for Your Serverless Apps

I build a lot of serverless apps with Next.js and deploy them on Vercel—I’m a huge fan of Vercel for its amazing developer experience (DX). However, I found myself running into challenges when it came to running background jobs in a queue. Setting up a reliable, straightforward solution wasn’t as simple as I hoped.

So, I decided to build Dispatched—a lightweight, developer-friendly service designed to handle background jobs with pure HTTP simplicity. It's perfect for serverless environments like Vercel, Netlify, and AWS Lambda.

I’d love to hear your thoughts and feedback! If you’ve faced similar challenges or have ideas for improvement, let me know. 😊

I'm also giving a launch special discount of 30% off with code LAUNCH30.

I'm interested in the product and have been looking for a similar project to quickly support my own. I'd like to start with the free tier, but I have a few questions.

If a free tier is available, could you please clarify its limitations regarding job execution, queue depth, or request volume?

There is a free tier but it's mostly for trialing out the app and for testing/sandbox purposes. You could ideally use it for smaller websites but the limits are smaller (only 100 jobs/tasks per day, max 60 seconds per job, etc). For more info, please checkout the pricing page: https://dispatched.dev/pricing

I would recommand using the free tier to test it out, and if you're happy, subscribe to the Indie plan or startup depending on the number of jobs you need for a day.

Also, if you have any feedback, please let me know as well. Thank you for your interesting in trying out Dispatched!

I've added a couple of medium articles about this too (~3mins read time each):

This topic is closed. It no longer accepts new replies.