Why Zeplo?

I’m the co-founder and CTO of Zeplo, and we’re building the future of serverless.

Zeplo is a message queue as a service. It allows developers to add retry, delay, queue and schedule to their existing HTTP endpoints without Redis, RabbitMQ or SQS. It works great with serverless - but can work with any HTTP endpoint.

And what do you have to do to get this queue magic working? Just prefix your URL with zeplo.to/your_url.com - that’s it. We then forward the request with the exact same method, query, body to your endpoint.

You might use it for one of the following use cases:

  • Ensuring incoming webhooks are reliably received
  • Send an email to a customer an hour after they sign up
  • Schedule a regular back up of your database
  • Run long running async tasks
  • Why now?

    Serverless has seen increased adoption, even within larger organisations - but adopting serverless still brings numerous challenges. The supporting infrastructure is struggling to keep up.

    What about AWS SQS?

    AWS SQS and Google Cloud Pub Sub and powerful tools, but they require a bunch of setup and are quite limited in their functionality. You can only delay messages by 15 minutes, queued requests can only be pending for 5 minutes and there is almost no visibility into the message queue. It’s very hard to re-process failed records!

    What’s next?

    We’re focussing on building out the enterprise features, whilst continuing to make the onboarding process simpler for smaller development teams.

    If you want to keep up to date on our progress - make sure to follow us at @zeploio

    © Copyright 2022 MildInsanityTakesTime