The collection work, done and queued for one look
Fauna exposes 3 operations and a companion can work all of them: import a GraphQL schema, execute a GraphQL query and read a from fauna collection. Anything that changes a record waits for your click.
Open the collection. Check it against something else. Write the change. Move to the next one. That is the Fauna afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a collection until you approve it.
What it can do is exactly what Fauna exposes to an account you authorise and nothing beyond it: 3 operations, 1 read and 2 writes. In practice that means it can import a GraphQL schema and execute a GraphQL query, and work across the collections, graphql queries and graphql schemas.
The Fauna API stops at Fauna. 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 collections come from?
1 of the 3 operations is a read.
Your account, not a guess at it: a companion can read a from fauna collection, and the full list below is the whole list, with nothing inferred from Fauna's documentation.
The collections are what most of this inventory is about, alongside the graphql queries. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of Fauna admin becomes a queue you review.
- Read From Fauna Collection
Can it change a collection without asking?
All 2 write operations wait for you.
A companion can import a GraphQL schema and execute a GraphQL query, and each one is staged on an approval card first: you see the collection, the field and the new value before it lands in Fauna.
Nothing in Fauna is sent, changed or deleted on your behalf without that click, and a rejected card leaves the collection exactly as it was. The gate is the same one on every surface, described at security.
- Import GraphQL schema
- Execute GraphQL Query
What does the recurring collections pass look like?
Yes.
Saved as a routine, the Fauna collections 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 research and analysis playbook catalogues the other recurring shapes of the queries, the Fauna collections 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