JJSourcery is a private workspace for developers and teams who want a queryable copy of their GitHub repositories. It mirrors repositories into your own object and metadata stores and serves a jj-powered dashboard for browsing, searching, and automating code operations.

How does the GitHub import work?

You connect GitHub via OAuth, select the repositories you want to import, and JJSourcery clones the full history, branches, tags, and metadata into your private object and metadata stores. The import runs through the CLI and is encrypted at rest.

Is JJSourcery open source?

JJSourcery is developed in the open on GitHub under the MIT OR Apache-2.0 license. Core import, backend, and dashboard code is available for inspection and self-hosting.

What authentication does JJSourcery use?

JJSourcery uses Pocket ID for self-hosted OIDC authentication. You control the identity provider, so credentials and sessions never depend on a third-party SaaS auth service.

Now accepting early users Private workspace

Mirror and browse
your GitHub repos.

JJSourcery imports your public and private repositories into storage you control, then gives you a jj-powered UI to browse files, commits, and diffs. Your history stays intact; your data stays yours.

Start importing Sign in to workspace

Install the CLI in one line

macOS · Linux · Windows (WSL)

curl -fsSL https://jjsourcery.com/install.sh | sh

Free during beta No credit card Self-hosted auth Your own storage

jjsourcery import --from github

$ jjsourcery auth login --provider pocket-id

✓ OIDC session: idp.your-domain.com

$ jjsourcery import \

--from github \

--to r2://your-bucket \

--repo awdemos/jjsourcery \

--preserve-everything

✓ Connected to GitHub API

✓ Cloning 12,847 commits, 38 branches, 142 tags

✓ Indexing into jj change graph

✓ Encrypting tarball and pushing to your object bucket

✓ Indexed into jj change graph

Import complete. Ready to browse.

Built for the open stack

jj Leptos Fly.io Pocket ID

Get the CLI

One command to get started

The JJSourcery CLI is a single static binary. Paste the installer into your terminal, authenticate with Pocket ID, and start importing.

$ curl -fsSL https://jjsourcery.com/install.sh | sh

✓ jjsourcery installed to ~/.local/bin

$ jjsourcery login

Open https://jjsourcery.com/cli/login?device_code=XXXX-XXXX

$ jjsourcery import --from github --repo awdemos/jjsourcery

✓ Import queued

Read the CLI manual

See it in action

Browse the JJSourcery repo inside JJSourcery

The same import and browse flow you would use for your own repos. Files, commits, and diffs rendered by jj.

View source on GitHub

$ jjsourcery import --from github --repo awdemos/jjsourcery

✓ Fetched 12,847 commits

✓ Mirrored 38 branches, 142 tags

✓ Indexed into jj change graph

$ jjsourcery repos browse awdemos/jjsourcery

Opening /app/repo/...

Capabilities

A workspace for your repositories

JJSourcery turns your GitHub repositories into a queryable, self-hosted workspace.

🛰️

Full-history import

Import public and private repositories with branches, tags, releases, and every commit preserved. Your history stays intact in storage you control.

$ jjsourcery repos list --from github

awdemos/jjsourcery → ready

awdemos/jj-cli → ready

awdemos/infra → ready

$ jjsourcery import --all --background

3 repositories queued. Track progress in /app/.

🔐

Private by design

Code lives in your object bucket. Metadata lives in your metadata database. You hold the keys, the backups, and the exit route.

⚡

jj-powered history

Browse files, commits, and diffs with jj as the VCS backend.

🌐

Edge-deployed

Runs on an edge worker and Fly.io for low-latency access, with no cold starts on the dashboard.

🔑

Own your identity

Secure OIDC sign-in with Pocket ID. Bring your own provider, enforce your own policies, and never outsource user trust.

FAQ

Import with confidence

The bottom-line answers technical teams need when importing GitHub repositories into a private, jj-powered workspace.

🚀

Quick start

Import your first repository from the web UI or CLI. Full docs are coming soon; the README and source are available now.

Coming soon

⌘

CLI reference

Every jjsourcery command, flag, and exit code. Browse the CLI source on GitHub.

View CLI source

🤖

Workspace API

Structured, machine-readable endpoints for querying and acting on code.

Browse endpoints

🏰

Self-hosting

Deploy the edge worker, backend, object store, metadata database, and Pocket ID on your own infrastructure.

Ask about self-hosting

Is JJSourcery a GitHub replacement?

No. It is an import and workspace layer. You mirror your repos into storage and metadata stores you control, then browse, search, and build on them. Social coding features like issues and PRs are intentionally out of scope; we focus on the code plane.

What happens to my git history?

Everything comes with you: commits, branches, tags, release metadata, and pull-request history. The import is read-only on the GitHub side, so the original stays untouched while your workspace gets a complete, queryable copy.

Why use jj as the VCS backend?

jj treats version control as a database of changes, not a chain of immutable snapshots. That means rebase-free workflows, first-class conflicts, and operations fast enough for automated tools to run at scale. Git compatibility is built in, so you can still push to any git remote.

Where does my code actually live?

In your object-storage bucket and metadata database by default. The hosted service only routes requests and never holds your repository contents. Prefer local storage? Self-host the backend and point it at a filesystem path.

Can I self-host the whole stack?

Yes. The edge worker, Fly.io backend, object store, metadata database, and Pocket ID auth provider can all run under accounts and infrastructure you control. We publish Terraform/Pulumi-style deployment configs and a reference self-hosting guide.

Do I have to move my whole team at once?

No. Import one repo, try the browser and API, then expand when you are ready. Because jj is git-compatible, you can keep pushing to GitHub as a mirror while you evaluate the new workflow.

What about CI/CD?

Keep your existing GitHub Actions during the transition. In 2026/2027 we are shipping native event hooks so CI can pull from your JJSourcery plane directly, without forcing a rip-and-replace.

How do tools interact with repositories?

Through a typed, auditable API. Tools can query history, read files, propose changes, and run jj operations with deterministic outcomes instead of scraping GitHub pages or guessing at repository state.

jjsourcery login && jjsourcery import

$ jjsourcery login

✓ Device authorized via Pocket ID

$ jjsourcery import --from github --to r2://my-bucket --repos org/critical-service

✓ Fetched 4,182 commits

✓ Mirrored 23 branches, 14 tags

✓ Indexed into jj change graph

Your repository is now mirrored.

Still have questions?

The codebase is open, the roadmap is public, and the maintainers are actively shipping. Open a GitHub issue, join the discussion, or read the architecture spec.

Ask on GitHub View on GitHub

Pricing

Free during beta

JJSourcery is in early access. Import repos, browse history, and use the dashboard at no cost while we build toward paid plans.

Beta

$0 /mo

Unlimited imports, full history browsing, and Pocket ID sign-in. No credit card required.

Unlimited imported repos
jj-powered history browser
Pocket ID sign-in
Community support

Start importing

Paid plans will come later. Self-hosting is on the roadmap.

Mirror and browse your GitHub repos.

One command to get started

Browse the JJSourcery repo inside JJSourcery

A workspace for your repositories

Full-history import

Private by design

jj-powered history

Edge-deployed

Own your identity

Import with confidence

Quick start

CLI reference

Workspace API

Self-hosting

Still have questions?

Free during beta

Workspace tips, jj guides, and automation ideas. No spam.

Mirror and browse
your GitHub repos.