Roadmap

This is the whole plan, in order, in public.

There are no dates here on purpose. A roadmap with missed dates costs exactly the credibility it was meant to build. The ordering is a commitment; the timing isn't. When something ships, its status changes here — and this file is the same one rendered at /roadmap, so there is no second, friendlier version of the truth.

Every line below is editable by pull request, like everything else in this repo.

Phase 1 — Git hosting · shipped

The part that has to be boring and correct before anything else matters.

  • Users and authentication
  • Repositories
  • Public and private visibility
  • Git over HTTPS
  • Git over SSH
  • SSH key management
  • Basic web UI — repository list, file browser, branches, tags

Phase 2 — The GitCamp basics · shipped

The collaboration surface people expect from a git host.

  • Organizations
  • Teams
  • Permissions
  • Issues
  • Pull requests
  • Comments
  • Webhooks — bring your own CI
  • Releases
  • Full REST API

Phase 3 — A real service · planned

The operational maturity that separates a project from something you'd trust a company to.

  • Billing
  • Storage quotas
  • Usage dashboard
  • Backups
  • Import from any git host — shipped early: GitHub, GitLab, Gitea, anywhere that speaks https, with a choice of the default branch or a full mirror. Migration is the other half of portability, so it did not wait for the rest of this phase.
  • Custom domains
  • Two-factor authentication
  • Audit logs

Phase 4 — Differentiation · planned

  • CI
  • Package registry
  • Git LFS
  • Pages
  • Advanced permissions
  • Deployments
  • Runner infrastructure

Phase 5 — Scale · planned

  • Multiple API servers
  • Multiple git storage nodes
  • Replicated PostgreSQL
  • Object storage
  • Dedicated workers and queues
  • CDN
  • DDoS protection
  • Multi-region backups

What we won't do

Features can be copied. These can't be, without a competitor changing their business — so they belong on the roadmap just as much as anything above.

  • We won't sell your data, or use your private code to train anything.
  • We won't invent proprietary formats. Your repositories are ordinary git repositories. Your metadata has an export path. Nothing here needs GitCamp to be read.
  • We won't build lock-in. Leaving should be a git clone and an export, not a support ticket. If leaving ever gets hard, that's a bug.
  • We won't close the source. You can always run this yourself. That is the ceiling on what we're able to charge you, and we'd rather have that ceiling than not.
  • We won't quietly rewrite this list. Changes to it are commits, in public, with history.