Skip to content
CodeQuay

Who it's for

Built for teams that answer for their code

Different companies and public bodies, one shared need: knowing who can do what with the code, and being able to prove it.

Project isolation: a member of the Portal project sees its repositories; the Payroll project, which they don't belong to, doesn't exist for them: it doesn't appear in lists, searches or the API, and the direct URL returns 404.

SMBs

For SMBs that build software in-house

Code is a business asset, yet it often lives on a forgotten server or on a service one person picked years ago. CodeQuay gives you clear rules and verified backups without needing a dedicated team.

Typical needs

  • Nobody in the company has time to run a git server
  • You need to know the code is safe and recoverable
  • A European tool from a European company

What you get with CodeQuay

  • Nightly backups and an automatic restore test every week

  • Main branches protected for everyone, with no silent exceptions

  • Credentials blocked at push time, before they turn into an incident

  • Developed in Italy by arimaslab, with data hosted in the EU

Software agencies

For software agencies working with multiple clients

Every client has its own projects, its own consultants and its own confidentiality requirements. CodeQuay keeps projects strictly separate and makes releases traceable.

Typical needs

  • One client's code must never be visible to people working for another
  • External contributors who join and leave projects
  • Delivered versions that must stay identical over time

What you get with CodeQuay

  • Full isolation: non-members can't even see that a project exists

  • Roles per organization, project and repository, with per-user restrictions

  • Immutable release tags: the v2.4.0 you delivered stays v2.4.0

  • Tokens with mandatory expiry for pipelines and integrations

Public sector and regulated industries

For the public sector and regulated industries

Government bodies, healthcare, finance, energy: where the question isn't just whether the code is safe, but whether you can prove it. CodeQuay produces the evidence you need.

Typical needs

  • Data and vendor under European jurisdiction
  • Traceable access and changes for GDPR and NIS2
  • Development rules that apply to external vendors too

What you get with CodeQuay

  • Instances in EU data centers, an Italian company, no third-party tracking

  • Append-only audit log, denied attempts included

  • Protections enforced by the server for everyone, vendors and admins included

  • Standard git format: no vendor lock-in

Decision makers

Everyone finds their answer

  • CTOs and engineering leads

    Development rules the team can't bypass in a hurry, traceable releases, migration from GitHub without stopping CI.

  • IT managers

    Backups with tested restores, alerts and system status on one page, sign-in with company accounts.

  • DPOs and compliance

    Data in the EU, a tamper-proof access log, evidence ready for audits and inspections.

Why CodeQuay

What sets CodeQuay apart

All strengths

Developers focus on code. The server enforces the rules.

Create your account and start free. For a dedicated instance or a custom contract, contact us: the people who build CodeQuay will get back to you.

Start free Contact us