Self-hosted Git infrastructure

Your source.
Your server.
Your rules.

Vellum is a repository browser and Git-over-HTTPS service built as one focused C binary. No framework tower. No separate web server. Just Git, access policy, and an interface people can actually use.

Built by Floof Logic. The private beta is for teams comfortable operating their own infrastructure.

Repository browser Clone · fetch · push Native authentication Auditable access

The point

Git hosting should feel like infrastructure, not a lifestyle.

Vellum keeps the operational surface deliberate: one service owns the browser, Git protocol, TLS boundary, and authorization decisions.

01

One service, end to end

Vellum serves repository pages and Git smart HTTP directly. There is no nginx-to-framework-to-plugin chain to assemble before the first clone.

clientVellumGit repository
02

Real identities

Use system-native PAM authentication and group membership instead of inventing another island of passwords.

03

Repository policy

Grant read or write access per repository, preserve global administration, and keep ungranted projects out of view.

04

Operationally legible

Health checks, access records, bounded logs, certificate checks, and release rollback belong to the product—not an afterthought.

05

Own the boundary

Terminate TLS with Vellum and keep source, credentials, and authorization decisions on infrastructure you control.

The interface

Useful at a glance.
Detailed on demand.

Browse trees, inspect source, review recent changes, copy the correct clone URL, and manage access without turning Git administration into its own project.

Repository browser Vellum native UI
Vellum repository browser showing repository details, branches, clone controls, recent commits, and a source tree.
The same compact interface serves browsing and smart Git operations from the same authenticated origin.

Inside the request

Fewer moving pieces. Clearer responsibility.

A Vellum request crosses a short, inspectable path. Each layer has one job and one owner.

  1. 01

    Authenticate

    The operating system verifies the user through PAM. Vellum never needs a parallel password database.

  2. 02

    Authorize

    Global and per-repository policy determine what the user can see, fetch, or change.

  3. 03

    Serve

    The native browser renders source and history, or Git smart HTTP handles clone, fetch, and push.

  4. 04

    Record

    Security-relevant activity lands in structured, rotating access logs built for human review.

Private beta

Bring a server.
Keep your source.

Vellum is running real Floof Logic repositories today. We are inviting a small number of technically adventurous teams to help shape the public release.