We have private repository on our organisation account on GitHub and Hobby plan on Vercel, we were able to deploy our preview website as well as the production, but since last 2 days Vercel not allowing us to deploy any kind of deployment, giving this log:
Unable to deploy a commit from a private repository on your GitHub organization to the team on Vercel, which is currently on the **Hobby** plan. In order to deploy, you can:
* Make your repository public or
* Upgrade to Pro. A Pro subscription is required to deploy from a private organization repository.
* Click here to upgrade.
To read more about collaboration on Vercel, click here.
@pawlean I am getting the same issue on a repo I have not moved and have been successfully deploying from for the last 2 years. This seems like a new restriction, and a very surprising one. As mentioned above, Startups will not use this as there are other alternatives without this restriction.
This restriction kicked in the last few days for our projects. This indeed seems like a terrible idea, one that cannot be made in a way such that no loopholes can exist.
Are you going to take away my ability to directly deploy code to an environment? We will just create runners that do that, instead of relying on your repository integration.
Vercel needs to find other ways of squeezing out revenue. This seems like a pretty stillborn idea, without an actual feasible implementation.
I would also like to note that this is essentially rug-pulling pre revenue Micro businesses. Fortunately an emergency migration away from Vercel is doable nowadays.
I would be able to understand this move if only Vercel would do any sort of communication about this.
This was done over the night, without any previous notifications.
Terrible idea, executed even worse.
Such moves lower the trust to hosting service as I expect such moves can be done in future, ie changing that private repos will have to pay extra in future just to be private
Wow, this is hilariously ironic: I was going to be moving to the Pro plan in a month or so after being on the Hobby plan for quite some time, and building my app on Vercel. I’ve been stoked and grateful that Vercel allowed me to grow my new business idea and let it germinate so it would be ready to launch and I could stay on the platform I built it on.
With this restriction, it would force me to move to Pro right at the tail end of it all, but BEFORE I was fully ready to do so.
I’ve now begun looking into alternative hosts to deploy my app. fly.io is looking great.
Pretty rich; in an effort to force people onto Pro, they’re inciting users to look elsewhere.
Everyone knows that Vercel just changed these rules without any announcement.
I’m looking for some options and I want to bring to all of them here.
0 - Pay 20$ for Vercel Pro Plan
1 - Move private repositories to a personal account and deploy from this account, not so good, but it can works, its worse if your team is working with you and you need to invite everyone and recreate some configs.
2 - Deploy into another server, I found these projects that can help: https://opennext.js.org/ - NextJS | Coolify Docs - Next.js | Dokploy - Next.js on AWS with SST | SST
3 - Build up to your own server:
If you have alternatives to help others on the same situation post here, just complaining to staff will not solve our problem, they rules changed and maybe they just want to “clean up” the client base.
For now, following Vercel’s official guide on getting your code deployed through GitHub Actions works - just create a pipeline in Github, instead of using the integration - you can safely remove the repository integration from Vercel’s side as well.
