Skip to content
Self-hosted · open source · free

Your code, your reviews, your infrastructure.

Jithub is a complete, self-hosted developer platform — git hosting, pull requests, issues, an npm-compatible package registry and static Pages. Everything GitHub gives you, running on hardware you control.

No credit card. Runs anywhere Docker does.

your terminal
$
All in one place:GitPull requestsCode reviewIssuesProjectsPackagesPagesWebhooks2FA
Code review

Review that actually flows

Open a pull request and get a fast, focused review experience: rich diffs, inline conversations, suggested changes and the merge strategy your team prefers.

  • Inline comments, threads and suggestions
  • Required approvals & branch protection
  • Merge or squash, your choice
  • Linked issues that close on merge
acme/app · Pull request #42
MergedAdd rate limiting
- app.use(routes)
+ app.use(rateLimit())
+ app.use(routes)
Nice — can we make the window configurable? @maintainer
Plan & track

Plan work on boards you can drag

Turn issues into a plan. Group work into columns and reorder or move cards with native drag-and-drop — labels, assignees and milestones included.

  • Drag-and-drop kanban boards
  • Issues, labels, milestones & reactions
  • Assignees and cross-references
  • Task lists with live progress
acme/app · Project board
Todo
Dark mode
CSV export
In progress
Rate limiting
Done
Login
Webhooks
Packages

Your own package registry

Publish and install versioned packages from your own instance with a registry that speaks npm — no extra service, private by default when linked to a private repo.

  • npm publish / npm install out of the box
  • Token auth via your .npmrc
  • Versions, integrity & download stats
  • Scoped packages for orgs
packages · @acme/ui
@acme/ui
v2.3.0 · npm
npm install @acme/ui
2.3.02.2.12.1.0
Pages

Ship sites straight from a branch

Publish documentation or a marketing site from any branch. Pages are served from a sandboxed origin, so published code can never read your session.

  • Publish from any branch or /docs
  • Sandboxed origin (CSP isolation)
  • Custom 404 & nested routes
  • Live the moment you push
/pages/acme/app/

Everything in the box

No add-ons, no marketplace, no per-seat upsells. One platform from the first commit to a published release.

Real git, over HTTP & SSH

Clone, push and branch with the git client you already use — no lock-in, no proprietary protocol.

Pull requests & reviews

Diffs, inline review threads, suggestions, required approvals and merge or squash.

Issues, labels & milestones

Triage work with assignees, labels, milestones, reactions and cross-references.

Drag-and-drop projects

Plan on kanban boards with cards you can reorder and move across columns in real time.

Built-in package registry

An npm-compatible registry — npm publish and npm install straight from your own instance.

Pages: static hosting

Publish a site from any branch, served in a sandboxed origin so it can never touch your session.

Code search & insights

Grep across a repo, jump to any file, blame lines and read contribution and activity graphs.

Secure by default

Private repos, access tokens, 2FA, branch protection and webhooks — on infrastructure you own.

Security you can audit

Your data stays on hardware you control, and every sensitive surface is locked down by default.

  • Private repositories
  • Scoped access tokens
  • Two-factor authentication
  • Branch protection rules
  • Signed webhooks
  • Sandboxed Pages hosting
public repositories
0

public repositories

developers
0

developers

packages published
0

packages published

From commit to ship

A single, coherent workflow — no context-switching between five different tools.

  1. 1

    Push your code

    Clone and push over HTTPS or SSH — bring the repos you already have.

  2. 2

    Review & merge

    Open pull requests, leave inline reviews and merge with confidence.

  3. 3

    Publish packages

    Ship versioned artifacts to your own npm-compatible registry.

  4. 4

    Go live with Pages

    Serve docs and sites straight from a branch — sandboxed and instant.

Frequently asked questions

Is Jithub really self-hosted?

Yes. Jithub runs as a single container you deploy on your own server. Your repositories, packages and data never leave infrastructure you control.

Does it work with the regular git CLI?

Completely. Clone, fetch and push over HTTPS or SSH with the standard git client — Jithub speaks the real git protocols, no plugins required.

Can I publish private npm packages?

Yes. Jithub ships an npm-compatible registry. Point your .npmrc at your instance with an access token and use npm publish / npm install as usual; packages linked to private repositories stay private.

How are Pages sites kept safe?

Published Pages are served from an opaque, sandboxed origin (CSP sandbox), so the static HTML and JavaScript can never read your Jithub session or act on your behalf.

What about access control and security?

Private repositories, scoped access tokens, two-factor authentication, branch protection rules and signed webhooks are all built in.

How much does it cost?

Jithub is free and open source. You only pay for the server you run it on.

Ready to own your workflow?

Spin up repositories, invite collaborators, publish packages and ship Pages — all on your own Jithub.