If you're an open source user, the first thing that you can do is just go to atlas.hashicorp.com and see the features we add on top of the project you're already using. We now break down features by project being augmented.
Example: Vagrant augmentation: https://atlas.hashicorp.com/learn/vagrant
We have pages like that for all our tools.
We'll continue to improve this! Thanks for the feedback.
EDIT: Sorry, I was answering "why don't I know what Atlas is" versus the answer that was expected for "what is Atlas". The best answer for that is to use the homepage and click on the product (Vagrant, Packer, etc.) you use the most! http://atlas.hashicorp.com
So is Atlas the "Pro" versions of your core offerings?
Or is it something else, a single coherent product that changes the way I'd interact with Vagrant, &c? Is it like Packer As A Service? Does it host images I make with Packer? Is it a centralized Consul repository?
I think it's the "managed nodes" pricing model (which is fine, don't get me wrong) that makes me confused about what the offering is.
If you note, this is the #1 voted comment and you still have not answered the question.
So please take this as an opportunity clarify succinctly what Atlas does and also push your team towards updating your web site.
Based only on the leading description, it sounds like something trying to be a non-crap Docker replacement that was actually built from experience instead of just trying to capture a VC money waterfall? Atlas builds upon and unites our popular open source tooling to create a version control system for infrastructure. Automate, audit, and collaborate on infrastructure changes across any infrastructure provider.
Though, looking more at this post, it's a "we did this product" post, not a post about the product: the product has become a polished, intuitive experience.
That's nice?
The actual product page starts with: Atlas unites HashiCorp development and infrastructure management tools to create a version control system for infrastructure. Automate, audit, and collaborate on infrastructure changes.
Which, I'm still not sure.
Atlas can be used for all its features, or features can be used individually. All components are HashiCorp open source tools that are hosted and run in Atlas.
That's what it can do, but not what it do. Is this a side effect of SF startup culture? Do we forget everybody doesn't live inside our startups?
As best I can tell, Atlas is their map (heh) of how all their pre-existing products work together, and you can buy one umbrella product/support instead of buying 4 individual products?
Atlas is an application that glues together four different projects by Hashicorp: Packer, Vagrant, Terraform and Consul.
Packer creates virtual machine images (also has Docker support). Vagrant will create, provision and run them for you (so a bit of overlap with Packer there). Terraform is basically a platform agnostic version of Amazon CloudFormation (create and manage infrastructure via configuration). Consul is a service discovery solution.
All of these tools used in conjunction can help you set up a machine, or a cluster of machines, on any supported provider, that will run your application images, all from a set of configuration files. More importantly, changes to your infrastructure and application environment are now a matter of editing configuration.
Atlas places a UI in front of these tools and allows you to execute commands and monitor their status.
So much so that I created a FOSS that uses it and Puppet: https://puphpet.com
In the case of the company I'm currently at it's even more important because we have a firmware build system with a non-trivial configuration that would take days to replicate correctly (because of all the "missing pieces" required that the original developer forgot to write down when documenting the process post-setting it up).
There's still some pretty significant pain points, bit surprised they released already. Hope they get piles of cash to roll in for all their hard work.
If I can switch my workflow to build and store all the box versions inside of Atlas, that would save some time and effort...
Per-node a difficult proposition -- the price of "per server" of something varies wildly, for example a t1.micro is roughly $9.50 a month, while a m4.4xlarge is $738. $40 on 9.50 seems extreme, but $40 on $738, and Atlas is only a 5% of the cost of your server.
But when your target customer is using high end instances, because they are creating more value for their company that way, a 5% upcharge for better management, can be justified. Mostly its because the team of ops/software engineers supporting production environment are going to cost more than the infrastructure anyways.
Additionally, any large deal (>1000 nodes) is gonna get negotiated anyways, so public pricing is kinda a wash.
Pricing seems a bit Atlassian: almost free if you're small, very expensive if you are not.
Now send someone to softwarecircus.io to talk about it!
