why deepstreamHub? compare us getting started faq
use cases
blog contact

why deepstreamhub?

I'm not sure I believe there is such a thing as "realtime apps" any more. Apps either update instantly and smoothly, or they appear broken. I feel that "realtime" as a feature has moved down the Kano graph. It is much more of an expectation, than an "exciter"

From Whatsapp’s messaging to Uber’s geo-tracking to collaboration in Google docs: modern apps share data the second it becomes available. But the infrastructure required to do so is hard to build, harder to scale and a nightmare to keep in sync.

This is where deepstreamHub comes in. It combines the power of a document oriented datastore with the speed of high performance message brokers. This creates a unique and scalable high performance platform that caters for a wide array of usecases and technologies:

  • deepstream helps ticket merchants drive revenue by selling out venues within minutes using realtime seatmaps that incentivise users to pay higher prices for quickly filling slots.
  • It reduces maintenance costs for electricity companies by enabling smart meters that continuously stream readings to a server without human intervention.
  • Or it reduces risk by allowing microservices to instantly share state, increase availability and react to each other’s changes.

On average we help our users...

  • cut backend development by

  • decrease time to market by

  • increase app revenue by

source: ds user survey 2016

But we’re especially good when the going gets tough

deepstream originated from realtime trading middleware that investment banks use to stream prices, chart data and execution orders from and to end customers. It now caters for usecases as challenging as low latency finance, mobile multiplayer gaming or the industrial IoT.

How is it different from other realtime platforms?

You can find a detailed answer on our comparison page - but in a nutshell, deepstream isn’t just a messaging platform (although it is that too), it’s an extremely fast realtime document storage and synchronization network.

Couldn’t I just build this myself?

As computer scientists will agree, distributed stateful systems that work in the real world are one of the hardest problems to get right. We combine decades of experience in some of the toughest environments with realtime usecases (Financial Trading, Multiplayer Gaming etc.), have spent years developing deepstream together with a hundred head strong community - and are still surprised by just how much there is to learn.

Can I trust you guys?

We hope so. It’s true that deepstream is comparatively young. While companies like realtime.co have have been around for more than 20 years we’ve only existed since 2015 - but that hasn’t stopped some of the largest corporations to not only trust us, but integrate us as the very heart of their stack. And there are good reasons for that:

  • We are a highly experienced team with a track record of building comparable technologies for enterprises around the world.
  • We’ve started (and are still based on and maintain) as deepstream.io, a very successful open source project with more than 5.500 github stars, countless integrations with other systems and an active community. That gives our users the confidence to escape vendor lock-in and always fall back on an open solution.