# Free plan build minutes limit on CircleCI

**URL:** <https://discuss.circleci.com/t/free-plan-build-minutes-limit-on-circleci/17012>\
**Category:** Announcements\
**Created:** [October 2, 2017, 1:18pm UTC](https://discuss.circleci.com/t/free-plan-build-minutes-limit-on-circleci/17012 "2017-10-02T13:18:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tom](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/tom/32/27680_2.png) [@tom](https://discuss.circleci.com/u/tom)\
**Post date:** [October 2, 2017, 1:18pm UTC](https://discuss.circleci.com/t/free-plan-build-minutes-limit-on-circleci/17012/1 "2017-10-02T13:18:31Z")

</div>

The free Linux plan on CircleCI has 1,500 minutes of build time available per month: [https://circleci.com/pricing](https://circleci.com/pricing)

We have recently started enforcing the limit. This is the reason you may see:

```auto
Your build was not run - reason code (:org-over-credit-limit)

```

All customers who are affected by this should have received an email in preparation for the change.

Your monthly cycle is based on the date your org was created on CircleCI (not necessarily 1st of the month).

You can upgrade to a paid plan to remove the build minutes limitation.  
If you’re building an Open Source project on MacOS you can [contact us](https://circleci.com/pricing/#faq-section-linux) to request your project be covered by our Open Source plan which will remove the minutes limitation. OSS projects built on Linux do not count towards your usage limit.

The limit is to prevent abuse of the platform so we can provide the best service for everyone.

---

<div class="post-metadata">

**Author:** ![rishimkumar](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/rishimkumar/32/4798_2.png) [@rishimkumar](https://discuss.circleci.com/u/rishimkumar)\
**Post date:** [October 2, 2017, 1:22pm UTC](https://discuss.circleci.com/t/free-plan-build-minutes-limit-on-circleci/17012/2 "2017-10-02T13:22:46Z")

</div>

in complete transparency - we’ve had this limit for at least a year and have only sparingly enforced it on top abusers manually.

The reason we’re trying more systematic enforcement is that we are experimenting with giving all users more features (e.g., bigger machines but limited on usage) and accordingly, we need to prove whether we can actually systematically prevent abuse of the system. We need to balance our desire to get everyone on great CI with what AWS makes us pay them for all the compute… 🙂

---

<div class="post-metadata">

**Author:** ![jgkamat](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/jgkamat/32/13323_2.png) [@jgkamat](https://discuss.circleci.com/u/jgkamat)\
**Post date:** [October 2, 2017, 1:54pm UTC](https://discuss.circleci.com/t/free-plan-build-minutes-limit-on-circleci/17012/3 "2017-10-02T13:54:30Z")

</div>

I’m happy that open source projects don’t have this limitation, I think it’s reasonable to start enforcing it on private repositories though.

Looking forward to the (possible) larger machine changes, though (and forked PR’s on 2.0 Workflows). Keep up the good work!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [June 18, 2018, 11:42am UTC](https://discuss.circleci.com/t/free-plan-build-minutes-limit-on-circleci/17012/4 "2018-06-18T11:42:04Z")

</div>