Companies that use Gitea

Source: Analysis of job postings that mention Gitea (using the Bloomberry Jobs API)

My analysis shows that Gitea purchasing decisions are primarily driven by DevOps Engineers (35%), Software Engineers (18%), and System Administrators (12%), with Engineering Managers (8%) and Platform Engineers (7%) also playing significant roles. These buyers are predominantly in technical infrastructure and development teams, focused on building self-hosted, automated CI/CD pipelines and managing internal development tools. Their strategic priorities center on automation, security integration, and maintaining control over their source code management infrastructure without relying on external SaaS platforms.

Day-to-day users are hands-on technical practitioners working across the full DevOps lifecycle. They use Gitea alongside tools like Jenkins, Terraform, Ansible, ArgoCD, and Kubernetes to manage source code, trigger automated builds, and coordinate deployments. Many postings describe responsibilities like "administering and supporting critical development tools and integrations" and maintaining "self-hosted Git platforms" as core infrastructure. Users are implementing GitOps workflows, managing container deployments, and integrating Gitea into broader platform engineering efforts.

The pain points reveal a strong desire for independence from commercial providers and the need for security-focused development practices. Organizations seek "self-contained, deployable solutions" and emphasize "air-gapped environments" and "on-premises infrastructure." One posting specifically mentions the goal of "becoming more independent from Google," while another describes building "unified, greenfield observability and monitoring frameworks." Companies value Gitea for its ability to integrate seamlessly into regulated, high-security environments where data sovereignty and complete infrastructure control are non-negotiable requirements.

Source: Analysis of Linkedin bios of 3,755 companies that use Gitea

I noticed that Gitea users are predominantly technical shops building custom software and digital solutions for clients or developing their own products. These aren't SaaS unicorns or enterprise software giants. They're software development consultancies, embedded systems firms, game studios, IoT specialists, and companies building vertical-specific platforms. Many describe themselves as creating "tailor-made" or "custom" solutions, and there's a strong presence of companies working on hardware-software integration, from embedded firmware to VR systems to industrial automation.

These are predominantly small to mid-sized companies, typically between 10 and 50 employees based on the LinkedIn data. The funding information is telling: most show no external funding at all, with only a handful having raised seed rounds under $5 million. They're bootstrapped or organically grown businesses, not venture-backed rockets. The maturity varies, but many were founded in the 2010s and describe themselves as "established" while maintaining "startup character." They're past survival mode but nowhere near enterprise scale.

Source: Analysis of tech stacks from 3,755 companies that use Gitea

I noticed that companies using Gitea are overwhelmingly self-hosting oriented organizations that prioritize infrastructure control and operational independence. The presence of Element, Rocket.chat, and Mattermost (all self-hosted communication platforms appearing 300-1000x more frequently) reveals these companies deliberately choose to run their own infrastructure rather than rely on SaaS providers. They're likely technical organizations, dev tool companies, or infrastructure-focused businesses that view data sovereignty and customization as competitive advantages.

The pairing of Gitea with Portainer makes perfect sense because both tools serve teams managing their own containerized infrastructure. If you're self-hosting your Git repositories, you're almost certainly running Docker containers and need orchestration tools. Similarly, the strong correlation with Grafana and Zabbix tells me these companies take monitoring seriously. They're not just self-hosting for ideology, they're running production systems that require robust observability. The Rocket.chat connection is particularly revealing because it suggests these teams want their internal communications to live on infrastructure they control, consistent with the broader pattern.

The full stack reveals these are product-led, engineering-driven companies, likely at early to mid-stage growth. They're not enterprise sales organizations with massive budgets for Salesforce and marketing automation. Instead, they're building technical products where the engineering team has significant buying power and architectural influence. They optimize for cost control, customization, and avoiding vendor lock-in rather than convenience.