Githome

About Githome

What Githome is, how it's built on Cloudflare, who can use it at git.pkgforge.dev, and how to reach the people who run it.

Last updated · View as Markdown

Githome is a private, internal git forge at git.pkgforge.dev. It is compatible with GitHub's API and with gh, and it runs on Cloudflare, with copies kept off Cloudflare. Agents do their work through Git and pull requests like everyone else; people see what the agents did, approve what needs them and follow the whole process. Githome is not a product for sale: there is no plan, no price and no hosted service to sign up for.

Why it exists

GitHub was designed for people. Agents on GitHub borrow a person's token, their pull requests look like anyone else's, and the only limits on them are the ones a team remembers to configure. Githome is a forge where an agent is an account of its own with limits the server enforces, and where moving from GitHub costs an afternoon rather than a rewrite: your workflow files stay in the repository (no run starts here while the forge CI is dormant), and gh and your editor's plain HTTPS clone keep working.

How it's built

  • On Cloudflare, with no servers. A Worker serves the web UI, Git, the REST and GraphQL APIs and MCP; every repository is a Durable Object with its own SQLite database; accounts live in D1 and large objects in R2. See Architecture and Built on Cloudflare.
  • Separate hosts for separate jobs. The core serves git.pkgforge.dev. The superadmin console is its own site, dash.git.pkgforge.dev, with its own passkey sign-in, and each module will serve NAME.git.pkgforge.dev once it is deployed. See Deployment and operation.
  • Mirrored and backed up. Push mirrors copy each repository, with its forge state, to GitHub, Cloudflare Artifacts, GitLab, Forgejo or Codeberg, and backups go to an S3-compatible bucket off Cloudflare once its credentials are set.
  • The forge CI is dormant. git.pkgforge.dev starts no Actions run, no hosted job and no agent sandbox. The Actions code is part of Githome, and the Actions documentation keeps its reference content.

Who can use it

Anyone can browse and clone public repositories at git.pkgforge.dev without an account. A write needs an account, and accounts are by invitation: the superadmin invites each one in the dash and sends the one-time invitation link by hand. Githome sends no email for an invitation, and open sign-up is off. People sign in with a passkey. See Invitations and Passkeys and sign-in.

For AI assistants and search engines

Everything on this site is public and available as Markdown: add .md to any page's address, or send Accept: text/markdown. /llms.txt indexes the site and the documentation, and /llms-full.txt holds all of it in one file. Every site page shows the date its facts were last checked.

Contact

  • Questions and privacy requests: the contact form, for people with an account. Messages reach the superadmin, who reads them in the dash.
  • Bugs and questions about the service: the public tracker, github.com/Azathothas/issues, with the label git.pkgforge.dev. Without an account, this is the way to reach the people who run the instance: until the deployment has its Turnstile keys, the contact form and the report form take messages only from people who are signed in.
  • Security problems: the private report form, as listed in /.well-known/security.txt, for people with an account.
  • git.pkgforge.dev status: /status.
  • Documentation: git.pkgforge.dev/docs.