bicep VS infracost

Compare bicep vs infracost and see what are their differences.

bicep

Bicep is a declarative language for describing and deploying Azure resources (by Azure)
Our great sponsors
  • Scout APM - Less time debugging, more time building
  • SonarQube - Static code analysis for 29 languages.
  • SaaSHub - Software Alternatives and Reviews
bicep infracost
56 55
2,341 6,499
3.8% 5.8%
9.9 9.8
6 days ago 4 days ago
Bicep Go
MIT License Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

bicep

Posts with mentions or reviews of bicep. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-04-04.

infracost

Posts with mentions or reviews of infracost. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-03-24.
  • Lidl has launched a rival to AWS
    1 project | news.ycombinator.com | 30 Mar 2022
    Wonder how long until we get our first request to add support for this to infracost https://github.com/infracost/infracost? At least the price list looks a lot simpler than AWS / Azure / GCP - more like UpCloud! Though honestly, if it starts to work, I'm sure the number of prices/services will grow exponentially.
  • Top 10 uncommon DevOps tools you should know
    8 projects | dev.to | 24 Mar 2022
    If you’re a Terraform fan, you’ll love this one. What if I tell you you can couple your infrastructure as code with bill forecasting? Sounds fantastic, huh? That’s what infracost.io is all about: it will scan through your Terraform files when you commit some changes to git and estimate the resulting billing of your changes! Pretty handy to have before getting unpleasant surprises.
  • Terraform deployment estimation before the resource creation
    1 project | reddit.com/r/Terraform | 11 Mar 2022
  • Open source Go projects to contribute (beginners)
    25 projects | reddit.com/r/golang | 5 Mar 2022
    Infracost https://github.com/infracost/Infracost (cli tool for cloud cost estimates from terraform) is always looking for new contributors. I’m one of the maintainers and we’re an approachable lot who are happy to help you through your first dip into open source.
  • GitHub - infracost/infracost: Cloud cost estimates for Terraform in pull requests💰📉 Love your cloud bill!
    1 project | reddit.com/r/devopsish | 3 Feb 2022
  • Open-source cloud cost policies?
    2 projects | reddit.com/r/devops | 26 Jan 2022
    I wanted to share an interesting learning from the open source project https://github.com/infracost/infracost/ and see what people think about writing policies for cloud costs using things like Open Policy Agent and HashiCorp Sentinel. For example: https://github.com/infracost/actions/tree/master/examples/opa
  • Show HN: Infracost (YC W21) – open-source cloud cost policies
    8 projects | news.ycombinator.com | 26 Jan 2022
    Awesome! Let me know how it goes :) We also have CloudFormation in our target: https://github.com/infracost/infracost/issues/190
    8 projects | news.ycombinator.com | 26 Jan 2022
    Hi, we’re Ali, Hassan and Alistair, co-founders of Infracost ([https://www.infracost.io](https://www.infracost.io/)). Infracost shows engineers the cost of each Terraform change in CI/CD before resources are launched. When something changes, it posts a comment with the cloud cost impact. e.g. you’ve added 2 instances and volumes, and have changed an instance type from medium to large, this will increase your bill by 25% next month from $1000 to $1250 per month.

    We launched the first version of Infracost just under a year ago (https://news.ycombinator.com/item?id=26064588). As we said in our first release ‘the people who are purchasing cloud resources are not shown costs upfront, so they don’t know how much the resources will cost before launching them’. Our assumption was that because we are open source and the engineers are flying blind, they would pull us into the workflow. Actually, something different is happening:

    The engineers are not pulling us in - it turns out to be the senior DevOps, SREs and platform teams. One of their challenges is figuring out how their small team of 7 people can fulfill the infrastructure requirements of hundreds of engineers. To solve this, they have created and put in place processes for engineers to provision infrastructure when they need. Now they want to implement cost policies and guardrails so that these hundreds of engineers don’t blow past all budgets. For example, if a change will result in a higher than 15% increase, leave a warning. If a change results in a >25% increase in costs, block the change till a team lead has reviewed it.

    This has two implications for us. First, we need to create an output that isn’t only used by humans but is also digested into other systems to make further decisions. The second is the people we have been speaking to are not our end users. We need to figure out how we can get introduced to our end users, and create a different set of questions for each persona.

    Now, we are reworking our JSON output and creating examples with standard policy tools like Open Policy Agent (OPA), HashiCorp Sentinel and Conftest. We’d really love your feedback around the cost policies use-case. You can check out the repo for GitHub Actions at (https://github.com/infracost/infracost) (our other CI/CD integrations are listed here: https://www.infracost.io/docs/#4-add-to-cicd).

    We'd love to hear how you think about policies and guardrails.

    8 projects | news.ycombinator.com | 26 Jan 2022
  • I Got Pwned by My Cloud Costs
    1 project | news.ycombinator.com | 24 Jan 2022
    We've been thinking about this for a while, and if there is any way we can catch these types of cost spikes before they happen. We've managed to do it for Terraform resources using an estimation approach, and using a usage file, you can model expected usage-based resources (https://github.com/infracost/infracost/blob/master/infracost...), but this one has got us thinking more about policies.

    To be clear - we would not have been able to catch this one right now :'(

    Would love to hear thoughts / brainstorm ideas - is there any way we can proactively catch these types of cost spikes?

What are some alternatives?

When comparing bicep and infracost you can also consider the following projects:

Pester - Pester is the ubiquitous test and mock framework for PowerShell.

azure-cli - Azure Command-Line Interface

terracost-cli - AWS cost estimation for Terraform projects

terraform-cost-estimation - Anonymized, secure, and free Terraform cost estimation based on Terraform plan (0.12+) or Terraform state (any version)

terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is an open source tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.

azure-quickstart-templates - Azure Quickstart Templates

validator - :100:Go Struct and Field validation, including Cross Field, Cross Struct, Map, Slice and Array diving

prometheus - The Prometheus monitoring system and time series database.

aws-nuke - Nuke a whole AWS account and delete all its resources.

iam-policy-json-to-terraform - Small tool to convert an IAM Policy in JSON format into a Terraform aws_iam_policy_document

infracost-gitlab-ci