Stop fixing broken data by hand
FAIRy checks incoming datasets against your rules before they get submitted and gives contributors a one-page "here's what to fix" report. Local-first. No uploads.
We'll map your 'don't publish without this' rules and show you what your readiness report would look like.
For data stewards, curators, cores, and collections.
| Check | Status | Next Step |
|---|---|---|
| Sample IDs present | PASS | No action needed |
| Dates in ISO format | PASS | No action needed |
| Contact email valid | WARN | Verify email format |
| File naming convention | FAIL | Rename files per standard |
| Required metadata fields | PASS | No action needed |
Saying "this won't pass" shouldn't be miserable. FAIRy gives you rule-based checks, a clear report, and an attestation.
FAIRy Submission Readiness Package
Your intake rules, encoded into a local rulepack plus a one-page readiness report for contributors and an attestation bundle you can attach to deposits.
You get
You walk away with these after the pilot. They're yours.
Your rulepack, encoded
Your required fields, formats, and naming rules are encoded into a FAIRy rulepack that runs locally. You keep it.
One-page readiness report
For each dataset, FAIRy produces a human-readable PASS / WARN / FAIL sheet with "how to fix" text you can send back to contributors.
Language your people will actually listen to
We adapt wording to match how you already tell labs/collectors what's wrong, so you don't get 'what does this even mean?' emails.
Attestation bundle
FAIRy also generates a machine-readable record (timestamp, file hashes, rulepack version) so you can prove what was checked and when.
Who this is for / Not a fit
- Core facility staff and bioinformatics teams who run QC before returning results to labs
- Data stewards and RDM teams who need repository-style preflight checks
- Collections managers handling hundreds of datasets across facilities, herbaria, and archives
- Groups that need to prove consistent QC before deposit for funder/compliance reporting
Not a fit: Individual researchers submitting their own datasets (check out the solo tier instead).
Attestation: Show your due diligence
It's your "we actually checked this" receipt.
Institutions
When a PI asks "who approved this?" six months later, you can point to the attestation: timestamp, file hashes, rulepack version, PASS/WARN/FAIL results. That protects you.
Journals
Some journals require proof of data validation before acceptance. FAIRy's attestation bundle is machine-readable and can be attached to your submission packet.
Grant panels
Funders increasingly ask for evidence of consistent QC practices. Attestation bundles provide a verifiable record you can share with leadership or include in compliance reports.
Start with a Preflight Mapping Session
We'll map your 5–7 "don't publish without this" rules and show you what your readiness report would look like.
Pricing
FAIRy-core
For individual researchers and DIY labs.
- •Open-source validator (local-first)
- •Starter templates & common rulepacks
- •Readiness report (human + JSON)
Includes common, non-custom rulepacks. Custom rulepacks are part of Pilot/Institution.
Download FAIRy-core →Encode your rules
For labs & cores that need their intake codified.
- •Translate your intake policy into a custom rulepack
- •One guided run + readiness report you can forward internally
- •Attestation file (what was checked, when, and by which rules)
Typical turnaround: 1–2 weeks; fixed-price scope.
Request a Pilot Scope →Looking for maintenance, dashboards, SLAs? Talk to us.
| Feature | Community | Pilot | Institution |
|---|---|---|---|
| Custom rulepack | ✖︎ | ✔︎ | ✔︎ |
| Maintenance | ✖︎ | ✖︎ | ✔︎ |
| SLAs | ✖︎ | ✖︎ | ✔︎ |
Frequently asked questions
Do we have to upload our data to you?
No. FAIRy is local-first. You run it on your machine or inside your network. During the Preflight Mapping Session, we can work from column names and examples, you don't have to send us full datasets.
Are we locked in after the pilot?
No. After the pilot, you keep your rulepack, your readiness report template, and your attestation bundle. You can keep using them internally.
Can you update the rules when our policy changes?
Yes. You can edit the rulepack yourself, or we can maintain it for you when required fields / formats / vocabularies change.
Do people have to use the command line to get the report?
FAIRy can run from the command line for power users, but the output is a clean one-page readiness report (PASS / WARN / FAIL with "how to fix") that you can just send around. Most contributors only ever see that report.
Resources for evaluation / deployment
Institution Kit (PDF)
Everything you need for security review and deployment planning:
- Security summary and architecture overview
- Software Bill of Materials (SBOM)
- Deployment options and requirements
- Data handling and privacy policy
- Support expectations and SLAs
Rollout playbook
Recommended workflow for integrating FAIRy into your intake process:
Lab runs FAIRy → Curator reviews → Deposit
"If FAIRy says green, curator fast-tracks metadata review."
This workflow lets labs self-check before submission while giving curators confidence to fast-track datasets that pass FAIRy's validation. The readiness report becomes part of the submission packet, and the attestation bundle provides audit trail.