Open source. Off the conveyor.

Your project.
Your rules.

Your project is more than your code.
Why leave the rest trapped on a platform?

Your code, collaboration, and agent memory—together in Git. Work locally, choose your infrastructure, and keep your project yours.

A small CLI. A bigger idea. Open beta.

Two people rescue their green project boxes from a conveyor leading into a giant purple platform monster.
Three people work together to carry their green project box.

01 / A small act of rebellion

Take the whole
thing with you.

Git made code portable.
Let’s bring the collaboration along.

Issues, decisions, and discussions are part of your project, too. Hubnot records signed collaboration facts in Git refs and exchanges them through an ordinary Git remote.

No Hubnot service. No Hubnot database. No new platform you have to move into.

Bring the project. Leave yourself an exit.

Change platforms.
Keep the context.

Take more than your code. Bring the work, the conversations, and the decisions along. Work locally. Choose your host. Keep your options open.

People carry their green project boxes between a server, a friendly cloud, and a laptop.

Migration adapters: GitHub · GitLab · Forgejo / Codeberg · Gitea · Bitbucket Cloud · Azure DevOps

Supported content and migration direction vary by provider.

Find your way out ↗

02 / A lot fits in a little box

Same project.
All the pieces.

Open it up. There’s more in here than source files.

ONE PROJECT. NO LOOSE ENDS.

PICK A PIECE TO EXPLORE ↓

The code is already home.

Your source stays in Git. Hubnot adds signed collaboration alongside it, under refs/hn/*, using the same remote as transport.

Read about the protocol ↗

03 / Less platform. More project.

Built on Git.
Made to move.

One small command: hn.

Initialize a device identity. Open an issue. Synchronize collaboration refs with your remote. The project’s collaboration becomes something you can carry.

Read the getting-started guide ↗

Syncing an unfamiliar remote? The guide explains explicit replication selections and budgets.

your-project / a quick start

# In your existing Git repository

$ hn init --name "My device"
$ hn identity public

# Make the work part of the project
$ hn issue open \
    --body "Bring the whole project along" \
    "Get off the conveyor"

# Exchange collaboration through Git
$ hn sync origin

Illustrative commands · requires an installed hn executable

NO HUB REQUIRED.

For people. For agents. For the whole project.

New session.
Same project memory.

Your next agent shouldn’t have to start from scratch. Carry decisions and handoffs with the project, and put your own CI workers on the checks.

A woman and friendly robot assistants share a green box of project memories and run checks at a testing bench.

Remember the why.

Give the next session the context to keep going.

Put your checks to work.

Your pipelines. Your workers. Results that travel with the code.

Meet memory and CI ↗

04 / And then, back to work

A little less dependency.
A lot more possibility.

Work locally. Collaborate through a remote you choose.
Keep the decisions alongside the work that made them matter.

Three people work together at a desk with their own green project boxes.

05 / A friendlier kind of cloud

Hosting is
a choice.

Keep the cloud.
Lose the dependency.

A useful cloud is a choice, not a dependency. Work locally or share through a compatible Git host. Keep your project close, wherever you take it.

Explore your options ↗
A person relaxes on a friendly cloud with their green project box.
MIT LICENSED · OPEN BETA

Your projects are yours.
Your code is yours.
Your infrastructure is optional.

Ready to unpack a different way of working?

Hubnot is in open beta. Check the release notes for compatibility, platform support, and known limitations.