Deploy your repo to your own Cloudflare account — you keep ownership.
Paste a repository, YGIT analyzes it, connects your accounts, and deploys. No middleman host. No lock-in.
Free forever·Open source·Your Cloudflare account, your infra
New deployment · YGIT
Five steps, in order, no detours
This is the actual sequence YGIT runs — not marketing copy.
Same five steps, without leaving your terminal.
The web flow is the easiest way to start today. The CLI is in development, for repos you deploy often, or workflows you want to script and run in CI.
- Same account connections, no browser round-trip
- Scriptable — drop it into your own build or release pipeline
- Open source, same as the rest of YGIT
YGIT isn't a website builder, a host, a CMS, or a control panel.
Those products keep your site running on their infrastructure, under their terms. YGIT connects to accounts you already control and deploys there — so nothing about your project depends on YGIT staying online.
That's also why YGIT is free forever: it never pays for your infrastructure, so it never needs to charge you for it.
What changes when the infrastructure account is yours?
YGIT, Vercel, and Netlify all start from Git. The meaningful difference is who operates the production account, who bills you, and what a handoff requires.
Prioritizing cost visibility, portability, and direct ownership.
You receive infrastructure charges from Cloudflare on your own account.
You pay Vercel for plan seats, add-ons, and metered usage.
You pay Netlify through its plan and usage-credit model.
You keep the GitHub repo and the Cloudflare Pages project in accounts you control.
You keep your Git repo; moving the live deployment and platform settings requires migration.
You keep your Git repo; moving the site and Netlify-specific configuration requires migration.
You keep working in the repository you connected.
You connect a GitHub, GitLab, Bitbucket, or Azure DevOps repository.
You connect a repository and Netlify deploys from it.
The Pages project is created inside your Cloudflare account.
The project runs as a Vercel project owned by your selected Vercel team.
The site belongs to a Netlify team, even when that team contains only you.
You deploy into the client’s Cloudflare account, so the runtime starts under their control.
You can transfer the project to another Vercel team; it remains on Vercel.
You can transfer the project to another Netlify team; it remains on Netlify.
“Partial” means the option is supported, but a platform account, transfer, or migration is still part of the handoff.
Nothing hidden in the deploy path
The full pipeline — analysis, account connection, deploy — is public. Read it, fork it, run it yourself.
Built with
Built free, because these are free
YGIT doesn't run its own servers for your site. It exists because these platforms give developers a generous free tier to build on — this project stands on top of that.
GitHub
Free repositories, GitHub Apps, and Actions runners — the entire account-connection and CI layer YGIT relies on.
GitLab
Open-source tooling and free CI minutes that shaped how YGIT's own pipeline is built and tested.
Cloudflare
Pages, R2, and DNS on a genuinely free tier — the actual infrastructure every YGIT deployment runs on.
YGIT is free forever because these platforms are. We don't host your site — they do, on your account.
Deploy your first repo
Create an account and connect GitHub — it takes about two minutes.