Zeplovs
Upstash


Upstash: If you want a serverless-friendly queue and Redis from a larger vendor with more infrastructure behind it

Message queue as a URL prefix, adding retries and delays to any HTTP request
As of 31 August 2026, Zeplo has a free plan and paid plans start at $39/month. A hosted queue you use by prefixing any URL with zeplo. Softwr lists it under APIs. Zeplo is available on Web, Cloud.
Overview
Zeplo is a queue-as-a-service for HTTP requests. Rather than provisioning a broker and writing a consumer, you send a request to a Zeplo-prefixed URL with query parameters describing the behaviour you want: retry counts and backoff, a delay before delivery, a cron schedule, a concurrency limit, or a deduplication key. Zeplo accepts the request immediately, then calls your endpoint according to those rules and records every attempt in a searchable log. The distinguishing property is how little integration it requires. There is no SDK to adopt, no broker to run and no consumer process to deploy; a single URL change turns a fire-and-forget HTTP call into a durable, retried job. That fits Vercel, Cloudflare Workers, Netlify and other environments where long-running background processes are awkward or impossible, and where the alternative is standing up a separate always-on worker just to hold a queue. Pricing is per request: a free Developer tier with 500 requests a month, a Company tier at 39 US dollars a month for a million requests, and additional volume at 10 dollars per million. That is cheap for the value at moderate scale. The trade-off is dependence: Zeplo sits in the execution path of your background work, it is operated by a very small team with no published SLA on the lower tiers, and if it is unavailable your jobs simply do not run. Extra team members cost 15 US dollars each, and the free tier allows only one.
The honest half
Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about Zeplo.
Cross-shopped
Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.


Upstash: If you want a serverless-friendly queue and Redis from a larger vendor with more infrastructure behind it


Inngest: If you need durable multi-step workflows and event-driven functions rather than single retried requests


Svix: If the specific job is delivering webhooks to your customers rather than queuing your own work
Pricing
Taken from the vendor's own pricing page. Prices move, so check before you buy.
Developer
Free
Company
$39 /mo
Enterprise
On request
Capabilities
URL prefix interface
Prefix any endpoint with zeplo.to to queue the request, no SDK required
Retries with backoff
Configurable attempt counts and backoff strategy via query parameters
Delayed delivery
Schedule a request for a fixed delay or a specific time
Cron scheduling
Recurring calls to an endpoint on a cron expression
Concurrency limits
Cap simultaneous in-flight requests per queue to protect downstream services
Deduplication keys
Suppress duplicate jobs with the same key within a window
Request logs
Searchable history of attempts, responses and failures
Team workspaces
Shared projects with per-member billing
Answered, with sources
Each answer names the page it came from, so you can check it rather than take our word for it.
You prefix your endpoint URL with zeplo.to and add query parameters for retries, delay, cron or concurrency. No SDK or broker is needed.
Free for 500 requests a month; 39 US dollars a month for a million requests, then 10 dollars per additional million.
It is a small vendor in your execution path with no published SLA below Enterprise, so weigh that against the convenience.
Yes, that is its main use, covering Vercel, Cloudflare Workers, Netlify and similar environments that lack long-running workers.
Keep looking
Outbound webhook sending as a service, with retries, signing and a customer-facing portal
Fully managed API gateway service for creating and managing APIs at scale
Direct banking API for ACH, wires, real-time payments, accounts and cards
US money movement API for ACH, RTP and FedNow with KYC and ledgering built in
European open banking platform for account data and payment initiation
Realtime messaging API for building live features into apps
Long-running financial data aggregation with deep transaction history
API-first card issuing platform with direct Visa, Mastercard and Amex network connections
European banking-as-a-service platform for embedding accounts, cards and payments into other products
Combined issuer and acquirer processing platform for fintechs, banks and acquirers
Banking as a service platform for embedding deposit accounts, cards and payments, with a sponsor bank behind it
Open source webhooks gateway you self-host, handling both sending and receiving
Developer tokenisation platform that holds card and sensitive data inside a PCI Level 1 environment you do not operate
Unified API management within the Boomi integration platform
One API for small business accounting, banking and commerce data
Command-line tool for transferring data using URLs with wide protocol support
"Neobank in a box" for banks in emerging markets, paid on a performance basis
French open banking payments built around B2B invoice collection
Softwr does not host reviews and shows no star rating for Zeplo, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.
What people switch to, and what they give up
Every tier, and where the cost actually lands
Put it head to head with anything we hold
Its rating, and an embed for your own site
European bank API aggregation with a free restricted production tier for your own accounts
Per connected account per monthDigital and AI-native engagement banking platform for customer-facing banking experiences
quote