Alternatives
Products that do what betterMQ — Http Messaging & Scheduling does
Http Messaging & Scheduling
- 1BT
Jan 2026 · bustermq.sh
- 2LA
Hi HN. I'm Carl, creator of LavinMQ. LavinMQ is an open-source message broker. AMQP 0-9-1, MQTT, HTTP and streaming. Single binary, minimal resource use. If you know RabbitMQ, it's that (but running on a fraction of hardware). We're the team behind CloudAMQP where we've hosted RabbitMQ for 14 years. Sometimes customers hit issues we couldn't fully explain / work around. So we built our own broker, in order to provide solutions where we previously couldn't (which is much easier when you control the full stack). It all started by me building an open-source AMQP proxy to handle short-lived…
Apr 2026 · github.com
- 3
- 4
- 5WJ
2016 · github.com
- 6
- 7
- 8SA
2021 · starqueue.org
- 9YY
2018 · yamq.io
- 10
- 11IB
2016 · github.com
- 12
- 13RC
Hi HN, we built SuperHQ, an open source app that runs AI coding agents in isolated microVM sandboxes instead of directly on your machine. Each agent gets its own VM with a full Debian environment. You mount your projects in, writes go to a tmpfs overlay so your host is never touched, and you get a diff view to accept or discard changes. API keys never enter the sandbox. We also just launched remote.superhq.ai which acts as a remote control for SuperHQ, allowing you to access your workspaces and agents from anywhere.
Apr 2026 · github.com
- 14AS
Hello, everyone. Three months ago, I started building my first GoLang package, VarMQ. In this short period, I gained a significant amount of traction from the community, and it resulted in over 140 stars on GitHub. A week ago, to check how it performs, I ran benchmarks with a similar package, Pond, which has been managed for years. Pond is not a message queue, though; however, it can be compared to VarmQ since it shares some similarities, except for its storage system. From the benchmarks, I got surprising results, which are that Varmq is taking 50%+ less memory than Pond and also has good…
2025 · github.com
- 15AM
2017 · amqphosting.com
- 16SO
2014 · sharq.io
- 17RA
2022 · github.com
- 18
- 19
- 20IC
In my last project, I was struggling to create and monitor cron jobs. So, instead of creating hundreds of standalone scrips and executing them with cron, I decided to turn those scripts into multiple endpoints. Next, I created a single service that I could schedule HTTP requests to those endpoints and monitor its execution. No more scripts, now everything is endpoints that I can run manually at any time I turned this scheduler service into a Micro-SaaS so you don't have to build it yourself: beew.io I know you can Schedule HTTP requests with Zapier but come on... I will not pay 50 bucks for…
2021
- 21
- 22AS
Hi HN! This is something I've been tinkering on for the past couple months. It's basically just an API/CLI for scheduling delayed or recurring jobs as HTTP requests. I initially built it as a personal tool to save myself a bit of time on little side projects where I've needed scheduled/recurring alerts, but decided it could be a good opportunity to practice building out a nice landing page [0] and documentation [1]. And who knows, maybe someone else will find it useful ¯\_(ツ)_/¯ The tool relies heavily on Elixir's Oban [2] library for managing jobs, and Mintlify [3] for…
2023 · booper.dev
- 23MU
The Problem Enterprise Go apps typically use multiple message queues: RabbitMQ for reliability, Kafka for streaming, SQS for cloud, NATS for microservices, Redis for caching. Each has different APIs, error handling, and testing strategies. Result: Teams spend months learning 6+ SDKs instead of building features. Migration = complete rewrites. The Solution mqutils provides one unified API for 6 major message queue systems. Same code, different URL: // Switch systems by changing URL only consumer, err := mqutils.NewConsumer("amqp://localhost:5672/orders") consumer, err…
2025 · mqutils.dev
- 24HA
2015 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →