You may have heard about "the Cloud". We are a young software editor that created a solution that helps dev/devops/ops create environments for their apps in the Cloud.
(Opening a slight digression here, to give you a bit more context before we dive into our activity) Running applications in the cloud, goes along with a new way of coding your apps. Before, developers used to code their apps as one huge piece of code (called « a monolith »). Now, developers tend to break this code into pieces, a bit like a puzzle, which enables them to be more flexible when they need to change or upgrade one specific piece of the puzzle and not the whole monolith. This is what the Docker Logo is all about: pieces of containers put together. This logo (a whale carrying containers) was created on this platform. Please keep in mind that Docker is a major reference in our ecosystem.
Back to us, more precisely, we enable developers/devops to automate the creation of their environments through code, as environment creation is a repeat action that can be made over and over again depending on the context.
Automating the creation of environments through code is called "Infrastructure-as-Code". Creating Infrastructure-as-Code is tricky. It requires a specific organization within your team to put resources together and specific skills. If not done properly, automation has major downsides, such as chaotic process endangering your production (that means, having your app or your websites go down for a long time), and/or huge bills to pay, as resorting to cloud-based resources can be extremely expensive if not tightly under control.
Our solution helps users access the benefits of Infrastructure-as-Code and settle a safe framework to prevent off road actions. A bit like in a plant, with clear production process, we help « streamline » their production of code.
Last but not least, our solution helps users migrate from one Cloud provider to another or combine clouds and so avoid cloud providers lock in. For the record, major cloud providers in our ecosystem are Amazon AWS, Microsoft Azure and Google Cloud.
Out targets are:
- Senior DevOps (age 30-35) : a mix-breed of software developers and operations engineers. While software developers can be creative and like to design new things (like new code or new apps) Operations engineers (Ops) like simple, reliable, sturdy stuff that will not endanger their production (for example, no funky code that will crash their servers). While most developers like to brag about the latest fashionable tool that they used, most « Ops » grow a beard, frown a lot, don’t talk much and act disciplined as navy seals. Senior DevOps usually work in "Scaleups" (growing startups with an already reasonable level of success in funding and market traction) or big companies. To please them, your tool has to be both new, highly relevant on the tech side and extremely reliable.
- Young developers or Junior DevOps (age 25-30) : They are not as good or knowledgeable as Senior DevOps. Some of them work along with Senior DevOps and learn from them. Some of them are left to themselves (for example in small startups) where they have to create their own environments without any guidance. They usually struggle to do so, and get cold sweat as any mistake might mean a server breakdown and trigger huge consequences for them and the company.
- CTOs (age 30-45) : Usually those people are managers that want to make sure that everything is under control. « Everything » means the tech and the bills. They want to make sure that their DevOps or developers know what they are doing and will not make major mistakes that will endanger their activity. And they want to get a grip on the bills they have to pay, regarding cloud resources consumption.
Values we wish to convey:
- Making things accessible and fun to use
- Tool (we are a tool)
Designs that we like (see attached file)
- Hashicorp logo: simple, straightforward, sturdy, techie, reliable, Japanese touch
- Docker logo: very self-explanatory. Drawing design gives an impression of simple, accessible things
- Gitlab logo: we like gradient color designs. The wireframe base can also be used in various contexts
- Twistlock logo in 3D design
- Kube bench logo
- Ribbon-shaped forms with intricate designs, just for the beauty of it
- Overlapping elements, such as displayed on 99 Design trends page (Paypal, Duuky...)