igorzij

21 ms·

1. 181.▲
   by igorzij 5y ago

   Yeah PaaS like Vercel and Heroku have an inherent limitation - at some point you need to move off them because the industry has moved on and you can only do so much without things like infra-as-code and kubernetes that became industry stand
2. 182.▲
   by igorzij 5y ago

   Things like Dynamo are AWS-specific, it is their way of locking you in. You could use MongoDB or Cassandra (which is right depends on what you use it for) that would work in any cloud provider. Moreover, for 90% of use cases the capabilitie
3. 183.▲
   by igorzij 5y ago

   We support Serverless too - Alicorn has a concept of Targets which are essentially different ways to run your backend code. You can mix & match Serverless, standalone containers and K8S. Under the hood Alicorn generates Terraform, which
4. 184.▲
   by igorzij 5y ago

   A bit more complex than that :) PaaS on top of K8S have a problem of serving no one - because for small cases they're too heavy and for large teams too inflexible, they could just as well use K8S directly. Alicorn actually generates in
5. 185.▲
   by igorzij 5y ago

   Hi HN! We've built Alicorn to allow startups escape vendor lock-in with their cloud providers. AWS, GCP or Azure – with Alicorn your stack runs anywhere. Switch cloud providers in one click and never run out of free credits! For a whil
6. 186.▲
   Show HN: Alicorn Cloud – Easily move between AWS, GCP and Azure(alicorncloud.io)

   82 points by igorzij 5y ago|41 comments
7. 187.▲
   by igorzij 5y ago

   Thanks for sharing your thoughts! CreditHero isn't a service that runs in your AWS account. It's a service that allows you to run your stack in someone else's AWS account
8. 188.▲
   by igorzij 5y ago

   Yes, a very reasonable concern, we haven't yet implemented any measures against this. However, deployment is done via Terraform centrally in the CreditHero backend, so we can put measures in place.
9. 189.▲
   by igorzij 5y ago

   We studied the T&Cs thoroughly prior to building this. Here: https://aws.amazon.com/awscredits/ The only point of potential concern is #3: "You may not sell, license, rent, or otherwise transfer Promotional Cr
10. 190.▲
    by igorzij 5y ago

    They prohibit reselling, but we believe that nothing stops one from hosting a friendly startup's stack or part of it in their account for free. Founders do that a lot. And that's what CreditHero makes super easy
11. 191.▲
    by igorzij 5y ago

    Hi HN! AWS free credits are great - until you run out of them. This can force startups to go out of business, or at least to rebuild with a different cloud provider. At the same time there are lots of startups who never use all of their AWS
12. 192.▲
    Show HN: CreditHero – extend your AWS free credits(credithero.io)

    23 points by igorzij 5y ago|14 comments
13. 193.▲
    by igorzij 5y ago

    Massive thanks - noted!
14. 194.▲
    by igorzij 5y ago

    Yep, that's exactly the reason why we went with Parameter Store We'd rather build a UI on top of that then let users down by sending them to AWS UI :)
15. 195.▲
    by igorzij 5y ago

    Very fair request! We are actually planning to support multiple "compilation targets" in future, including CloudFormation and CDK code generation. Just started with Terraform because it's the most widely used of all in the De
16. 196.▲
    by igorzij 5y ago

    Thanks so much!! Extremely helpful, and we'll address that asap
17. 197.▲
    by igorzij 5y ago

    Yes, that would be quite straightforward - just connect a repo and you're good to go as long as you put it into a container That said, if your entire project or most of it is a Wordrpess or Drupal site, you could be better off by using
18. 198.▲
    by igorzij 5y ago

    We have a concept of Targets - essentially "template generators" that follow a particular architecture and include modules for most commonly used services. When you connect your repositories Digger asks you to confirm a few basic
19. 199.▲
    by igorzij 5y ago

    On the Standard plan we don't take on any liability; but keep in mind that it's all git-based workflow with rollback to any state possible. And TF is mature enough to make glitches extremely unlikely. And we enforce least-privileg
20. 200.▲
    by igorzij 5y ago

    That's superbly helpful! Thank you so much!! We've taken note and will be working on improving docs and architecture transparency.
21. 201.▲
    by igorzij 5y ago

    Exactly!
22. 202.▲
    by igorzij 5y ago

    Thanks so much for this!!! Extremely helpful and a big overlook on our side. Will be fixed asap!
23. 203.▲
    by igorzij 5y ago

    Thank you!! Perhaps what we mean by "implementation" is different here. We should probably make it more explicit in the docs. What I mean by "interface" is "My stack needs infrastructure for 3 containers and 2 webap
24. 204.▲
    by igorzij 5y ago

    Thanks again! This viewpoint has a lot of merit for sure. Please let me defend my claim on Terraform capability though. The real question isn't whether doing X is possible with TF; it's whether it's likely to be done in pract
25. 205.▲
    by igorzij 5y ago

    Yes we focus mainly on AWS at the lower price points
26. 206.▲
    by igorzij 5y ago

    Yes we support PCI-DSS and SOC2 in the Enterprise plan
27. 207.▲
    by igorzij 5y ago

    Thanks Ben! For sure :)
28. 208.▲
    by igorzij 5y ago

    Its a very understandable viewpoint. We believe that you not only can - you should. It may sound a bit utopian today, but look at what these managed cloud services really are: the new hardware. You had to manage every piece of hardware your
29. 209.▲
    by igorzij 5y ago

    so sorry for that, we are looking at it!!
30. 210.▲
    by igorzij 5y ago

    sorry fixing now!!