Own your workflow. Protect your code.
A private, dedicated forge for Git, Mercurial, and Fossil. Your code is yours — never shared, never mined, never training data.
Git, Mercurial & Fossil — all first-class · Fully dedicated, managed tenant · Your code never shared · Issues, PRs, CI/CD, releases · SSO · Analytics
One forge, three version control systems, entirely yours.
Flexible VCS options
Git, Mercurial, and Fossil are all first-class and native — not a Mercurial shop that tolerates Git, and not a Git forge with a bolt-on. Clone, pull, and push over native HTTP and SSH. The web UI speaks each VCS’s own vocabulary, with unified pipelines across all three. (Git also transparently serves Jujutsu / jj.)
Everything in one forge
Repositories, issues, pull requests with inline review, CI/CD pipelines, releases, SSO, organization management, fine-grained API tokens, and analytics. No third-party tracker, no separate CI service, no identity provider to bolt on. A built-in Git importer brings existing repositories across with full history.
Fully dedicated & sovereign
Your repositories are private to your tenant — never shared, never mined, never used to train AI models. Leafscale runs your forge as a fully dedicated, managed tenant. And you are never captive: a standard REST API, standard-shape webhooks, swappable CI, and native VCS protocols mean leaving takes your history with you.
Screenshots
Everything a team needs, under one roof.
Git, Mercurial & Fossil repos
Native HTTP and SSH. History, blame, tags, and LFS content in the web UI. (Git transparently serves jj.)
Fully dedicated & managed
A dedicated tenant — hosting, upgrades, backups, and monitoring handled for you. Your repositories stay private.
Data residency
When regulation requires it, choose the region and country your tenant runs in. Repos, database, backups, and CI stay in your jurisdiction.
CI/CD pipelines
Define pipelines in .isurus-ci.yml. Docker or Incus executors, encrypted secrets, parallel steps, release publishing.
SSO & identity
OIDC and SAML 2.0, per-instance. Invite-only or auto-provisioning. Fine-grained API tokens scoped to repos, orgs, or roles.
Analytics & reporting
Built-in analytics backed by QuestDB: commit velocity, issue throughput, CI/CD reliability, platform health. No external vendor.
Issue tracker
Hierarchical labels, issue templates, multiple assignees, pinned issues, a three-state workflow, and auto-linking cross-references.
Code review
Pull requests with diff review, inline comments, required approvals, and status checks — linked to your CI and issues.
Import & convert
Point Isurus at any Git repository and it converts to Mercurial on your tenant, full history mapped — or snapshot and start clean.
Unique 3D interface
Dive into ‘The Abyss’ — explore and manage your repositories through a unique 3D Dashboard and Repository Manager.
Speaks your language
The full web UI ships in 25 languages — German, French, Spanish, Japanese, Korean, Portuguese, Russian, Simplified & Traditional Chinese, and more. Each user picks their own.
Expandable
Available add-ons let you expand Isurus as you grow or your requirements change.
We use it ourselves.
Leafscale hosts its own source on an Isurus tenant — and Isurus builds, tests, and ships Isurus through its own CI/CD pipelines. Every release was built by the product you’re evaluating, on the forge it hosts.
Browse Leafscale on Isurus →Security
- API tokens hashed at rest
- Session cookies HttpOnly, Secure, SameSite-configurable
- CI secrets & auth client-secrets encrypted at rest (AES-256-GCM, per-instance master key)
- SSO via OIDC and SAML 2.0
- Fine-grained API token scopes (read/write per resource)
- Admin audit log for privileged actions
Data sovereignty
- Fully dedicated tenant — application, database, and repositories yours alone
- Your code and data are never shared, never mined, never used to train AI models
- No lock-in by design: standard REST API, standard webhooks, plain-YAML CI, native VCS protocols
- Choose your data-residency region and country
Frequently asked
Which version control systems does Isurus support?
Git, Mercurial, and Fossil — all first-class and native, with the same forge features over each. Different repositories can run different VCSs in one instance. Git also transparently serves Jujutsu (jj), since a jj repository is a Git repository server-side.
Is my code private?
Yes. Leafscale runs your forge as a fully dedicated, managed tenant — not a shared multi-tenant pool. Your repositories are private to your tenant, and your code and data are never shared with other customers or anyone else.
Is my code used to train AI models?
No. Never. Nothing in Isurus sends your code to any AI service or training pipeline, and Leafscale does not use customer code or data for model training of any kind.
Does it work with my existing SSO?
Yes, if your SSO provider supports OIDC or SAML 2.0. Common providers — Google Workspace, Microsoft Entra ID, Okta, Keycloak, custom OIDC — work out of the box.
Can I get my data out? How hard is it to leave?
Easy, by design. Repositories clone out with full history over native Git, Mercurial, and Fossil protocols. Integrations use standard shapes — a conventional REST API, de-facto-standard webhooks, and plain-YAML CI. The rest of your tenant’s data exports via standard database dumps.
Can I self-host instead?
For enterprises whose policy strictly requires on-premises deployment, a self-hosted option may be available — ask sales. The dedicated, Leafscale-managed tenant is the standard offering, and delivers the isolation most teams are after without you running any infrastructure.
Ready to try it?
We reply personally — usually within a business day or two.