Developer Tools · head to head
Cortex vs Gitea

Cortex
Developer Tools
Internal developer portal that scores service ownership and maturity rather than just cataloguing services
- From
- On request
- Free plan
- No

Gitea
Developer Tools
Self-hosted, open source Git service with issues, CI/CD and package hosting
- From
- Free
- Free plan
- Yes
The short version
- Gitea is an MIT-licensed, self-hosted Git platform.
- Gitea is free; Cortex prices on request.
- Only Cortex lists service catalogue; only Gitea lists time tracking on issues.
- Where Gitea falls short: self-hosting means you handle installation, upgrades and backups yourself.
- Prices and features on this page were last checked on 20 November 2026.
How do Cortex and Gitea differ?
Cortex and Gitea differ on starting price (On request against Free), pricing model (Quote against Open-source) and free tier (No against Yes). Only the attributes on which Cortex and Gitea actually diverge.
Identical on both: category (Developer Tools).
Not yet recorded: founded for Cortex.
Which features does each one have?
They share no listed features; 8 appear only for Cortex and 7 only for Gitea. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Cortex
- Service catalogue
- Scorecards
- Initiatives
- Self-service templates
- Query language
- Eng intelligence
- Integrations layer
- On-call and ownership mapping
Only in Gitea
- Git repository hosting with pull requests and code review
- Issue tracking with labels, milestones and kanban boards
- Gitea Actions CI/CD compatible with GitHub Actions workflows
- Package registry supporting more than 20 package types
- Time tracking on issues
- Webhooks and API for chat and external CI integrations
- Enterprise SAML single sign-on and audit logs
What is each one used for?
Gitea is most often brought in for self-hosted source code hosting. The jobs each tool is most often brought in to do.
Cortex
- A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Gitea
- An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Gitea
- Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Gitea
- Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Gitea
Gitea
- Self-hosted source code hostingnot Cortex
- Private Git server on small hardwarenot Cortex
- CI/CD with GitHub Actions style workflowsnot Cortex
- Internal package registrynot Cortex
- On-premises hosting for regulated teamsnot Cortex
Where do Cortex and Gitea fall short?
Gitea's most cited limit: self-hosting means you handle installation, upgrades and backups yourself. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Cortex
- Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first
- The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything
- Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue
- It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves
- Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract
Gitea
- Self-hosting means you handle installation, upgrades and backups yourself
- Enterprise plan online payment requires a one-year commitment
- Gitea Cloud pricing is not published on the pricing page
- Enterprise features such as SAML SSO and audit logs are not in the free edition
How much do Cortex and Gitea cost?
Cortex is priced on request; Gitea is free to use. Plan by plan below, from each vendor's own pricing page.
Cortex
On request- CortexOn request
- Service catalogue and ownership mapping
- Scorecards and initiatives
- Self-service templates
Gitea
Free- Open Source (self managed)Free
Which should you pick?
Choose Cortex if
- You need service catalogue.
- You work on Web, API.
- You also want scorecards.
Choose Gitea if
- You need git repository hosting with pull requests and code review.
- You want to start without paying.
- You work on Linux, Windows, macOS, Web.
- You also want issue tracking with labels, milestones and kanban boards.
Questions people ask
- Is Cortex or Gitea better?
- Neither clearly leads. Cortex starts at On request and Gitea at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Cortex or Gitea?
- Gitea has a free tier; the other does not. Paid plans start at On request for Cortex and Free for Gitea.
- Does Cortex or Gitea run on more platforms?
- Cortex runs on Web, API. Gitea runs on Linux, Windows, macOS, Web.
- Can I use Gitea for free?
- Yes. Gitea has a free tier, so you can try it without paying. Cortex starts at On request.
- What is Cortex best used for?
- Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what Gitea is typically brought in for.
- What can Cortex do that Gitea cannot?
- Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Gitea covers Git repository hosting with pull requests and code review, Issue tracking with labels, milestones and kanban boards, Gitea Actions CI/CD compatible with GitHub Actions workflows, Package registry supporting more than 20 package types.
Answered from the vendors’ own pages
Cortex: How is Cortex different from Backstage?
Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.
Gitea: Is Gitea free?
The Open Source edition is free to self-host under the MIT licence, with unlimited users and repositories. An Enterprise edition is charged per user per month.
SourceCortex: Is pricing published?
No. Cortex requires a sales conversation and prepares a custom proposal.
Gitea: What is the relationship between Gitea and Gogs?
Gitea began in 2016 as a fork of Gogs. The developers forked it because the Gogs repository was controlled by a single maintainer and they wanted a community-driven model.
SourceCortex: Can it self-host?
It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.
Gitea: Which platforms and databases does Gitea support?
The vendor lists Linux, Windows, macOS, FreeBSD and Kubernetes on x86 and arm64. Supported databases are SQLite, MySQL, PostgreSQL, TiDB and MS SQL.
SourceCortex: What is the main adoption risk?
Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.
Gitea: Does Gitea include CI/CD?
Yes, Gitea Actions is built in and is compatible with GitHub Actions workflows. Enterprise adds Kubernetes autoscaling runners.
SourceRelated pages
Other head to heads
- Cortex vs Backstage
- Cortex vs OpsLevel
- Cortex vs GitHub
- Cortex vs Spacelift
- Cortex vs Earthly
- Cortex vs Atlantis
- Cortex vs SonarQube
- Cortex vs Envoy
- Cortex vs Depot
- Cortex vs Istio
- Cortex vs Nix
- Cortex vs Buildkite
- Cortex vs Azure DevOps
- Cortex vs Bitbucket
- Cortex vs Daytona
- Cortex vs Helix
- Cortex vs Nx Cloud
- Cortex vs Pants Build
- Cortex vs GitLab
- Cortex vs Jenkins
- Cortex vs Soketi
- Cortex vs Kubernetes
- Cortex vs Penpot
- Cortex vs Jitsu
- Cortex vs Coder
- Cortex vs Distroless
- Cortex vs Frappe
- Cortex vs Visual Studio Code
- Cortex vs GitHub Copilot
- Cortex vs Docker
- Cortex vs Terraform
- Cortex vs Postman
- Gitea vs Backstage
- Gitea vs OpsLevel
- Gitea vs GitHub
- Gitea vs Spacelift
- Gitea vs Earthly
- Gitea vs Atlantis
- Gitea vs SonarQube
- Gitea vs Envoy
- Gitea vs Depot
- Gitea vs Istio
- Gitea vs Nix
- Gitea vs Buildkite
- Gitea vs Azure DevOps
- Gitea vs Bitbucket
- Gitea vs Daytona
- Gitea vs Helix
- Gitea vs Nx Cloud
- Gitea vs Pants Build
- Gitea vs GitLab
- Gitea vs Jenkins
- Gitea vs Soketi
- Gitea vs Kubernetes
- Gitea vs Penpot
- Gitea vs Jitsu
- Gitea vs Coder
- Gitea vs Distroless
- Gitea vs Frappe
- Gitea vs Visual Studio Code
- Gitea vs GitHub Copilot
- Gitea vs Docker
- Gitea vs Terraform
- Gitea vs Postman
