Skip to content
GitLand

One verified profile for all the code you’ve written.

GitLand combines your GitHub and GitLab accounts, including work you did in private repositories, into one profile you can share. You decide what’s shown. Your code never is.

Three accounts, GitHub personal, GitHub work and GitLab work, drawn as separate areas on a contour map, joined by one outline labelled gitland.dev/alex.

How it works

  1. Connect your accounts

    Create your account with GitHub, GitLab or email. Then connect every Git account you’ve used: personal, work and open source.

  2. Choose what’s shown

    Review each repository. Private ones stay hidden until you pick how much to reveal.

  3. Publish one link

    Share gitland.dev/you. Visitors see what you approved, and who vouches for each part of it.

Private work, shown safely

For a private repository, you choose a disclosure level. GitLand shows the evidence, never the code, the repository name or your employer’s internal details.

What GitLand keeps

  • That you worked on the repository, and when
  • Technologies found in manifests and config files
  • Counts of commits, reviews and merge requests

What GitLand never keeps or shows

  • Source code or diffs
  • The repository name, if you set an alias
  • Commit messages, issue text or internal documentation

Every claim says who vouches for it

Profiles mark each fact with its source, so a reader can tell evidence from description.

Provider verified
Confirmed by the Git provider, for example ownership of a GitHub or GitLab account.
GitLand verified
Derived by GitLand from repository evidence, such as participation, activity period or technology use.
Developer provided
Written by the developer. GitLand has not verified it.