We're building Vault42. Join the waitlist for early access. Join Waitlist

The Frankfurt financial district skyline seen across the river Main at dusk
Enterprise

Source code hosting for organisations that answer for their data

Your code on a dedicated instance in the EU, under EU law, with the assurances your security and compliance teams will ask for.

Talk to us Join the waitlist

Every Enterprise setup is arranged with you individually. This page describes what we offer and how the process works.

Pricing

Enterprise starts at €450 per month, billed annually. The final price depends on what you need:

  • The number of users, agreed per contract
  • Storage and CI capacity
  • Support needs
  • Integrations and network options

Get in touch and we will prepare a proposal for your organisation.

Dedicated instance

The Developer and Teams plans run on a shared platform. Each Enterprise customer gets an isolated Forgejo instance on dedicated virtual machines in the EU, with its own database and storage. Your repositories, users and backups stay separate from those of other customers.

Data and security

  • Hosting. Your instance runs on Scaleway, a European infrastructure provider, in one of its EU regions: Paris, Amsterdam, Warsaw or Milan. Vault42 has no US parent company and no US infrastructure, and will be incorporated in the EU.
  • Encryption. Data is encrypted at rest, including backups. All traffic is encrypted in transit with TLS, including traffic between the servers of your instance.
  • Staff access. Our staff access your data only to handle a support request or an incident, and every access is logged.
  • Backups. Daily encrypted backups, kept for 30 days and replicated to a second EU region. The restore procedure is documented and tested regularly. A restore returns your instance to the most recent daily backup, and your SLA sets the recovery time.
  • Leaving. Your repositories are standard Git and available at any time. When you leave, we provide a full export of your instance, including repositories, issues, pull requests, wikis and users, as a standard Forgejo backup that you can restore on your own server.
  • Data processing agreement. Every Enterprise contract includes a data processing agreement . We also publish our sub-processor list .

Custom domains

Your instance can run on your own domain, such as git.example.com . You add one DNS record, and we take care of the TLS certificate.

Identity provider

Your instance signs users in through your own identity provider, over OpenID Connect or LDAP.

  • Works with Microsoft Entra ID, Google Workspace, Okta, Keycloak, Active Directory and other OpenID Connect or LDAP providers
  • Groups in your provider map to Forgejo organisations and teams
  • Providers that support only SAML, such as AWS IAM Identity Center, connect through an identity broker such as Keycloak, which we add to your instance

Branding and instance settings

  • Your logo and colours
  • Your choice of first page, such as the sign-in page
  • Size limits for repositories, Git LFS, packages and CI artifacts, set for each user or organisation
  • Upload limits and other instance settings that match your policies

Connecting your internal systems

  • Webhooks and API. Notifications for pushes, pull requests, issues, releases and other events, plus a full REST API. Most tools connect through one of these.
  • Issue trackers and wikis. Link Jira, Confluence or another tracker or wiki for each repository. References such as PROJ-123 in commits and pull requests then link to your tracker.
  • Systems inside your network. For Artifactory, Nexus, private container registries and similar systems, run Forgejo runners on your own infrastructure. A runner connects out to your instance, so it needs no inbound access from the internet, and your systems stay inside your network.
  • Cloud accounts. Workflows can request short-lived OpenID Connect tokens that AWS, Google Cloud and Azure exchange for temporary credentials. No long-lived keys are stored in Forgejo. The cloud provider must be able to reach your instance over the internet, so this option does not work with the VPN-only setup under Network access.

Network access

By default, your instance is reachable over HTTPS, and your identity provider controls who can sign in. If you need more, we can add:

  • An IP allowlist for the ranges of your offices and VPN
  • A site-to-site IPsec VPN, so the instance is reachable only from your own network

We include these options in the proposal.

Service level agreement

Each Enterprise contract includes a signed SLA, with terms agreed per contract. The SLA sets the support hours, response times and maintenance windows for your instance.

Migration

Forgejo imports repositories together with their issues, pull requests, labels, milestones, releases and wikis from GitHub, GitLab, Gitea, Gogs and other Forgejo instances. From Bitbucket and other Git hosts, we import the repositories with their full history. We can run the migration for you.

How a setup works

The steps depend on what you need. A typical setup looks like this:

  1. A call about your requirements: users, identity provider, domain, CI, integrations and support
  2. A written proposal with the scope and the price
  3. We set up your instance and agree the configuration with you
  4. You add the DNS record and register an application in your identity provider, and we connect both
  5. If you use your own runners, you install them in your network and we register them
  6. If you want, we migrate your existing repositories

After setup, your named contact stays available for changes and support.

Talk to us Read our security & compliance page