Your Anonymous Git Server on a VPS: Gitea/Forgejo, No KYC

Your Gitea or Forgejo instance lives on a no-KYC KVM: 4 GB ECC at the floor, SSH keys for access, a token for signup, coin for invoices. Core $4.80/mo annual.
Your Gitea or Forgejo instance lives on a no-KYC KVM: 4 GB ECC at the floor, SSH keys for access, a token for signup, coin for invoices. Core $4.80/mo annual.
12 locations · 19 coins · SLA 99.95% · no KYC · public canary
VPS from $4.80* — Core on the annual term (list $6/mo), one invoice for 12 months, no auto-charges. Dedicated with IPMI from $39.20/mo. Crypto invoice, no KYC.
Launch nowWhy keep the forge on your own server
Gitea and Forgejo are lean forges that speak HTTP and SSH, small enough to live on a KVM slice kept under your hand: repositories, retention and access rules all stay yours. A quiet instance asks for roughly 1 GB of memory, so the catalog floor already clears the bar — Core (2 vCPU / 4 GB ECC / 80 GB NVMe / unmetered 1 Gbps / $4.80/mo annual) across twelve locations. An account opens from a 32-character token with no inbox behind it, or from an email-password pair, and payment runs in coin alone. At no point does the flow ask for a passport, a selfie or a phone.
Sizing memory against the catalog plans

A forge serving one person or a small team sits close to 1 GB RSS once running. The catalog carries no 1 GB plan, so that demand lands on the entry SKU and scales upward from there:
| Scenario | Memory required | Matching VPSbit plan |
|---|---|---|
| Solo dev or a handful of users, SQLite | 1 GB will do | Core — 2 vCPU / 4 GB ECC / 80 GB NVMe / unmetered 1 Gbps / $4.80/mo annual |
| Compact team, heavier mirroring | ~2–4 GB | Core — 2 vCPU / 4 GB DDR5 ECC / 80 GB NVMe / unmetered 1 Gbps / $6/mo list |
| CI runners sharing the box | ~8 GB+ | Prime — 4 vCPU / 8 GB DDR5 ECC / 160 GB NVMe / unmetered 2.5 Gbps / $12/mo list |
Every plan ships with L3/L4 DDoS filtering, PTR records are editable straight from the panel, and nested virtualization is enabled — so the forge can sit inside Docker, a route the Forgejo docs describe in detail. Should CI runners and mirror farms outgrow a single slice, a dedicated server fits under the same invoice flow: Forge starts at $39.20/mo annual-eff, whole Ryzen 9 9950X cores, ECC and IPMI included.
Git over SSH, with no personal inbox involved
Your legal mailbox has no role here. The panel identity and the git transport are treated as separate layers:
- A VPSbit account keyed to a token. Sign up using the 32-character hex token without attaching any address, then keep that token offline the way you would a recovery code. The Core SKU and the coin invoice match the email route exactly.
- Keys, not inboxes, for SSH. Create the keypair with an empty comment —
ssh-keygen -t ed25519 -C "" -f ~/.ssh/nvps_gitea— and paste its public half into the panel. Log in as root (or as a user you made) with that key alone. - Forge accounts that need no inbox. Add the initial admin from the server itself, disable open sign-ups, and keep each account's email blank or a placeholder — Gitea and Forgejo both operate happily without mail.
- SSH transport, not HTTPS with a password. Register a deploy key carrying no identity string, and remotes will read
git@YOUR_IP:org/repo.git. Make sure nothing in the key comment traces back to your name.
ssh-keygen -t ed25519 -C "" -f ~/.ssh/nvps_gitea
ssh -i ~/.ssh/nvps_gitea root@YOUR_IP
apt-get update
apt-get install -y git sqlite3
# Gitea or Forgejo: install from the project docs (upstream binary or a distro package).
# Public git-hosting marketplaces are not a source to clone from.
install -d /var/lib/gitea /etc/gitea
# Once the server first boots: disable open registration in the admin settings.
How anonymous VPSbit is lays out the whole threat picture — IP, payment chain, logs. The token-versus-inbox trade-offs sit in best no-email VPS, and the floor price in cheap VPS from $4.80.
The configuration we advise
Plan: Core — 2 vCPU, 4 GB ECC, 80 GB NVMe, $4.80/mo annual; that is the catalog floor answering the forge's 1 GB appetite. Location: pick whichever of the twelve cities sits nearest your collaborators — the SKU itself does not change between them. Backups stay inside the same posture: a nightly dump of the SQLite file over SSH to a second location costs nothing extra, and a mirror — Gitea and Forgejo both pull upstream repositories on their own schedule — gives a second copy without a second provider. Renewal is the same coin invoice; nothing about year two reintroduces identity — the token still opens the panel, the keys still open the transport.
Gitea or Forgejo on your own VPS from $4.80/mo — token signup, KYC out of the picture.
Deploy CoreWill 1 GB of RAM cover Gitea or Forgejo?
Yes, as long as the forge serves a person or a small team over SQLite. The cheapest SKU, Core, ships 4 GB of ECC for $4.80/mo annual — comfortable headroom above the 1 GB the process actually needs.
Is SSH access and git push possible with no personal email?
Yes. Open the panel with a token instead of an address, generate SSH keys whose comment stays empty, create forge accounts with no verified mailbox, and move code over SSH — never HTTPS paired with a password.
Is KYC demanded for a git server VPS?
No. Neither signup nor renewal ever asks for a passport, a selfie or a phone; invoices clear in crypto or from prepaid balance.
Does picking Gitea over Forgejo alter the plan?
No. At this hardware class both run comfortably on SQLite and install from their project docs onto the same Core image; what separates them is governance and bundled tooling, never the sizing.
Primary sources
Ready to launch?
Build the box — VPS or bare metal — create the password, pay the invoice that follows.