Vultr is an independent cloud computing platform on a mission to provide businesses and developers around the world with unrivaled ease of use, price-to-performance, and global reach.
$2.50
per month
Pricing
Apache Mesos
Vultr
Editions & Modules
No answers on this topic
Block Storage
$1
per month
Cloud Compute
$2.50
per month
Object Storage
$5
per month
Kubernetes Engine
$10
per month
Load Balancers
$10
per month
Managed Databases
$15
per month
Optimized Cloud Compute
$28
per month
Cloud GPU
$90
per month
Bare Metal
$120
per month
Offerings
Pricing Offerings
Mesos
Vultr
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Pricing is based on specifications chosen in each product category. Bandwidth is also included up to a certain amount per month.
There's really no reason to ever use Mesos. We switched over to Kubernetes and it's been a breath of fresh air - better CD support, easy CLI for browsing logs, no mysterious dangling redeploys. If you're looking for a tool to manage a fleet of Docker containers on VMs, Kubernetes beats Mesos by a wide margin.
I've been with Vultr over 5 years hosting multiple businesses and email related services. I never experienced a significant outage or data loss. Migration has always been successful as well. Support is top tier and IP reputation is clean. I like the choices of OS, ease of platform use and multiple hosting/ region options.
Mesos may have many frameworks. If you have Mesos installed on your servers, you may use it for many kinds of tasks. Today we're running only web applications but the idea is to install a different framework for big data soon.
Unreliable deployments that would fail for no good reason. Sometimes our Docker container would be "restarting" forever because Mesos thought it didn't have enough resources to start the container.
Impossibly slow UI. Built in React under the hood with a lot of bloatware backed in, so loading the Mesos UI on a slow internet connection was painful.
No real logging solution - it would stream "console.log()" output to the UI, but searching for logs wasn't really possible without downloading a huge file.
No built-in support for redeploying containers from a CI. We had to create a service whose whole job was to expose an HTTP endpoint that restarted a container, and then made Circle CI ping the endpoint whenever we wanted to redeploy.
We’ve been extremely satisfied with the service for many years. After trying other providers, we’ve found nothing that matches the reliability and performance—so we’re not likely to switch anytime soon.
easy to use and configure. great bang for the buck. I need an affordable solution to host in the cloud data from systems installed at our client's site with the ability to drill down and change the configuration remotely. Vultr enabled us to do that in an efficient and affordable way.
Kubernetes is really great and their community is growing really fast (Google influence). We evaluated it in the beginning and it would fit for our web applications workload. We decided to proceed with Mesos because it has more potential. You may use a different framework for different kinds of tasks on Mesos. There is a Kubernetes framework for Mesos, by the way.
Linode is a more old-school offering. Linode pricing model and infrastructure rely on classic Virtual Machines. What we like about Vultr is that they offer the same at the front, but in the back, the machines are much more flexible and can be tailor-made to our needs, which of course also impacts the costs of running the infrastructure.