Complete history & accountability
Every change is committed with an author, a timestamp, and a message. Nothing is ever silently overwritten — you can always see exactly who changed what, and when.
Private, secure version control — built for HartApps
Collaborate at Hart is HartApps' own private version control and collaboration platform: a self-hosted alternative to public code hosts, purpose-built so internal teams and trusted contractors can manage source code with full visibility, full control, and none of the exposure of routing proprietary work through a third party's servers.
What is Collaborate at Hart?
At its core, Collaborate at Hart is a version control system: it tracks every change ever made to a project's files, who made it, and why. On top of that foundation it adds the tools a team actually needs to work together day to day — repositories organized under organizations, branches and merges, in-browser file editing and uploads, issue tracking with threaded comments and @mentions, notifications, personal access tokens for CLI and automation use, and an admin console for managing users, organizations, and system-wide settings.
Unlike public code-hosting platforms, Collaborate at Hart was designed from day one to be private by default. It authenticates exclusively through HartApps' own Keycloak single sign-on, every file is encrypted at rest, and access is always scoped to an organization you've explicitly been added to. Nothing is public unless a repository owner deliberately makes it so — and even then, only organization members can push changes to it.
The result is a code host that feels familiar to anyone who has used a modern version control platform, while keeping every byte of HartApps' intellectual property under HartApps' own control.
Why keep your code in a repository?
A repository is more than a folder of files — it's a living, searchable record of a project's entire life. Here's what that buys you in practice.
Safe experimentation via branching
Try a risky idea in its own branch without touching the working codebase. Merge it in only once it's reviewed and ready — or throw it away with zero cleanup.
Instant rollback
If a change breaks something, you're never stuck. Revert to any prior commit in seconds instead of hoping someone kept a backup copy.
Real team collaboration
Multiple people can work on the same codebase at once. Diffs and merges reconcile everyone's changes instead of overwriting each other's work.
A record of decisions, not just code
Commit messages, issues, and comments capture the *why* behind a change — a searchable history of context that outlives any one person's memory.
Confidentiality through access control
Organization-scoped roles mean only the people who should see a repository can see it — proprietary and client-confidential code stays contained.
One source of truth
A single canonical location for the code, eliminating "final_v3_ACTUAL.zip" email attachments and the version confusion that comes with them.
Faster onboarding
A new teammate or contractor can clone a repository and be productive immediately, with full history available for context on how the project got here.
How Collaborate at Hart keeps that code private
Privacy isn't a setting bolted on afterward — it's the reason Collaborate at Hart exists.
Hosted on HartApps infrastructure
Collaborate runs entirely on servers HartApps controls. Your code never leaves the building to sit on a third-party cloud provider.
Single sign-on, not another password
Access is authenticated through the HartApps Keycloak identity provider. There's no separate Collaborate password to manage, phish, or leak.
Encrypted at rest
Every file is content-addressed by the SHA-256 hash of its contents, then gzip-compressed and encrypted with AES-256-GCM before it ever touches disk.
Organizations & role-based access
Every repository belongs to an organization. Members are readers, maintainers, or org admins — access is explicit, never accidental or implicit.
Audit-logged security events
Sign-ins, role changes, and other sensitive admin actions are written to an append-only audit log that administrators can review at any time.
Soft delete, not instant loss
Deleting a repository doesn't destroy it immediately — it's held in a recoverable state for a grace window before permanent removal.
Ready to get started?
Create your first repository, or browse the Help Center for step-by-step guides on everything from branching to personal access tokens.