@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
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
'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.
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!!
Congratulations @mohamed_habib1 and @igor_zalutski on the launch! I've always found the AWS UI very difficult to navigate. It's too crowded. It assumes familiarity with the sometimes (poorly named) AWS products. I suspect the AWS UI is as complicated/obtuse as is it because of the rise in AWS certifications - they're practically a cottage industry themselves. Twenty years ago a sysadmin/devops candidate would have LAMP (Linux, Apache, MySQL, PHP) on their resume and more and more you'll see AWS certifications. This is good and bad - good because it communicates expertise with (necessary) cloud services provider but bad in that it only increases hyper-specialization and cloud provider lock in. At the point you're building a startup or tech stack now do cloud providers not only have all of your data and infrastructure, they somewhat own/define portions of your team. Hiring, onboarding, and keeping people is one of the biggest challenges in a business. It's extremely "sticky" for AWS and a brilliant strategy overall but it's (IMO) not the best thing for technology companies and (especially) early stage startups! I'm thrilled to see something like Lemon come along to help address this and lower the barrier to utilizing multiple cloud providers for business-critical data and architecture.
With that, a couple comments:
- Github seems to be the only social login you support for account creation. When using it the name of the application is "diggerhq". From following the launch on HN I realize this is old branding but not only is it not clear to users, all users authorizing the app will have to be re-authed or otherwise dealt with later. That said it's a logical choice - getting setup with the other social auth providers is onerous and your targeted user is likely to have a Github account.
- The pricing tiers are fairly expensive and have significant jumps. Free is awesome but even with my recently launched, simple startup it's unusable for us. I have an account but I don't have anything defined because it's basically a non-starter. Even with our very small team $70/user/month for the next tier would mean that we end up spending more on Lemon than we do for our entire infrastructure (currently hosted on Azure and GCP - which is also locked behind the Enterprise/ask us for pricing tier)!
Unfortunately given that last point I'm unable to have any further experience with the product - and I wish I did!
Congratulations again on the launch and I'll be watching you!
@kristian_kielhofner thank you so much for this thoughtful comment!! super helpful. And glad it resonates!
Pricing is something we're still figuring out tbh, thanks for sharing your perspective
Noted on social logins. Diggerhq naming, yes, that's a tradeoff we made in order to not deal with multi-app login
Replies
Digger.dev
Invoice generator
Digger.dev
Digger.dev
Digger.dev
Sprinkles
Digger.dev
ArrayList
Digger.dev
Digger.dev
Digger.dev
Digger.dev
Digger.dev
FromNotion
Digger.dev
Digger.dev
TailAdmin
Digger.dev
Digger.dev
123RF AI Search Engine
Digger.dev
Digger.dev
Digger.dev
Digger.dev
Digger.dev
Digger.dev
Digger.dev
Digger.dev
Digger.dev