CLAIMR — The Digital Ownership Platform

THE OWNERSHIP MANIFESTO

Every file has an owner. The question is: is it you?

For too long, ownership has been an afterthought — a metadata field nobody checks until something breaks. Files sit unclaimed. Directories belong to ghosts. Entire hierarchies are owned by users who left the company three years ago.

CLAIMR exists because ownership is not a detail. It's the foundation. The first question any system asks isn't "what is this file" — it's "who does it belong to?" We believe that question deserves a real answer, delivered instantly, propagated recursively, and enforced unconditionally.

This is ownership, finally owned.

CAPABILITIES

SIX TRANSFER PRIMITIVES.
TOTAL OWNERSHIP CONTROL.

Every feature built to answer one question: who owns this?

👤

Dual-Entity Transfer

Transfer both user and group ownership in a single atomic operation using the OWNER:GROUP syntax. Change just the user, just the group, or both — one command, total control.

claimr root:staff /assets

🌳

Recursive Propagation

The -R flag cascades ownership changes across entire directory trees. Every file, every subdirectory, every nested asset — claimed in one sweep. Deep ownership, instantly.

claimr -R admin:team /project

🔗

Symlink Intelligence

Choose how symbolic links are handled during transfers. --dereference follows the link to claim the target. -h claims the link itself. You choose what ownership means.

claimr -h deploy:ops /link

🎯

Conditional Transfers

The --from flag transfers ownership only when the current owner matches your specification. Surgical precision — no accidental claims, no collateral damage.

claimr --from=old:team new:team /data

📋

Reference Cloning

With --reference, clone the ownership of any existing file onto your target. No need to look up UIDs or group names — just point to the source of truth and inherit.

claimr --reference=template.conf /new

📡

Transfer Transparency

The -v flag provides real-time diagnostics for every file processed. -c reports only when changes are made. -f silences errors. Full control over signal-to-noise ratio.

claimr -v root:root /etc/config

ARCHITECTURE

FOUR STEPS TO CLAIM

A radically simple pipeline for instant ownership transfer.

Declare the Owner

Specify the new owner as a username or numeric UID. Optionally append a colon and group name to transfer group ownership simultaneously.

Select Your Targets

Pass one or more files, directories, or entire hierarchies. Use -R for recursive claims. Set -H, -L, or -P to control symlink traversal behavior.

Set Conditions

Optionally lock the transfer to specific current owners with --from. Enable --preserve-root to protect the root filesystem. Safety and precision, by design.

Transfer Executes

Ownership changes propagate instantly. Every file touched, every group updated, every claim recorded. Verbose mode gives you full visibility. Silent mode gives you peace.

PRICING

OWN AT EVERY SCALE

From personal file systems to enterprise infrastructure.

Tenant

Free

For hobbyists exploring ownership

50 transfers per day
Single-file ownership
User-only transfers
Community support

Start Free

THEY CLAIMED. THEY CONQUERED.

"We had 14,000 files owned by a contractor who left in 2019. CLAIMR's --from flag let us conditionally transfer every single one without touching anything else. Finished in 0.3 seconds."

Raj Krishnamurthy Head of Infrastructure, DataVault

"The recursive flag changed our deployment pipeline. One command, and the entire /var/www tree belongs to the deploy user. No scripts. No loops. Just ownership, transferred."

Elena Whitfield Staff SRE, NimbusCloud

"I used to spend 20 minutes figuring out UIDs and GIDs. CLAIMR's --reference flag means I just point to a correctly-owned file and say 'make it like that.' Revolutionary."

Tomás Aguilar DevOps Lead, Buildcraft

"We evaluated every ownership platform on the market. CLAIMR was the only one that understood that OWNER:GROUP is a primitive, not a feature. It's the foundation of our entire permissions layer."

Nadia Patel CTO, PermissionStack

THE TEAM

THE OWNERS OF OWNERSHIP

Ada Okonkwo

CEO & Co-founder

Former identity systems architect at Google. Realized every security incident starts with the question "who owns this file?" and nobody had a good answer.

Adaeze Mwangi

CTO & Co-founder

PhD in distributed ownership models from Stanford. Wrote the recursive propagation engine on a redeye flight. It's never been slower than 0.4ms.

Aisha Koroma

Head of Transfers

12 years running permission infrastructure at AWS. Believes that unclaimed files are the single biggest liability in modern computing. She's right.

FAQ

QUESTIONS. ANSWERED.

What's the difference between CLAIMR and just changing file permissions?

Permissions determine what you can do. Ownership determines who you are. CLAIMR handles the identity layer — the OWNER:GROUP assignment that every permission check depends on. Without ownership, permissions are meaningless.

How does the OWNER:GROUP syntax work?

Pass user:group to set both. Pass user: (colon, no group) to set the user and change the group to the user's login group. Pass :group to change only the group. Pass user alone to change only the owner. It's the most expressive ownership syntax ever designed.

Does recursive mode follow symlinks?

By default (-P), no — we don't traverse symbolic links. Use -L to traverse all symlinks to directories, or -H to traverse only command-line argument symlinks. Three modes for three levels of intent.

What does --from do exactly?

The --from=CURRENT_OWNER:CURRENT_GROUP flag makes the transfer conditional. Ownership only changes if the current owner and/or group match what you specify. It's a guard clause for ownership — surgical precision with zero collateral.

Can I accidentally change ownership of the entire root filesystem?

Not with --preserve-root enabled. This flag prevents recursive operations on /. It's your safety net. For enterprises, we recommend making it the default. Because some claims should never be made.

OWNERSHIP.
TRANSFERRED.

THE OWNERSHIP MANIFESTO