Web 3.0 Starts Here, Join Us!
We have spent over a year analysing existing cloud solutions, architectures, and the needs of the Internet of Everything - to make sure our platform doesn't end up as another patchwork platform - a semi-random collection of services the developers find "cool".

Many of today's cloud platforms have already made certain architectural decisions for you, making it hard to tailor the architecture to the specific needs of your system. VStack.co is different. The core communication mechanisms are the same across all our services, but you can implement a wide variety of architectures on top of VStack.co.

Additionally, most of the current cloud platforms are accessed via HTTP. However, there are services, architectures and message exchange patterns for which HTTP is not suitable. Therefore we have taken a step further and defined a general purpose network protocol (IAP) which can handle a wider variety of message exchange patterns and use cases than HTTP.

Reactive Platform

VStack is a reactive platform in the sense that it uses an asynchronous message oriented architecture (which is the definition of "reactive").

Message Oriented

VStack is message oriented. All communication between the outside and VStack happens via asynchronous message passing. The platform is also message oriented internally, meaning that the platform`s internal services communicate via messages too.

IoE Ready

VStack is not just designed as a typical application backend with standard services like a database, message queue, log etc. The Internet of Everything (IoE) will be using many different communication patterns and services - some of which we don't even know yet.

Our platform is designed to be able to handle as wide a range of IoE use cases as possible. This includes traditional request-response type apps, but it also includes apps using one-way message passing, server side push, or streaming (in both directions).

High Performance and Scalability

VStack is designed with high performance and scalability in mind. The asynchronous message oriented architecture helps with that. Additionally, our services are designed to keep data in memory as much as possible. Even databases are kept in memory.

Services communicate via IAP, our compact binary network protocol. Servers that connect to our platform can receive messages from user devices in batches, resulting in better utilization of the server's bandwidth and CPU resources.


The better a cloud platform performs, the more clients can be served by the same hardware. Our focus on high performance and scalability means we can keep the prices lower than many other cloud platform providers. Slow platforms are expensive platforms.