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!!
Report
Love it, I've been working with AWS a lot recently and this looks like something I'd enjoy using :)
@siddharth2395 thank you!! Glad you like it - give it a try ;)
Report
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
123RF AI Search Engine
Digger.dev
Digger.dev
Digger.dev
Digger.dev
Digger.dev
Digger.dev
Digger.dev
Digger.dev
Digger.dev