3 ms·

I find the pricing of this service to be incomprehensible, as well as contradictory to “Unlimited private Git repositories for free”. Can anyone explain it?

by abtinf 8y ago

dragonwriter 8y ago
> I find the pricing of this service to be incomprehensible, as well as contradictory to “Unlimited private Git repositories for free”. You get unlimited private repositories, 5 project users, 50 GB of storage, and 50 GB egress per monthly for free. Monthly overage charges beyond the free quota are $1 per project-user, $0.10 per GB of storage, and $0.10 per GB of egress. So for 10 project-users, 100 GB of storage, and 200 GB of egress in a month, you pay $5 for users, $5 for storage, and $10 for egress, for a total of $20.
- abtinf 8y ago
  I still don’t get it. What is a “project” and how does it differ from a “repo”? If they are the same thing, isn’t every project/repo going to cost at least a $1?
  - russellwolf 8y ago
    Cloud Source Repositories PM here. A project as described here refers to a "Cloud Project" which is the basis for creating, enabling, and using all GCP services including managing APIs, enabling billing, grouping resources, etc. Within a project, one could have tens or hundreds of repositories. With 6 users on a single project, you would pay $1/month total (because the first 5 users are free) and all those users would have access to every repository in that project. I appreciate your feedback that you find the pricing model and project concept difficult to understand. I'll bring this back to the team and we'll look at different ways to improve this.
    - abtinf 8y ago
      Thank you - this explanation is much more clear and I understand now. I’m generally familiar with AWS but haven’t used GCP, so I didn’t have the “Cloud Project” concept.
  - jpatokal 8y ago
    Projects are the fundamental organization unit of GCP. Every resource you create in GCP lives in a project, and users are granted access to projects. https://cloud.google.com/resource-manager/docs/creating-managing-projects https://cloud.google.com/resource-manager/docs/creating-mana... "Project-user" here means that access is counted per project. So if you (x@) use GCR for projects A and B, meaning you check in/out code as x@A and x@B, that's two "project-users". Disclaimer: I work for GCP.

I find the pricing of this service to be incomprehensible, as well as contradictory to “Unlimited private Git repositories for free”. Can anyone explain it?

by abtinf 8y ago

I find the pricing of this service to be incomprehensible, as well as contradictory to “Unlimited private Git repositories for free”. Can anyone explain it?

dragonwriter 8y ago

> I find the pricing of this service to be incomprehensible, as well as contradictory to “Unlimited private Git repositories for free”. You get unlimited private repositories, 5 project users, 50 GB of storage, and 50 GB egress per monthly for free. Monthly overage charges beyond the free quota are $1 per project-user, $0.10 per GB of storage, and $0.10 per GB of egress. So for 10 project-users, 100 GB of storage, and 200 GB of egress in a month, you pay $5 for users, $5 for storage, and $10 for egress, for a total of $20.

abtinf 8y ago
I still don’t get it. What is a “project” and how does it differ from a “repo”? If they are the same thing, isn’t every project/repo going to cost at least a $1?
- russellwolf 8y ago
  Cloud Source Repositories PM here. A project as described here refers to a "Cloud Project" which is the basis for creating, enabling, and using all GCP services including managing APIs, enabling billing, grouping resources, etc. Within a project, one could have tens or hundreds of repositories. With 6 users on a single project, you would pay $1/month total (because the first 5 users are free) and all those users would have access to every repository in that project. I appreciate your feedback that you find the pricing model and project concept difficult to understand. I'll bring this back to the team and we'll look at different ways to improve this.
  - abtinf 8y ago
    Thank you - this explanation is much more clear and I understand now. I’m generally familiar with AWS but haven’t used GCP, so I didn’t have the “Cloud Project” concept.
- jpatokal 8y ago
  Projects are the fundamental organization unit of GCP. Every resource you create in GCP lives in a project, and users are granted access to projects. https://cloud.google.com/resource-manager/docs/creating-managing-projects https://cloud.google.com/resource-manager/docs/creating-mana... "Project-user" here means that access is counted per project. So if you (x@) use GCR for projects A and B, meaning you check in/out code as x@A and x@B, that's two "project-users". Disclaimer: I work for GCP.