The Grant Space Workbench

The workbench for everything a grant produces.

Work privately across outputs, evidence, lineage, compliance, and team decisions. When the record is ready, publish each approved output with provenance, a persistent identifier, and a version the public can trust.

No grant number needed. Start from files or an award; nothing goes public without your approval.

DATASETFAIR

Coastal salinity survey, 2019–2024

ark:/99999/ro.example · v3
MODELFAIR

Tidal-mixing emulator weights

ark:/99999/ro.example · v1
CODEdraft

salinity-pipeline (reproducible)

ark:/99999/ro.example · v2

From active project to trusted record

One place to assemble, verify, and release.

  1. 01
    Assemble

    Start from an award or your own files. The Workbench brings publications, data, software, people, and grant context into one project record.

  2. 02
    Work and verify

    Search the whole grant, ask cited questions, follow lineage, record decisions, and clear a funder-aware FAIR and compliance punch list.

  3. 03
    Release

    Approve what goes public. Each release is versioned, citable, machine-readable, and linked back to the award and the evidence behind it.

One file is enough to begin. Open a Workbench

Seven views, one grant record

The team and the public use the same evidence.

Switch between a clear visual workspace and canonical source metadata at any time. Project-wide Copilot answers from the Grant Space and cites the records it used.

  1. 01
    Outputs

    Working files and public records.

  2. 02
    Copilot

    Project-wide answers with citations.

  3. 03
    Search

    Find evidence across the whole grant.

  4. 04
    Lineage

    See inputs, reuse, and relationships.

  5. 05
    Compliance

    Turn mandates into a release gate.

  6. 06
    Collaborate

    Keep people, decisions, and follow-ups together.

  7. 07
    History

    Release, cite, export, and inspect versions.

One record model, every artifact

Deposit any output.

Datasets

Tabular, imaging, sensor. Checksums and schema captured on deposit.

Code

Snapshotted repositories with an environment lock for re-execution.

Models

Weights, cards and eval traces, versioned alongside their training data.

Protocols

Step-by-step methods, forkable and citable in their own right.

Why now

Every major funder now mandates open data and code, but the work still happens across lab drives, repositories, spreadsheets, and reporting portals. A registry only sees the end. The scarce thing is a workbench that helps the team reach a trustworthy record: versioned, licensed, evidenced, and linked to the work it enabled.

For funders & institutions

See every output an award produced.

Grant spaces roll all outputs up to the award that funded them, with FAIR compliance visible at a glance.

Explore grant spaces

Frequently asked questions

What is a Grant Space?
A Grant Space is a project workbench for everything a grant produces. The team works privately across outputs, evidence, lineage, compliance, and decisions, then publishes each approved output into one citable, FAIR, machine-readable record.
Do I need a grant number to start?
No. You can start uploading your working files straight away. If you do have a grant number, we also assemble what's already published under it — publications, datasets, and software from OpenAlex, DataCite, and Crossref (plus the full NIH RePORTER record for NIH awards).
What can I do with my files once they're in?
Every file is previewed and profiled in your browser. AI drafts a title, description, keywords, and a licence for you to approve; you can build charts in the Chart Studio, run SQL and AI-guided analysis, export metadata in every standard schema, and draft your data-availability and methods statements. Your raw data never leaves your machine.
Is the data open and machine-readable?
Yes. Published Grant Spaces are public, carry schema.org JSON-LD and a citation in plain text and BibTeX, expose each output's metadata in DataCite, Dublin Core, CodeMeta, and Croissant, and are queryable by agents via a Model Context Protocol (MCP) endpoint.
How is funder compliance determined?
A funder-aware engine checks open access (and PubMed Central for NIH) and data sharing against the award's mandate, producing a score and a punch list — computed by the platform, not self-reported.

Get started

Open a workbench for your next grant.

Start from the award or whatever is already on the lab drive. Organise the work in private, then approve exactly what becomes part of the public record.