DataTrails StrawberryRead every asset, draft every event, approve in one pass
Hand a companion the outcome. It reads the DataTrails (formerly RKVST) assets, does the 2-operation version of the job, and stops for your click on anything that changes a record.
Open the asset. Check it against something else. Write the change. Move to the next one. That is the DataTrails (formerly RKVST) afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a asset until you approve it.
What it can do is exactly what DataTrails (formerly RKVST) exposes to an account you authorise and nothing beyond it: 2 operations, no reads and 2 writes. In practice that means it can create an event and create an asset, and work across the assets and events.
The DataTrails (formerly RKVST) API stops at DataTrails (formerly RKVST). A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Where do the assets come from?
In the tab. DataTrails (formerly RKVST) exposes no read operation to a connected account, so a companion opens DataTrails (formerly RKVST) in the session you are already signed into and reads the screens you would.
The assets are what most of this inventory is about, alongside the events. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of DataTrails (formerly RKVST) admin becomes a queue you review.
Which assets wait for your approval?
All 2 write operations wait for you. A companion can create an event and create an asset, and each one is staged on an approval card first: you see the asset, the field and the new value before it lands in DataTrails (formerly RKVST).
Nothing in DataTrails (formerly RKVST) is sent, changed or deleted on your behalf without that click, and a rejected card leaves the asset exactly as it was. The gate is the same one on every surface, described at security.
- Create Event
- Create Asset
What does the recurring assets pass look like?
Yes. Saved as a routine, the DataTrails (formerly RKVST) assets pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the site work, the DataTrails (formerly RKVST) assets sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents