What we arebuilding next.

    Running today

    6 stages, all in the app now

    • Get data in

      Any table in · Generate records with AI · Column types and duplicates

    • Write the contract

      Allowed values and synonyms · Values proposed from your data · Ratchet safety fields

    • Run it

      Rules before AI · Validated AI answers · Receipts on every value · Unchanged records skipped

    • Curate

      Review queue · Hand edits that lock · Hold records back

    • Publish

      Immutable releases · Similar-item ranking · Ranking checks

    • Serve

      A tool your agent calls · MCP and REST · Keys you can limit · Export to CSV

    You can try all six in the playground, on a catalog you pick.

    Building next

    In this order. Not available yet

    • Photos and PDFs in

      Menus, labels and spec sheets arrive as images far more often than as spreadsheets. Today they have to be typed up first.

    • Pull requests for your data

      Change preview with a safety diff

      Swapping a model is a one-line change that can quietly rewrite thousands of records, the scariest deploy in a safety-critical product. So treat it like code: rerun a sample, show the diff, block it if a single safety flag would be lost. It ships once a person approves.

    Named, not started

    After those. No date

    • Connectors for databases, sheets and storage

      Read records from where they already live instead of exporting a file. Needs stored credentials, which is real security work.

    • Drift alerts

      Tell the owner when a field's distribution moves, before a caller notices.

    • Golden sets for values

      A held-out set of known-correct values, so a contract edit can be scored rather than eyeballed.

    • Usage metering and billing

      Self-serve plans. Today every workspace is on the same early-access limits.

    • Load rating certificate

      A signed statement of what a release was checked against, for whoever has to sign it off.

    These are written down so we can say no to them out loud. Each one answers a problem a customer only has at volume, and nothing is started until the two above are done.

    Need one of these sooner than we have it? Tell us which. It is the clearest signal we get about what to build.