JJSourcery is a sovereign, AI-native workspace for developers and teams migrating from GitHub. It imports repositories into your own object and metadata stores and serves a Rust/jj-powered dashboard for browsing, searching, and agent-driven code operations.

How does the GitHub migration work?

You connect GitHub via OAuth, select the repositories you want to migrate, and JJSourcery clones the full history, branches, tags, and metadata into your private object and metadata stores. The migration runs through a Rust 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 migration, 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 Sovereign workspace

Escape GitHub.
Own your code plane.

JJSourcery is the AI-native workspace for teams migrating off GitHub. Move repositories, history, and identity into a private, Rust- and jj-powered plane you control — then let agents work on it.

Start migrating 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 migrate --from github --sovereign

$ jjsourcery auth login --provider pocket-id

✓ OIDC session: idp.your-domain.com

$ jjsourcery migrate \

--from github \

--to r2://your-bucket \

--repos awdemos/jjsourcery \

--preserve-everything

✓ Connected to GitHub API

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

✓ Rewriting into jj change graph

✓ Encrypting tarball and pushing to your object bucket

✓ Indexing symbols for semantic search

Migration complete. You own every byte.

Built for the sovereign stack

Rust jj Leptos Fly.io Pocket ID

Get the CLI

One command to get started

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

$ 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 migrate --from github --repos awdemos/jjsourcery

✓ Migration queued

Read the CLI manual

Capabilities

A workspace built for 2027

Migration is just the start. JJSourcery gives you a modern, agentic, fully ownable alternative to GitHub.

🛰️

One-click, no-loss migration

Import public and private repositories with branches, tags, pull requests, releases, and every commit preserved. Your history stays intact; the lock-in does not.

$ jjsourcery repos list --from github

awdemos/jjsourcery → ready

awdemos/jj-cli → ready

awdemos/infra → ready

$ jjsourcery migrate --all --background

3 repositories queued. Track progress in /app/.

🔐

Sovereign 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-native history

Browse files, commits, and diffs through a next-generation VCS backend that treats history as a queryable graph.

🤖

Agent-ready workspace

Semantic search, machine-readable APIs, and deterministic jj operations give AI agents a codebase they can reason about.

🌐

Edge-deployed

Runs on an edge worker and Fly.io for sub-50ms access anywhere on Earth, 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.

Docs & FAQ

Migrate with confidence

The bottom-line answers technical teams need when moving off GitHub to a sovereign, Rust- and jj-powered workspace.

🚀

Quick start

Migrate your first repository in under five minutes from the web UI or CLI. Docs are coming soon.

Coming soon

⌘

CLI reference

Every jjsourcery command, flag, and exit code. Explore the source for now.

View CLI source

🤖

Agent API

Structured, machine-readable endpoints for agents that need to query and act 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 a migration and workspace layer. You import 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 owning the code plane.

What happens to my git history?

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

Why jj instead of git?

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 agents 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. Migrate 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 webhook sync and native event hooks so CI can pull from your JJSourcery plane directly, without forcing a rip-and-replace.

How do agents interact with repositories?

Through a typed, auditable API and a semantic code index. Agents 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 migrate

$ jjsourcery login

✓ Device authorized via Pocket ID

$ jjsourcery migrate --from github --to r2://my-plane --repos org/critical-service

✓ Fetched 4,182 commits

✓ Mirrored 23 branches, 14 tags

✓ Indexed for semantic search

Your repository is now sovereign.

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

Pay for sovereignty,
not seat licenses

No per-user tax. No data ransom. Start free during beta, then scale by what you store and run — not by how many teammates you invite.

Starter

Free

For solo hackers and open-source maintainers.

$0 /mo

Up to 5 migrated repos
jj-powered history browser
Pocket ID sign-in
Community Discord support

Start for free

Recommended

Pro

Beta price

For indie teams who outgrew GitHub's terms.

$5 /workspace /mo

Unlimited migrated repos
Semantic code search
Webhook sync to GitHub
1 TB object storage included
Priority support

Migrate now

Sovereign

Self-hosted

For orgs that can't let code leave their perimeter.

Custom

Everything in Pro
Run backend on your own Fly.io / metal
Bring your own S3-compatible store
Custom OIDC / SCIM
Dedicated engineering support

Talk to us

Why teams are leaving GitHub for JJSourcery

Per-user fees

Own

Your object bucket

Rust

Backend & CLI

Native VCS plane

You're using the beta

Escape GitHub. Own your code plane.