Cloud Git hosting

# Private Git hosting for your team

Deploy Gitea from a marketplace template to host private source code repositories for your team.

[Get started](https://panel.deplomo.com/signup)[Back to marketplace](/marketplace)

## Why deploy Gitea on Deplomo?

Run Gitea with the resources your repositories and CI/CD workloads require, and manage access with your team.

### Lightweight Git hosting built with Go

Gitea is written in Go and is designed to run with modest resources. Requirements vary with repository size and usage.

### Protect access to your source code

Host private Git repositories and manage access for your development team.

### Works with Actions and CI/CD pipelines

Use Gitea Actions to run automated tests and release workflows.

### Manage organizations, teams and access

Create teams, organizations, SSH keys and access tokens, and configure branch permissions.

## Gitea FAQs

Answers to common questions about Gitea, repository migration and private Git hosting:

What is Gitea, and how do development teams use it?

Is Gitea a GitHub alternative for development teams?

How does Gitea compare with GitLab?

How do I migrate GitHub repositories to Gitea?

Does Gitea support SSH and HTTPS?

## Gitea guide: private Git hosting in the cloud

Private Git hosting gives teams control over source code access, repository administration and deployment workflows. Gitea provides a lightweight, self-hosted alternative for projects that need an independent development environment.

### What is Gitea, and how can teams use it?

Gitea is a self-hosted, open-source Git service written in Go. Teams can use it to manage repositories, pull requests, code reviews, issues and branches.

Gitea is designed for lighter deployments than larger platforms such as [GitLab hosting](/marketplace/apps/gitlab) . You can also use [Deploy from GitHub](/support/docs/paas/deploy) to deploy from Gitea and other Git repositories on Deplomo.

### Manual private Git server setup compared with cloud hosting

Setting up Git repositories on a Linux server can involve configuring a web server and database, enabling SSH access, maintaining certificates and planning regular backups. A vulnerable server can put private code at risk.

When international service creation is available, deploy Gitea from a marketplace template and review its network, storage, domain and certificate settings before connecting repositories.

### Compare Gitea on Deplomo with public GitHub and self-hosted GitLab

The table compares technical and operational factors:

<table class="w-full text-start text-sm"><thead class="border-b border-border/80 bg-muted/60 text-xs font-bold text-foreground"><tr><th class="p-4">Feature</th><th class="p-4 text-deplomo-600 dark:text-deplomo-400 font-extrabold">Gitea on Deplomo</th><th class="p-4">Public GitHub</th><th class="p-4">Self-hosted GitLab</th></tr></thead><tbody class="divide-y divide-border/60 text-muted-foreground"><tr class="hover:bg-muted/30"><td class="p-4 font-semibold text-foreground">Source code privacy and access control</td><td class="p-4 font-medium text-foreground">Private repositories on a self-hosted Git service</td><td class="p-4">Repository storage follows the hosted provider’s policies</td><td class="p-4">You manage the service and its maintenance</td></tr><tr class="hover:bg-muted/30"><td class="p-4 font-semibold text-foreground">Resource requirements</td><td class="p-4 font-medium text-foreground">Designed for relatively low resource use; actual RAM depends on workload</td><td class="p-4">Hosted shared service (SaaS)</td><td class="p-4">Resource needs vary by deployment and workload</td></tr><tr class="hover:bg-muted/30"><td class="p-4 font-semibold text-foreground">Git pull and push performance</td><td class="p-4 font-medium text-foreground">Depends on the server location, network route and repository size</td><td class="p-4">May depend on internet connectivity and network latency</td><td class="p-4">May need ongoing Docker cache configuration</td></tr><tr class="hover:bg-muted/30"><td class="p-4 font-semibold text-foreground">SSH and HTTPS access</td><td class="p-4 font-medium text-foreground">SSH access and custom domains with SSL where supported</td><td class="p-4">Supported, subject to server configuration</td><td class="p-4">Configure SSH ports and server access</td></tr><tr class="hover:bg-muted/30"><td class="p-4 font-semibold text-foreground">Pricing and monthly costs</td><td class="p-4 font-medium text-foreground">Fixed monthly EUR package pricing</td><td class="p-4">Some team features or larger repositories may require a paid plan</td><td class="p-4">May require additional hardware resources</td></tr></tbody></table>

A private Gitea instance lets software teams manage repositories in an environment they control. Plan its resources, maintenance and access settings for your team.

### Set up Gitea on Deplomo

When available, use these steps to deploy Gitea:

- **Choose Gitea from the marketplace** When international service creation is available, choose Gitea from the development tools in the Deplomo console.

- **Choose CPU, RAM and storage** Set CPU, RAM and storage based on your repository and team needs.

- **Open the service** After deployment, open the service address and configure SSL where supported.

- **Create a repository or migrate existing code** Sign in to Gitea, create organizations and teams, then use its migration tool to import project code.

### Get started with Gitea on Deplomo

Gitea is a self-hosted alternative to GitHub for teams that want to manage private repositories. Review the service configuration and access controls for your deployment.

Set up a Gitea server on Deplomo for your software team.

## Start Gitea with a click

Automatic installation, dedicated resources and NVMe storage, with optional custom domain support.

[Get started with Gitea](https://panel.deplomo.com/signup)