Your own GitHub · one native service

Your own GitHub.
No separate
web server.

Vellum is the server: one focused C binary serves the repository browser and Git smart HTTP directly. Script-assisted installation and upgrades keep the operational surface small, while clone, fetch, push, and access control stay familiar.

Built by Floof Logic for teams that want to own their source without adopting another platform to operate.

No separate web server One native service Script-assisted install Low overhead

The point

The useful parts of GitHub. Almost none of the stack.

Vellum keeps installation, operation, and maintenance deliberate: one service owns the browser, Git protocol, TLS boundary, and authorization decisions.

01

No web-server stack

Vellum is the server: repository pages and Git smart HTTP come directly from the same native service. No nginx-to-framework-to-plugin chain to install, configure, patch, and debug.

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

Low-overhead by design

Script-assisted installs and release upgrades, health checks, bounded logs, certificate checks, and rollback keep routine operation predictable.

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 on modest hardware. We are inviting a small number of technically adventurous teams to help shape the public release.

No spam. We’ll only use this to follow up about Vellum.