Getting started

This is the shortest real path from nothing to a repository with your code in it. It uses plain git — there is no extra tooling to install.

1. Create an account

Sign up at neosource.dev/signup. Signups are open; there is no waitlist or invite code.

Signup is rate-limited to five accounts per source IP per hour, which only matters if you are creating several at once.

Already have an account? Log in.

2. Create a repository

Go to /new. You need a name and a visibility:

• Public — anyone can read it.
• Private — only you and the people you grant access.

Your repository then lives at https://neosource.dev/<owner>/<repo>.

The same page can import an existing repository from a public Git URL instead of starting empty — see Importing from GitHub.

3. Set up authentication

Pick one. Both are managed at /settings/developer.

SSH key

Add your public key on that page, then use the SSH URL. This is the usual choice for day-to-day work.

Personal access token

Create a token on the same page and use it over HTTPS. When Git prompts for credentials:

• Username — anything. It is ignored.
• Password — your token.

Tokens are fine-grained and expiring; repo:write on the repository you are pushing to is enough. See Authentication and tokens for scopes, expiry and rotation.

4. Push

Both URL forms are shown on the repository page.

# HTTPS — the .git suffix is required
git remote add origin https://neosource.dev/<owner>/<repo>.git

# or SSH — the .git suffix is optional
git remote add origin ssh://git@neosource.dev/<owner>/<repo>.git

git push -u origin main

Caution

Over HTTPS the .git suffix is required — a URL without it returns 404. Over SSH it is optional.

Pushing an existing project is the ordinary sequence, with nothing neosource-specific about it:

cd my-project
git remote add origin https://neosource.dev/<owner>/my-project.git
git push -u origin main

5. Look at it

Open https://neosource.dev/<owner>/<repo>.

View	Path
Code browser	/<owner>/<repo>, plus /tree/… and /blob/…
Commits	/<owner>/<repo>/commits/<ref>
A single commit	/<owner>/<repo>/commit/<oid>
Pull requests	/<owner>/<repo>/pulls
Issues	/<owner>/<repo>/issues
Actions (CI)	/<owner>/<repo>/actions
Operations	/<owner>/<repo>/operations
Settings	/<owner>/<repo>/settings/general

Using jj instead

If you use jj, it works against the same URLs with no extra configuration, because jj speaks Git:

jj git clone https://neosource.dev/<owner>/<repo>.git

You never have to. Git is the default and fully first-class — see Protocols: Git and jj.

Next steps

• Set up CI — workflows go in .neosource/workflows/, not .github/workflows/. That catches nearly everyone once.
• Importing from GitHub — bring an existing repository across.
• The storage engine — what is underneath.
• Project status — what is and is not ready.

About the neo CLI

neosource has a command-line client, neo, but it is not distributed yet — there is no released binary, install script, or package. Everything on this page works with plain git and the web UI, which is the supported path today. If you come across neo commands in other material, treat them as forward-looking until there is a way to install it.