qdOpen-source, drop-in Amazon SQS replacement for Kubernetes
An open-source, production-ready, highly available message queue that replaces Amazon SQS and runs natively on Kubernetes.qd (pronounced "queued") is an open-source, drop-in replacement for Amazon SQS. Applications written against SQS keep working, and the queue runs in your own Kubernetes cluster: highly available, production ready, and wherever your cluster is.
- Licence
- Open source
- Source
- github.com/hexploits/qd
- Pronounced
- “queued”
- Built by
- Hexploits, London
Who it’s for
- Teams moving workloads off AWS, or running them in more than one cloud, whose applications already depend on SQS.
- Platform teams that want queues inside the cluster, under the same deployment, monitoring and data residency as everything else.
- Engineers who need SQS locally and in CI without an AWS account.
What it does
Open source
The source is public on GitHub, so you can read it, run it and change it.
Drop-in SQS replacement
Built to stand in for Amazon SQS, so existing producers and consumers do not need rewriting.
Kubernetes native
Deployed and operated as a Kubernetes workload, alongside the services that use it.
Highly available
Built for high availability, so the queue is not a single point of failure.
Production ready
Built for production traffic, not only for local development and tests.
Related services
The engineering work that usually sits around qd.
Kubernetes platforms
Under Cloud and platform
Managed clusters with high availability, GitOps deployment and the observability to prove it.
Cloud architecture and migration
Under Cloud and platform
Landing zones, network design, identity and a migration plan with rollback at every step.
Cost optimisation
Under Cloud and platform
Right-sizing, reserved capacity and architecture changes that reduce the bill without reducing resilience.
Questions we get asked
Is qd a replacement for Amazon SQS?
Is qd open source?
How do you pronounce qd?
Where does qd run?
Is it only for development and testing?
Next step
Talk to us about qd.
Tell us about the system and the sector. A named engineer replies within one working day. A written scope and an indicative price within two working days of a short scoping call.