GitNest — private Git hosting with clone and push on osFoundry

Real Git over HTTPS for your workspace repositories, with access tokens you control.

GitNest is osFoundry’s built-in Git host. Every repository in your workspace has a real Git remote you can clone and push to over HTTPS with any standard Git client — no plugin, no export, no second account. Authentication uses workspace access tokens you create and revoke yourself. The repository you clone is the same one the web IDE edits and Maestro reads, so work done on your machine and work done in the workspace are the same history.

Quick answer

Clone and push any workspace repository over HTTPS with standard Git.
Authenticate with workspace access tokens you create, scope and revoke yourself.
Repositories are private to their workspace by default.
The same repository backs the web IDE, so a push shows up in the workspace.
Works with any Git client — the command line, an IDE, or a CI job.

What it is

GitNest is a Git remote that belongs to your workspace. It is not a mirror of a repository hosted somewhere else, and it is not a replacement for public open-source hosting — it is the place your workspace’s own code lives, reachable from your machine with the Git you already use. Because it is real Git rather than an export, the usual commands work unchanged: clone, fetch, branch, push, and any tool built on top of them.

Key capabilities

Smart-HTTP clone, fetch and push using the reference Git implementation.
Per-user access tokens with an expiry date and one-click revocation.
Workspace-scoped authorization — a token only reaches repositories in its own workspace.
Read and write access decided per repository, so a token can be refused a push.
Pushes appear in the workspace, so the web IDE and Maestro see what you pushed.
Published versions are protected: a push that would rewrite one is refused, not silently applied.

How to do it in osFoundry

Create an access token — Open Settings → repository tokens and create one. It is shown once, so copy it then. Give it an expiry — a token that never expires is one you can never stop worrying about.
Copy the clone URL — Open the repository in Code and use the Clone panel. The URL carries your workspace, because a Git client cannot send custom headers and the address has to be self-contained.
Clone it — Run git clone with the URL. Use your token as the password when Git asks; the username can be anything. A credential helper will remember it.
Commit and push as usual — Branch, commit and push with the commands you already use. Nothing about the workflow is osFoundry-specific.
See it in the workspace — The push is reflected back into the workspace, so the branch and its files appear in the web IDE and are available to Maestro.

How osFoundry compares

Capability	osFoundry	Most other tools
Where the code lives	A real Git remote inside your own workspace.	A separate hosting account, linked by an integration.
Getting code out	git clone — the standard command, no export step.	Download an archive, or install a plugin to sync.
Credentials	Workspace tokens you create and revoke, with expiry.	An account password or an OAuth grant to a third party.
Editor and remote	The same repository backs both, so they never drift.	A hosted repo mirrored into the editor, kept in sync by a job.

Use cases

Developer who prefers a local setup: Clones the workspace repository, works in their own editor with their own tooling, and pushes back. The team sees the change in the workspace without anyone exporting anything.
CI pipeline: A build job clones the repository with a scoped token that has an expiry, runs the test suite, and never needs a human account or a personal credential.
Team keeping code off public hosting: Keeps repositories private to the workspace while still working with ordinary Git, instead of trading normal tooling for privacy.

Frequently asked questions

What is GitNest?

GitNest is osFoundry’s built-in Git hosting. It gives every repository in your workspace a real Git remote you can clone and push to over HTTPS with any standard Git client.

Is GitNest a GitHub replacement?

No, and it is not trying to be. GitHub remains the place for public open-source hosting and its surrounding community. GitNest is where your workspace’s own repositories live so you can work on them locally and in osFoundry without moving code between two systems.

Can I use my normal Git commands?

Yes. GitNest speaks the standard Git smart-HTTP protocol using Git’s own reference implementation, so clone, fetch, branch and push behave exactly as they do anywhere else.

Does GitNest support SSH?

Not today — GitNest is HTTPS only. You authenticate with a workspace access token rather than an SSH key.

How do I authenticate?

Create an access token in Settings and use it as the password when Git prompts you. The username is not checked. Tokens are shown once, can be given an expiry, and can be revoked at any time.

What happens when I revoke a token?

It stops working immediately, on the next request. Anything already cloned to a machine stays on that machine — revoking a token ends future access, it does not reach out and delete a working copy.

Are my repositories private?

Yes. Repositories are private to their workspace by default, and a token only reaches repositories in the workspace it belongs to.

Does a push show up in the workspace?

Yes. After a push is accepted, the branch and its files are reflected back into the workspace, so the web IDE shows what you pushed and Maestro can read it.

Can I push to a published version?

No, and the push is refused up front rather than half-applied. A published version is a fixed record; if a push would rewrite one, GitNest rejects it and tells you which branch, leaving your repository untouched.

Can I use GitNest from CI?

Yes. Create a token with an expiry, store it in your CI provider’s secret store, and clone with it like any other Git remote.

Pricing

Hosting a repository is part of your workspace — there is no separate charge for a repository or for the number of them. Clone and push transfer is recorded against your workspace’s usage like other bandwidth.