Makes no sense for me, the repository are just like any other repo, even on personal GitHub accounts, any one can contribute to them, the only difference is GitHub organizations can have members and specific permissions. There can still only be one Vercel user, deploying from the organization, on the same plan as any other normal personal account. This is really annoying for people who are starting open source projects and would like to organize it inside a GitHub organization. Please consdier adding GitHub organization support for the hobby plan!
2 Likes
This is reasonable feedback, I’ve pushed it internally
1 Like
+1 for this, please. Just to keep my stuff organized, I rely on organizations, and vercel’s artificial boundary against that is causing me to rethink the use of v0.dev and vercel for my projects going forward.
1 Like
Hi @jacobparis , Is there any update on the same. As @dukkcc suggested This is really annoying for people who are starting open source projects and would like to organize it inside a GitHub organization.
There do not appear to be any plans to relax this limitation unfortunately
If you have a paid Vercel account you can deploy from as many github orgs as you’re a member of, but free hobby accounts are restricted to personal repositories
EDIT: This actually just changed a day or so ago and I missed the memo
Hobby accounts can now deploy from public organizations. Pro accounts are still required for private orgs though
1 Like
Very recent change! We’ll continue to restrict deployments from private repos on GitHub organizations, but we’re allowing all public repos to support open source projects 
1 Like
Awesome guys! thank you
1 Like
Hi Vercel team,
We’re a small startup using Vercel Hobby plan to build our MVP. Until recently, we could deploy from our private GitHub org repo — now it’s blocked unless we upgrade to Pro.
We understand the limits, but it’s tough for early-stage teams. Would you consider allowing 1 private org repo on Hobby or offering a startup-friendly option?
Thanks — we love Vercel and want to continue using it as we grow
2 Likes
It’s very unlikely this will change unfortunately, organizations have actually been blocked on the hobby plan for a long time already, but there were a few loopholes (old accounts, downgrades after setting up, etc) that remained open until now
You may be able to work around it by transferring the github repo to one of your team’s personal accounts and then you won’t be in an organization so it shouldn’t trigger the block
Otherwise you’ll either have to upgrade to pro or make your org repo public
Or we can just switch to other service. I guess that’s what is the goal here to remove most of us of the platform.
1 Like
We recently open sourced our repo and want contributors to be able to merge their own PRs.
What steps do we need to take to ensure deployments aren’t failing for outside collaborators?
The free tier has progressively been losing features. First we lost the ability to deploy branches, then we completely lost the ability to update our website… This is extortion - you promised to us we will be able to use your free tier until we need certain features, now you are blocking us from updating our website?!
This is not great guys, and it smells like some “feature” that some people in a board room came up with, thinking about “how do we raise profits without actually improving the product”, cause this type of removal of features is exactly what this is.
I can understand changing and evolving the free tier on accounts that are new, but for those you made a promise-to - you should just grandfather the account’s plan and let it continue.
How can we be sure that you are not going to shift the ground under our feet at some point and charge us a bunch of stuff we didn’t want to get charged for? A very bad look, guys, because it breaks our trust in you. We will upgrade, as we need to urgently update our website (how do you call this?!), but we are likely leaving Vercel in a month or 2.