Home / Solutions / Dev sandbox / CI
Workload playbook

Dev sandbox and self-hosted CI on a VPS

Docker, Forgejo and runners on a throwaway KVM. Nested virt. About a minute after the crypto invoice confirms.

BitCloudVPS dev sandbox VPS - root KVM for CI and experiments
Short answer

Rent a VPS, install Docker and Forgejo from their docs, and destroy the box when the job is done. We do not keep the disk after you delete.

What people actually run

Docker docs plus Forgejo (or GitHub-compatible runners) is the usual lab. Nested virt is on. Pay with USDT so CI spend is boring.

Business $24/mo (6 vCPU / 16 GB DDR5) is the production size. Crypto invoice, no KYC.

Launch now

Playbook

From invoice to a runner
  1. Starter for a toy. Plus / Business for runners. Dedicated if steal shows up.
  2. Install from Docker docs and Forgejo.
  3. Amsterdam if the team is EU. Delete the VM when finished.

Limits

Do not mine on shared KVM as a business. Do not scan the internet from a sandbox we can attribute.

Sizing a CI runner by job shape, not by vibes

Match the plan to what a job actually does. Compile-and-test microservices: Starter $8.50/mo (2 EPYC 7443P cores, 4 GB ECC, 60 GB NVMe) runs Forgejo plus one runner honestly. Docker-in-Docker, Postgres or Redis services in the pipeline: Plus $13.50 (4 vCPU, 8 GB, 120 GB) — RAM is the constraint, not cores. Parallel runner fleets or monorepo builds with big caches: Business at $30 list / $24 yearly (6 vCPU, 16 GB DDR5, 240 GB NVMe). Throwaway compile boxes cost $3/mo effective on Nano's flat $36/yr. Nested virtualization is on everywhere if a job needs its own VM, and the /64 IPv6 block on every plan keeps parallel runners from exhausting v4 egress. Unmetered ports mean artifact pushes and registry pulls never meter; ECC RAM means a flaky bit is not your debugging session. No KYC, token-only signup if you skip email, deploy in about a minute. Deploy in 60 seconds

Ephemeral infrastructure as a payment problem

Sandboxes die often, and the billing model should follow. Month-to-month at list price fits genuinely short-lived boxes: no commitment, destroy when the sprint ends. The quarter term takes 10% off, the year 20% — but a yearly sandbox you abandon in March is not a discount, it is a donation. Payment is where BitCloudVPS differs from card-billed clouds: 19 crypto assets, USDT across seven networks for a stable internal 'compute budget', XMR when the spend should not sit on a transparent chain, and no KYC or corporate card approval anywhere in the flow. Snapshots cover pre-change states, reinstall wipes in minutes, and deleting the VM deletes the disk — there is no hidden retention product to opt out of. The limits are the AUP's, not the billing's: no mining farms on shared KVM, no scanning the internet from a box that traces back. Open checkout — no email needed

Where the limits are (October 2026)

Keep the threat model precise. Anonymous-adjacent hosting removes the host-side identity trail: token-only signup, optional email, no KYC review, crypto invoices that record a txid rather than a name. It does not blind the host to traffic it must carry, it does not make a logged-in panel session anonymous, and it does not protect workloads that identify themselves — an admin login from your home IP defeats the whole design. Exact limits of no-KYC anonymity. OPSEC guide. Full checklist. Payment-side note: chain analysis happens on public blockchains, not at the host. Coin choice and network choice are your OPSEC knobs, and the checkout keeps 19 of them open.

Custom ISO?

Yes.

KYC for CI?

No.

Can a CI runner build Docker images on BitCloudVPS?

Yes. Every VPS is KVM with nested virtualization enabled, so Docker-in-Docker and buildkit work on Starter and up. For pipelines that also run database services, Plus ($13.50, 8 GB ECC) is the realistic floor; Starter handles builds without sidecar containers.

Can I pay for a sandbox with USDT on TRC-20?

Yes. USDT is accepted on seven networks — TRC-20, ERC-20, BEP-20, Polygon, Arbitrum, Optimism and SPL — alongside 18 other assets including BTC and XMR. The network choice changes nothing on the invoice: same plan price, same discounts, no KYC step.

Is Forgejo or Gitea allowed on the sandbox?

Both are ordinary self-hosted software and fully allowed on any plan. Forgejo's docs are the usual install path, and a single-user forge fits even on Nano at $3/mo effective — add a runner and Starter's 4 GB becomes the honest minimum.

What does a sandbox VPS cost?

The Nano plan lists at $5.49/mo, or a flat $36 per year — an effective $3/mo. If you need more headroom, Starter is $8.50/mo with 2 vCPU on an EPYC 7443P, 4 GB ECC RAM and 60 GB NVMe, also with unmetered networking.

What does the host actually know about me?

Whatever you hand over: a signup token, an optional email address, the invoice you paid and the service traffic. No ID documents, no phone number, no KYC step exists to hand anything else over.

What won't an anonymous VPS protect against?

Self-inflicted links: personal logins from a home IP, leaked cookies, services that publish your address, and on-chain patterns that tie wallets together. The server removes one identifier; it does not fix operational mistakes.

Primary sources

Ready to launch?

Configure a VPS or dedicated server, set a password, then pay the invoice.

Network

Edge RTT

Uptime · 36h

Complaints · 36h

Pick a city