'You don't need to be AWS Certified' that statement is soo pleasing to hear. AWS grew soo big and complex that it needs a certification and all that bs. Anyproduct which makes it simple is surely concentrating on a real painpoint.
Goodluck makers.
@rubenwolff mainly the pain of dealing with AWS for people who aren't devops experts
1. AWS UI it's disjointed, hard to navigate
developers are thinking in terms of apps and related services, naturally
whereas in AWS it's grouped by AWS service category and region
2. AWS UI is also overwhelming, it's exposing all the options at once. it's optimised for people who know exactly what they are doing. whereas to most developers it doesn't make much sense.
3. Finally, with AWS you either use UI or do infra-as-code . Meaning that either you miss out on what's pretty much industry standard (Terraform), or you have to write code even for trivial repetitive changes.
Hi ProductHunt! Co-founder of Lemon here
π€― AWS UI is like an airplane cockpit - perfect for seasoned pilots, incomprehensible to everyone else.
π Lemon is more like your phone β anyone can figure it out simply by using it. And it's free!
β Deploy containers, webapps, functions, databases, etc
β CI / CD just works out of the box, no configuration needed
β DevOps goodness: first-class Terraform support, environments, gitOps
π To get started, simply connect your AWS account at https://app.uselemon.io
@csaba_kissi So true. Worst of all, they literally cannot do anything about it - because it reflects Amazon org structure and optimised for independent org units interfering the least with each other. Integrated coherent user experience would mean that departments actually need to talk to each other, and that simply isn't possible at their scale
I'm so confused, the docs link to Digger which is just what Alicorn Cloud linked to https://www.producthunt.com/post.... These look like the same product but launched as separate products?
Could you clarify how Digger, Alicorn, and Lemon are different? Also, why do they all link to docs that talk about the Digger CLI?
@scott_ames_messinger heh you caught us π
The story behind it: we first built Digger which is the engine powering all these products
But then we realised that the value prop of it is too broad to sell for a tiny startup like us. If we were a large org then we could sell a general-purpose platform, but we aren't
So we needed to focus on one feature at a time. On which one? We could make a blind guess. Or we could ask the users - which we did by launching separate products, each focused on one use case. Under the hood it's the same engine, just minor UI tweaks.
Docs is our bad, needed to do a more thorough relabeling - will fix!!
SaaSBold