Gitea
Painless, self-hosted Git service for code hosting and collaboration.
Open the official app on gitea.io
This tool is hosted by its maintainers. Click below to open gitea.io in a new tab — it's their official demo.
Browse developer tools →What's next with Gitea?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is Gitea?
Gitea is a self-hosted DevOps platform designed for developers and teams to manage code repositories, collaborate on projects, and automate workflows. It provides a centralized hub for version control, code review, and continuous integration/continuous deployment (CI/CD) pipelines. The tool addresses the need for private, reliable, and customizable code management solutions, particularly for teams seeking control over their infrastructure and data. Gitea caters to both individual developers and enterprise teams, offering features like Git hosting, team collaboration tools, and package registries. Its primary purpose is to streamline software development processes by integrating code management, review, and automation into a single platform, reducing reliance on third-party services while maintaining flexibility and scalability.
How it works
Gitea is an open-source code hosting platform built on Git, enabling teams to manage repositories, track issues, and collaborate on projects. It emphasizes simplicity, performance, and ease of deployment, making it suitable for developers and organizations requiring full control over their code and infrastructure. The platform solves challenges related to code management, team coordination, and automation by providing a unified environment for version control, code reviews, and CI/CD pipelines. Its self-hosted model allows users to deploy it on-premises or via cloud services, ensuring data privacy and customization options. Gitea supports Git-based repositories, enabling users to create, manage, and collaborate on codebases. It includes features like pull requests, code reviews, and issue tracking to enhance team productivity. The integrated CI/CD system, Gitea Actions, allows users to automate workflows such as testing and deployment, compatible with GitHub Actions for familiarity.
How to use it
- 1Choose deployment method: Deploy via Docker, Kubernetes, or a self-hosted server. 2. Install Gitea using the selected method, configuring database settings and storage paths. 3. Create repositories and set up user accounts with access permissions. 4. Enable CI/CD pipelines by defining workflows in the `.gitea/workflows` directory or integrating with external tools. Practical tips: Use Docker for simplicity, configure backups regularly, and leverage Gitea Cloud for managed deployments. For teams, prioritize role-based access controls and integrate with existing infrastructure for workflows.
What it can do
- git hosting
Use cases
Assumptions and limitations
Assumptions
- source: https://github.com/go-gitea/gitea
- license: MIT — free to use
- privacy: Self-hosted — you control your data
Limitations
- Limited third-party integration compared to GitHub or GitLab
- Fewer advanced features for large-scale enterprise workflows
- Steeper learning curve for self-hosted deployments
- Community-driven support may lack enterprise-grade SLA guarantees
- Scalability challenges for extremely large repositories or user bases
Understanding the result
Painless, self-hosted Git service for code hosting and collaboration.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (MIT).
- Built with
- (go-gitea/gitea)
- License
- MIT
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with go-gitea/gitea. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- MIT
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- MIT License
Upstream project
Frequently asked
What is Gitea and how does it differ from GitHub?
Gitea is an open-source, self-hosted code hosting platform offering Git repository management, collaboration tools, and CI/CD pipelines. Unlike GitHub, which is a cloud-based SaaS solution, Gitea allows users to deploy and manage their own instances, providing greater control over data and infrastructure. It shares similarities with GitHub in features like pull requests and issue tracking but lacks some advanced tools found in GitHub Pro or Enterprise plans.
How does Gitea's CI/CD system work?
Gitea's CI/CD system, called Gitea Actions, enables users to define workflows using YAML files stored in repositories. These workflows trigger automated tasks like building code, running tests, or deploying applications when specific events occur (e.g., push to a branch). It is compatible with GitHub Actions, allowing users to migrate existing workflows while maintaining familiarity with the syntax and structure.
How do I set up a private repository?
To create a private repository, log in to your Gitea instance, navigate to the 'New Repository' page, and select 'Private' during creation. Set a name and description, then click 'Create.' Only users with explicit permissions will access the repository. You can manage access via the 'Settings' tab by adding collaborators and assigning roles like 'Maintainer' or 'Writer.'
How does Gitea compare to GitLab and GitHub?
Gitea focuses on simplicity and performance for self-hosted use cases, while GitLab offers a more comprehensive platform with built-in CI/CD, Kubernetes integration, and project management tools. GitHub excels in cloud-native collaboration and third-party integrations but lacks the self-hosting flexibility of Gitea. Gitea is ideal for teams prioritizing control over infrastructure, whereas GitLab and GitHub are better suited for users seeking out-of-the-box features without deployment complexity.
How do I resolve a '404 Not Found' error when accessing a repository?
A '404 Not Found' error typically indicates the repository does not exist or was deleted. Verify the repository name and path in the URL, check if the repository was recently removed, and ensure you have access permissions. If the issue persists, clear your browser cache or contact your Gitea administrator to confirm the repository's existence and your access rights.