Web data
that stays alive.
Tell Grava what you want to track. It collects the data into a table and keeps it up to date.
From a public page to your own table.
Choose what to collect. Review the rows. Keep the source and history as your data changes.
Start with a public page and the columns you need. Grava collects the rows into a table you can review.
- $150kSep 1fieldnote.example/careerschanged
- $145kAug 4fieldnote.example/careers
- $145kJul 7fieldnote.example/careers
Run held. Nothing published. Your table still shows Monday's salaries.
Recipe v4 is live. Policy stays on “ask me”.
Your datadoesn’t sit still.
Every row keeps its source, history, and checks. Grava keeps refreshing and checking your data while you work.
Keep your data fresh.
Set the schedule. Grava handles the updates.
Keep bad updates out.
Only updates that pass checks reach your table.
See what changed.
Compare past values, with sources and dates included.
Stay in control of fixes.
Grava proposes a fix. You decide whether to apply it.
Your table.
Ready for your next task.
Connect Claude Code, Cursor, or Codex to read your rows, compare the data, and request updates. Keep working in the agent you already use.
You pay for updates that pass.
One credit per page checked in a passing update. If a check fails, the update is held and you aren’t charged.
- Mon, Sep 1312 pages checked, passed312 credits
- Tue, Sep 2312 pages checked, passed312 credits
- Wed, Sep 3Check failed, update held0 credits
- Thu, Sep 4312 pages checked, passed312 credits
What data are you tired of collecting by hand?
Start with a public page and the columns you need. We’ll help you build your first dataset and set its update schedule.
Build your first dataset