Deploy from a Git Forge That Only Exists on Tor

A Git forge does not have to be exposed on the public internet to serve a deployment workflow. If your forge is available as a Tor onion service, an Impreza VPS can fetch a project from it through Tor and build the application on the server.

This can help teams keep source-control access separate from the public endpoints used by their applications. The forge remains reachable through Tor, while the deployment still runs on the VPS you manage. For private repositories, connect with a supported HTTP(S) token and grant only the access needed to read the project. SSH-based Git access to onion sources is not supported.

Review a change before it reaches the main deployment

Temporary branch previews give a team a place to inspect a proposed change. A preview can have its own onion address, which makes it reachable through Tor. The address itself does not decide who may open it: by default, Tor users who know the address can reach the service.

When a review should be limited to specific people, create the preview with Tor client authorization and add the intended reviewer clients during setup. Automatic previews created by a Git push remain reachable by Tor users, so choose the restricted option explicitly. Store the generated reviewer key safely because it is shown only once.

Check selected source findings before the build

For supported source deployments, the Impreza Agent can report known dependency advisories from selected lock files and selected patterns that may indicate credentials in source. The report provides finding details without returning source contents or credential values. It is a focused review signal: it does not cover every dependency or secret, inspect the finished container image, block the build, or certify that an application is secure.

Understand the network boundary

Tor is used to fetch an onion Git source. That does not automatically send build dependency downloads, container image pulls, application traffic, or all other server connections through Tor. Plan those connections separately if your project needs a specific network route.

This workflow connects private source hosting with controlled review on a VPS while keeping the scope of each protection clear. For supported versions and setup steps, see the private Git deployment guide and the Tor branch preview guide.