git.bvdl.io is in alpha

Things may not work

Features are incomplete and under active development. Pages can break, pushes and merges can fail, and behaviour can change without warning. There is no uptime guarantee and no support commitment: the service may be restarted, taken offline, or discontinued at any time.

Your data may be removed at any moment

The environment is reset as part of development. A reset deletes accounts, repositories, issues, pull requests, and everything else — without notice and without a way to restore it. There are no backups you can rely on.

Never keep your only copy of anything here. Keep a local clone or a mirror somewhere else, and treat every repository on git.bvdl.io as disposable.

The server is small

git.bvdl.io runs on modest hardware with limited CPU, memory, disk and bandwidth. Pages can be slow, and large or unusual work — a big push, cloning a heavy repository, a burst of API calls — can time out or be refused while the server catches up.

Please keep repositories small, avoid committing large binaries, and don’t point automated jobs or load tests at the service. Capacity limits may be tightened at short notice to keep the platform standing.

Only a handful of people are here

The alpha is deliberately limited to a small group of early users, so the platform is quiet by design. Explore pages, activity feeds and search results will look mostly empty, and there is no community to discover work through yet.

Because the group is small, features are tested by very few people before you reach them. If something looks wrong, it probably is — and you may well be the first to hit it. Telling us is the most useful thing you can do during the alpha.

Your data and activity are reviewed

Everything you store and do here — including private repositories, their contents, issues, comments, and your activity on the site — can be inspected by the people building it, and is used to diagnose problems and improve the product.

Usage is also measured. Page views, the actions you take, Git operations, errors and performance timings are recorded together with your account, and those analytics are read directly by the team to decide what to build and fix next. This is not anonymous aggregate reporting: individual accounts and individual sessions can be looked at.

Do not upload anything confidential, sensitive, or subject to obligations you cannot meet: no secrets, credentials, personal data of others, or proprietary code you are not free to share. Private visibility hides a repository from other users; it does not hide it from us.

Accepting these terms

You accept the points above when you create an account, and they keep applying for as long as you use the service. If you are not comfortable with them, please wait for a stable release. Ready anyway? Create an account.