Graview Cloud for a club season
Fourteen in the squad, five needed on the pitch, a fixture every weekend. Players mark themselves in or out from their phones. A match that's short of players is flagged while there's still time to find a sub, and a result nobody recorded gets chased.
For the person who runs the team's group chat, picks the side, and chases fourteen people every Thursday.
Graviewthursdays.graview.app/a/five-a-side-season
Live
You, in Claude
Set up our five-a-side season: the fixtures, the squad, and who's available for each game.
graview · create_app3 kinds · 13 records · 2 rules
Fixtures3
Players6
Availability4
RuleRiverside is short of players: 4 of 5 available
Rules2 of 2 hold
Watch it again
Sound familiar?
“Are you in Saturday?” — sent to fourteen people, answered by six.
“We turned up with four. Again.”
“Who has the kit? Who paid subs?”
For a club season
Fixtures with dates, venues and results
Availability per player, per match
A squad page anyone on the team can open
A week with it
you add the fixtures and the squad; everyone gets the app on their phone.
players mark themselves in or out themselves; the match that's short is flagged while there's still time to find someone.
the team is picked from the ones who are actually available; Saturday, everyone knows where to be.
Templates
It's a complete app for a club season. Answer the questions it asks and it's yours to change. Or skip it and describe the job in your own words.
The season's fixtures, the squad, and who's available for each match.
How it works
There is no setup. The app's shape comes from what you describe, and it changes when the job does.
Add Graview to ChatGPT or Claude once. Then say what you're organizing, in your own words. Or start from one of our templates on graview.cloud.
You: “Track our kitchen renovation and what's on order.”How to connectAbout a minute later it's live at its own address on graview.app, with the records and rules the job needs. It shows up in your chat and opens on any phone.
okafor.graview.app/a/kitchen-renovationGive each person a role: owner, editor, viewer, or one your app defines. Everyone sees each change as it lands, with the name of whoever made it, your AI included.
Here now: Nick, Sam and AnaAsk for a deposit field or a budget warning and the app changes shape. Every record comes through. If one wouldn't, you're asked first, and earlier versions can be restored.
You: “Add a deposit field.” → version 2Privacy
People put real money and real addresses into these apps. This is who can see them, and what happens when you leave.
Only you can open a new app. Each person you invite gets a role: owner, editor or viewer.
A connected chat can do what you could do in that app, and nothing more. Its changes are labeled as its own, and it can never change who has access.
An app can keep some records to some people. A record you can't see is absent everywhere: on the page, in search, and in your chat.
Each app runs on its own, with its own storage, at its own address.
We don't read your apps or train AI models on them. Staff can look only if you grant support access: read-only, for 24 hours, ended whenever you like.
Export a whole app with its history at any time. Delete it and it's gone within 7 days, and from backups within 30.
Questions
No. The app is a link; it opens on their phone and they tap in or out. The organizer signs in to change the season.
Yes: a kind for payments and one for kit, if you ask for them. Start with availability; add the rest when the season settles.
Other jobs
Private alpha
Graview Cloud is invite-only while we build it with its first people. Tell us what you'd make and we'll send an invite when there's room.
Coming soon
Your own apps, kept as long as you like and exportable at any time. Free while the alpha runs.
Coming soon
Everyone you share an app with, each in the role you give them.
Already have an invite?
Sign in to the private alpha