In the last weeks we have been testing our microservice infrastructure with several close friends. We called this phase our “Closed Alpha”. At the same time we were letting interested users put themselves on what we used to call “Private Beta List”. However, in the process of planning how to open up our platform to more people and especially people that we don’t know personally (yet), we decided to revise our wording to “Open Alpha”. Confusing? Yes. Logical? Absolutely. In light of our goal of transparency, we wanted to explain our line of thought, and our mindset behind that.
For one, we saw that our list of interested users was growing quite significantly and we think the best way to ensure a good user experience will be to let new users onto our platform in small batches in a regular timeframe (e.g. x users each week) and rather sooner than later. We decided to do this, as we want to have close relationships with our early users and build a product they love to use. We want to encompass as much early feedback as possible. There are tons of features to be implemented. But we want to choose the right ones, in the right order. We love to have conversations and get all of our users up to speed for using containers and Giant Swarm in the most efficient way they can.
Another reason for the “Open Alpha” naming is setting expectations right. Alpha for us means that things can still change, and that we are not production ready, though getting there. At the same time, our Open Alpha will be completely free (as in beer). Considering this, here’s what can you expect from us in this phase:
You can read more in our Docs.
So what would be perfect things you could try out on our Open Alpha:
If you’re not on the Open Alpha list yet, be sure to sign up below.
Request InviteGiant Swarm’s managed microservices infrastructure enables enterprises to run agile, resilient, distributed systems at scale, while removing the tasks related to managing the complex underlying infrastructure.
GET IN TOUCH
General: hello@giantswarm.io
CERTIFIED SERVICE PROVIDER
Comments (1)