Waiting list for Memphis cloud is now available
Learn how to reduce your data traffic by 30% instantly
STAR US 2.7k

Sign up to participate in the private beta!

Event streaming like you have never experienced before.

Private Beta
Memphis Cloud

Build queue-based applications at the speed of light.
Full serverless experience.

Open-Source

Fully available under the Memphis BSL license

curl -s https://memphisdev.github.io/memphis-docker/docker-compose.yml -o docker-compose.yml && docker compose -f docker-compose.yml -p memphis up
helm repo add memphis https://k8s.memphis.dev/charts/ --force-update && helm install memphis memphis/memphis --create-namespace --namespace memphis --wait

A turnkey solution for self-hosted event processing

  1. Run on any K8s or docker
  2. Fully aligned with Memphis' upcoming cloud

How Memphis.dev Helps Developers and Data Engineers

5 minutes average time to success. Deployment to data ingestion.

Martin Brodbeck
CTO
Priceline

What used to take three months in Kafka takes three minutes with Memphis. And with 90% fewer costs in the process.

David Mytton
Founder
console.dev

All that time you spend scaling, managing, and maintaining Kafka is better spent building your actual product. Memphis frees you to do just that.

Guy Podjarny
Founder
Snyk

Fits perfectly for microservices architecture and cloud-native environments.

Arjun Anjaria
Head of Data
Tiqets

Memphis gives you all the benefits of a traditional message broker minus all the deployment and operational overhead.

Tal Goldberg
Sr. Software Engineer
Palo Alto Networks

Async communication between microservices = use Memphis.

Carlos Gasperi
Software Engineer
Abnormal Security

I didn't realize working with a message broker could be pleasant until I came across Memphis.

Fred Simon
Chief Data Scientist
JFrog

The user experience and management tools allow different data stakeholders to collaborate over the pipelines.

Ran Ribenzaft
CTO
Epsagon (Cisco)

Message brokers are the core of the modern organization. Finally, I enjoy working with one.

Ariel Bar
Sr. Software Engineer
Zoominfo

It helped me build microservices-based data pipelines.

Daniel Eliyahu
Sr. Software Engineer

Less troubleshooting time. At least 50% of my time got back to me.

Judd Misael Baguio
Sr. Software Engineer
Penbrothers

I used NATS before when I try to implement event-driven side projects but Memphis made it better because of the dashboard UI and it really helped me debug the flow of my messages that were sent.

Marcelo Okano
CEO
OKN Group

Easy to install and run, very fast, an excellent alternative to Kafka.

How Memphis.dev differs from the landscape
Message consumption model
Pull-based
Pull-based
Pull/Push-based
Push-based
Storage architecture
Log
Log
Log
Index
Self-Healing
Notifications
Slack, Mattermost, email*
None
None
None
Message tracing (aka Stream lineage)
Mirroring (Replication)
Requires quorom-queues
Multi-tenancy
GUI
Storage tiering
Idempotency
Schema Management
Data-Level Observability
Content-aware routing
*
Consumer-level
Retry mechanism
Protocols
SDK (TCP), HTTP (REST), gRPC*, WS*, AMQP*, MQTT*
TCP
TCP, gRPC, WS
STOMP, AMQP, MQTT, WS, HTTP
Dead-letter
Priority queues
Delayed queues
Consumer-level
Consumer-level
Producer-level
Attribute-based consumer
Message headers
Languages
Go, Node.JS, Python, Typescript, NestJS, Java*, .NET*, Kotlin*
Python, Ruby, Elixir, PHP, Swift, Go, Java, C, Spring, .Net, and JavaScript
Python, Ruby, Elixir, PHP, Swift, Go, Java, C, Spring, .Net, and JavaScript
Python, Ruby, Elixir, PHP, Swift, Go, Java, C, Spring, .Net, and JavaScript
Message consumption model
Pull-based
Storage architecture
Log
Self-Healing
Notifications
Slack, Mattermost, email*
Message tracing (aka Stream lineage)
Mirroring (Replication)
Multi-tenancy
GUI
Storage tiering
Idempotency
Schema Management
Data-Level Observability
Content-aware routing
*
Retry mechanism
Protocols
SDK (TCP), HTTP (REST), gRPC*, WS*, AMQP*, MQTT*
Dead-letter
Priority queues
Delayed queues
Consumer-level
Attribute-based consumer
Message headers
Languages
Go, Node.JS, Python, Typescript, NestJS, Java*, .NET*, Kotlin*
Message consumption model
Pull-based
Storage architecture
Log
Self-Healing
Notifications
None
Message tracing (aka Stream lineage)
Mirroring (Replication)
Multi-tenancy
GUI
Storage tiering
Idempotency
Schema Management
Data-Level Observability
Content-aware routing
Consumer-level
Retry mechanism
Protocols
TCP
Dead-letter
Priority queues
Delayed queues
Attribute-based consumer
Message headers
Languages
Python, Ruby, Elixir, PHP, Swift, Go, Java, C, Spring, .Net, and JavaScript
Message consumption model
Pull/Push-based
Storage architecture
Log
Self-Healing
Notifications
None
Message tracing (aka Stream lineage)
Mirroring (Replication)
Multi-tenancy
GUI
Storage tiering
Idempotency
Schema Management
Data-Level Observability
Content-aware routing
Retry mechanism
Protocols
TCP, gRPC, WS
Dead-letter
Priority queues
Delayed queues
Consumer-level
Attribute-based consumer
Message headers
Languages
Python, Ruby, Elixir, PHP, Swift, Go, Java, C, Spring, .Net, and JavaScript
Message consumption model
Push-based
Storage architecture
Index
Self-Healing
Notifications
None
Message tracing (aka Stream lineage)
Mirroring (Replication)
Requires quorom-queues
Multi-tenancy
GUI
Storage tiering
Idempotency
Schema Management
Data-Level Observability
Content-aware routing
Retry mechanism
Protocols
STOMP, AMQP, MQTT, WS, HTTP
Dead-letter
Priority queues
Delayed queues
Producer-level
Attribute-based consumer
Message headers
Languages
Python, Ruby, Elixir, PHP, Swift, Go, Java, C, Spring, .Net, and JavaScript

* Available soon. Cloud only.