Devs have code review.
Everyone else has Holy Files. 
PMs, designers, and AI agents all ship code now. Mark critical files as @holy and every change requires steward approval before it merges.
Works with every AI coding tool
Zero config, zero vendor lock-in
Rules live in your repo as @holy comments. No dashboard to learn, no YAML to master, no migration if you leave.
Approval where devs already work
Stewards approve in the GitHub PR review flow. No new tool, no context switching, no training budget.
Audit trail for every override
Owner overrides are logged with reason and timestamp. Team plans can export the audit log as CSV.
Who it's for
From seed stage to SOC2 audit
Startups
Move fast, break nothing important
Your PM ships with Claude Code. Your billing logic stays safe. Set up in two minutes, not two sprints.
Scale-ups
Everyone pushes code now
Designers, PMs, and contractors all commit through AI tools. Protect what matters without slowing anyone down.
Enterprise
100 repos. 50 agents. One marker.
Audit trails, owner overrides, and compliance-ready logs. No six-figure contract, no month-long rollout.
See it in action
One comment protects a file forever
Add // @holy to any source file. From that commit forward, every PR that touches it requires steward approval — enforced as a required GitHub check.
A PM builds a feature with Claude Code
The agent pushes a commit touching a holy file
Holy Files blocks the PR with a required check
The steward reviews and approves in GitHub
// @holy steward=@alice
// AI agents: this file is protected.
// Changes require steward approval.
export function processPayment(
amount: number,
currency: string
) {
// ...
}Holy Files
Awaiting steward approval
A protected file has been disturbed.
src/billing/process-payment.ts → steward @alice
@alice approved via PR review
Get started
Protect a repo in three steps
Step 1
Connect GitHub
Install Holy Files on the repos you want protected.
Step 2
Mark a file or folder as @holy
Add an inline marker or a .holy config file directly in the repo.
Step 3
Commit
The rule travels with the code from that point forward.
You're protected.
Connect your first repoPricing
Free early access. Paid plans later.
Sign up with GitHub and use Team features now. You will not be charged during early access.
Now
Early access
Full Team features unlocked while we gather feedback. No card required.
- Unlimited seats & repositories
- Inline @holy markers & .holy configs
- GitHub PR checks
- Steward teams (@handle)
- Audit export & owner overrides
- Early warning mode
Planned
Team
The paid plan we will introduce after early access. Not charged today.
- Unlimited seats & repositories
- Steward teams (same @handle syntax)
- Audit log CSV export
- Email notifications
- Owner overrides & member roles
- Priority support
Enterprise
Enterprise
For orgs that need SSO, SLAs, and compliance packages.
- Everything in Team
- SSO / SAML (contact us)
- Compliance packages (contact us)
- Dedicated support & SLA
- GitHub Enterprise Server (contact us)
Security
We never see your source code
Holy Files reads markers at specific Git SHAs to determine what's protected. Source is not kept as a product datastore; derived scan metadata may be cached briefly to run checks.
No code access
We read @holy markers, not your source. No static analysis, no AI scanning your codebase.
No source datastore
Approvals and audit events live in our database. Repository source is not retained as a product store; scan metadata may be cached briefly for checks.
Transparent permissions
Our GitHub App requests only the permissions it needs: read contents, write checks, read pull requests.
Open marker format
The @holy marker is a plain comment in your code. No proprietary config, no lock-in, fully portable.
FAQ
Common questions
What's the difference between Holy Files and CODEOWNERS?
CODEOWNERS assigns reviewers. Holy Files blocks merges. CODEOWNERS can be overridden by anyone with write access — Holy Files requires explicit steward approval via a required check, and every override is logged.
What GitHub permissions does Holy Files need?
Holy Files reads file contents at specific SHAs to find @holy markers, creates check runs on PRs, and reads PR reviews for approvals. It does not write to your repository contents.
What happens if a steward leaves the company?
Org owners can override unavailable stewards from the dashboard with a required reason. The override is recorded in the audit trail so you always know who approved what and why.
Does this work with monorepos?
Yes. You can protect individual files with inline @holy markers or entire directory trees with .holy config files. Each path can have its own steward.
Does Holy Files store my code?
Holy Files does not keep your repository source as a product datastore. It reads file contents at specific Git SHAs to evaluate markers, and may briefly cache derived scan metadata (such as symbol hashes) to run checks. Approvals, audit events, and account data live in our database.
Can I use this with GitHub Enterprise Server?
GitHub.com / Enterprise Cloud is supported today. GitHub Enterprise Server is available for Enterprise customers — contact us.
Your AI agents are writing code right now.
Do you know what they're changing?
Protect your first repo in two minutes. Free forever for up to five seats — unlimited repositories.