# Graview Cloud > Graview Cloud turns one message in ChatGPT or Claude into a shared app at its own address, live for everyone you invite, with rules that flag problems and a history you can undo. Private alpha, invite-only. From a conversation to an app your group uses. One message in ChatGPT or Claude becomes an app at its own address, live for everyone you invite. Change it later by asking. Graview Cloud is made by En Dash (https://endash.us) and built on the open Graview framework. It is a private alpha: invite-only and free while the alpha runs; pricing is not set. ## How it works - **Describe it.** 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. - **Get the app.** About 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. - **Invite people.** Give 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. - **Change it by asking.** Ask 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. ## What every app has - **Its own address.** Each app lives at name.graview.app. Bookmark it, add it to a home screen, send it to the people you invite. - **Live on every screen.** Edits appear everywhere the moment they're made. If two people change the same thing at once, the second is asked which version to keep. - **Rules that watch.** Say “warn me if a category goes over budget”. The app flags the record that breaks the rule and offers the fix. - **Every change attributed.** Each change records who made it and how: Sam on her phone, or Claude acting for you. Any one of them can be undone, last week's included. - **A map of itself.** The Scene draws every record as a block, grouped by kind, with the links between them and anything wrong lit up. - **Pages for phones.** Each app has Pages, laid out for small screens, so people can update it from wherever they are. - **Templates for real jobs.** Curated starting points, from a wedding to a team’s history to a product roadmap. Answer two or three questions, then keep the example records or clear them. - **Export and self-host.** Download every record and its full history as one file. It opens in the Graview framework, which you can run on your own machine. ## What people make Each job has its own page and curated templates. A template is a complete app to start from; every template below is one of the 23 in the catalog. ### [Life admin](https://graview.cloud/for/life-admin) Chores, bills and job applications in one app the household shares, with what's overdue flagged. Ask: “Help me split the chores between the three of us, and show me what's overdue.” - **[Household chores](https://graview.cloud/for/life-admin#t-household-chores)**: Who's doing which chore this week, and what's overdue. It keeps chores, people and areas. Its headline rule, “Every chore has somebody on it”, catches this: A chore that is everyone's job is nobody's. - **[Job search](https://graview.cloud/for/life-admin#t-job-search)**: Track applications, people and next steps, so nothing goes quiet. It keeps companies, roles, steps and contacts. Its headline rule, “A live application always has a next step”, catches this: Applications go quiet; a week without a planned step means it is time to follow up. ### [Events](https://graview.cloud/for/events) The run of show, vendors against a budget, and where every guest sleeps. Ask: “Plan our wedding weekend: the run of show, the vendors and their quotes, and who's staying where.” - **[Event run-of-show](https://graview.cloud/for/events#t-event-run-of-show)**: What happens when, where, and who is running each part of the day. It keeps slots, sessions, people and places. Its headline rule, “Every session has someone running it”, catches this: On the day, a session nobody owns is the one that starts late with no microphone. - **[Trip planner](https://graview.cloud/for/events#t-trip-planner)**: Plan a trip day by day, so every night has somewhere to sleep. It keeps days, bookings, stops and travellers. Its headline rule, “Every night away has somewhere to sleep”, catches this: A day we stay away needs a stay booking that is not canceled. - **[Thanksgiving dinner](https://graview.cloud/for/events#t-thanksgiving-dinner)**: The day's schedule, who's coming, and who's bringing which dish, on everyone's phone. It keeps events, households, guests, schedule, dishes, rooms and photos. Its headline rule, “Every dish has someone bringing it”, catches this: Every dish has someone bringing it. - **[Vendor shortlist](https://graview.cloud/for/events#t-vendor-shortlist)**: Compare and book vendors against a budget, one per category. It keeps categories and vendors. Its headline rule, “One vendor booked per category”, catches this: Two booked photographers is a double payment waiting to happen. - **[Gift exchange](https://graview.cloud/for/events#t-gift-exchange)**: Names in the hat, wishlists, and a draw where each giver sees only their own match. It keeps exchanges, participants, matches and gift ideas. Its headline rule, “Everyone gets a gift”, catches this: Everyone in the hat has a Santa. Until the draw is done, this lists who still needs one. ### [A home project](https://graview.cloud/for/home-project) Rooms, tasks, purchases and trades, with blocked work flagged before the trade turns up. Ask: “Track our kitchen renovation: the tasks, what we've ordered and when it arrives, and which trade is doing what.” - **[Renovation](https://graview.cloud/for/home-project#t-renovation)**: Rooms, tasks, purchases and trades, so nobody waits on something not yet ordered. It keeps rooms, tasks, purchases and trades. Its headline rule, “Nothing waits on a purchase not yet ordered”, catches this: A tiler booked for Monday with no tiles ordered is a lost week. - **[Vendor shortlist](https://graview.cloud/for/home-project#t-vendor-shortlist)**: Compare and book vendors against a budget, one per category. It keeps categories and vendors. Its headline rule, “One vendor booked per category”, catches this: Two booked photographers is a double payment waiting to happen. ### [Research](https://graview.cloud/for/research) Questions, the sources behind them, and what each source actually claims. Ask: “Organize my thesis reading: the sources, what each one argues, and which chapter it supports.” - **[Reading list and research](https://graview.cloud/for/research#t-reading-list)**: Questions, the sources behind them, and what each source claims. It keeps questions, sources and claims. Its headline rule, “Every open question has a source behind it”, catches this: A question nothing on the reading list speaks to is where the reading should go next. ### [A club season](https://graview.cloud/for/club-season) Fixtures, the squad, and who's available for each match. Ask: “Set up our five-a-side season: the fixtures, the squad, and who's available for each game.” - **[Club season](https://graview.cloud/for/club-season#t-club-season)**: The season's fixtures, the squad, and who's available for each match. It keeps fixtures, players and availabilities. Its headline rule, “Every upcoming fixture has enough players”, catches this: Finding out on the morning that you are two short is how matches are forfeited. ### [Inventory](https://graview.cloud/for/inventory) What you have, where it's kept, and what's running low. Ask: “Track the stock for my candle business: what we have, what's running low, and who supplies it.” - **[Small inventory](https://graview.cloud/for/inventory#t-small-inventory)**: What you have, where it's kept, and what's running low. It keeps items, locations and movements. Its headline rule, “Nothing runs below its reorder point”, catches this: The time to reorder is before the last box goes, not after. ### [A content calendar](https://graview.cloud/for/content-calendar) What's going out, on which channel, who's making it, and the empty weeks. Ask: “Plan our content for the quarter: what goes out on which channel, and what's still in draft.” - **[Content calendar](https://graview.cloud/for/content-calendar#t-content-calendar)**: What's going out where and when, who's making it, and the gaps. It keeps slots, pieces, channels and people. Its headline rule, “Every coming slot has something scheduled”, catches this: An empty slot found on the morning is a scramble; found a week out, it's a plan. ### [Hiring](https://graview.cloud/for/hiring) Candidates, their interviews, and the feedback nobody has written yet. Ask: “Set up a hiring loop for two engineering roles: the candidates, the interview stages, and everyone's feedback.” - **[Hiring loop](https://graview.cloud/for/hiring#t-hiring-loop)**: Candidates, their interviews, and the feedback nobody has written yet. It keeps candidates, interviews, interviewers and feedback. Its headline rule, “Every interview is written up within two days”, catches this: Feedback written a week later is a memory of a memory, and the candidate is still waiting. ### [A bug bash](https://graview.cloud/for/bug-bash) What's broken, where, how bad, and whose it is. Ask: “Run a bug bash for our launch: what's broken, which area, how bad, and who's on it.” - **[Bug bash](https://graview.cloud/for/bug-bash#t-bug-bash)**: A punch list of what's broken, where, how bad, and whose it is. It keeps issues, areas and people. Its headline rule, “Every open blocker has somebody on it”, catches this: A blocker nobody owns is the one still open on launch day. ### [Fans and history](https://graview.cloud/for/fans) A team's seasons, a league's champions, a band's records: the history you know by heart, kept in one place. Ask: “Make a record book of my team's history: every season, the big games, the players and coaches, and every title.” - **[Team history](https://graview.cloud/for/fans#t-team-history)**: A fan's record book of one team: every era and season, the games that mattered, the people, and the honors. It keeps eras, seasons, games, people and honors. Its headline rule, “A championship season has its honor”, catches this: The seasons that ended with a parade are the ones the record book most needs to get right. - **[League record book](https://graview.cloud/for/fans#t-league-record-book)**: A series or league across its seasons: every event, who won it, who they drive for, and who took each title. It keeps seasons, events, competitors, constructors and venues. Its headline rule, “Every finished event has a winner”, catches this: A result nobody wrote down is the gap people argue about for years. - **[Discography](https://graview.cloud/for/fans#t-discography)**: An artist's releases and eras, the songs on them and their genres, and who wrote, played and produced each one. It keeps releases, songs, artists, credits, eras and genres. Its headline rule, “A released song is on a release”, catches this: A song that came out on nothing is usually a single nobody added, or a track on the wrong record. ### [A website](https://graview.cloud/for/website) A site's pages and sections, drafted, reviewed and published, with what's missing flagged. Ask: “Keep our website's content: the pages, their sections, the FAQ, and what's in draft or waiting on review.” - **[Website content](https://graview.cloud/for/website#t-website)**: Your site's pages and the words on them, from draft to review to live. It keeps pages, sections and people. Its headline rule, “Nothing empty on a live page”, catches this: A heading with nothing under it is the first thing a visitor notices. - **[Content calendar](https://graview.cloud/for/website#t-content-calendar)**: What's going out where and when, who's making it, and the gaps. It keeps slots, pieces, channels and people. Its headline rule, “Every coming slot has something scheduled”, catches this: An empty slot found on the morning is a scramble; found a week out, it's a plan. ### [A product](https://graview.cloud/for/product) What's planned, what people ask for, and what shipped in which release. Ask: “Run our product roadmap: features by stage, the requests customers send with their votes, and release notes.” - **[Product roadmap](https://graview.cloud/for/product#t-product-roadmap)**: What you're building now, next and later, what people asked for, and what shipped when. It keeps features, requests and releases. Its headline rule, “Every shipped feature is in a release”, catches this: A feature nobody reads about is one nobody knows to use. - **[Bug bash](https://graview.cloud/for/product#t-bug-bash)**: A punch list of what's broken, where, how bad, and whose it is. It keeps issues, areas and people. Its headline rule, “Every open blocker has somebody on it”, catches this: A blocker nobody owns is the one still open on launch day. ### [Writing](https://graview.cloud/for/writing) A book's chapters, the ideas and stories in them, and what still needs checking. Ask: “Help me write my book: who it's for, the chapters and where each one stands, and the stories I want to use.” - **[Writing a book](https://graview.cloud/for/writing#t-book-writing)**: A nonfiction book: what readers should walk away with, the chapters that deliver it, and stories you've checked. It keeps audiences, reader goals, chapters, ideas and stories. Its headline rule, “Every chapter delivers a reader goal”, catches this: A chapter that gives the reader nothing they came for is a chapter to cut or rethink. - **[Reading list and research](https://graview.cloud/for/writing#t-reading-list)**: Questions, the sources behind them, and what each source claims. It keeps questions, sources and claims. Its headline rule, “Every open question has a source behind it”, catches this: A question nothing on the reading list speaks to is where the reading should go next. ### [A guide others read](https://graview.cloud/for/guides) A market map, a watchlist, a voter guide: something you keep current and other people rely on. Ask: “Keep a guide to the tools in my market: the companies, their products and prices, and where each fact came from.” - **[Market map](https://graview.cloud/for/guides#t-market-map)**: A sourced, kept-up map of a market: who makes what, what it costs, and which to pick for what. It keeps companies, products, sources and use cases. Its headline rule, “Every product cites a source”, catches this: A price nobody can trace is a guess, and guesses are what people come here to avoid. - **[Watch desk](https://graview.cloud/for/guides#t-watch-desk)**: A watchlist for things that move fast: what's happening, whether it's confirmed, and what to do about it. It keeps items, updates, sources, topics and steps. Its headline rule, “An active item says what to do”, catches this: People open the desk to learn whether to worry. An active item with no answer leaves them guessing. - **[Voter guide](https://graview.cloud/for/guides#t-voter-guide)**: A neutral guide to one election: when it is and what's due, who's running for what, where they stand, and what's on the ballot. It keeps elections, key dates, contests, candidates, issues and stances. Its headline rule, “Every race lists its candidates”, catches this: A race with nobody listed looks uncontested, and that may be wrong. ## Occasions One page per occasion a group sets up, with the steps to set it up, the rules that keep it fair, and the template to start from. ### [Secret Santa](https://graview.cloud/for/secret-santa) Draw names, share wish lists, and keep every match a secret until the gifts come out. Ask: “Run our family Secret Santa: everyone's wish list, a budget, and a draw where each person only sees who they're buying for.” - **[Gift exchange](https://graview.cloud/for/secret-santa#t-gift-exchange)**: Names in the hat, wishlists, and a draw where each giver sees only their own match. It keeps exchanges, participants, matches and gift ideas. Its headline rule, “Everyone gets a gift”, catches this: Everyone in the hat has a Santa. Until the draw is done, this lists who still needs one. - A live demo: [Secret Santa](https://demos.graview.app/a/secret-santa) ### [Wish lists](https://graview.cloud/for/wish-lists) Everyone's wish list in one place the family can read, with gift plans kept from the person they're for. Ask: “Make a wish list app for our family: everyone's list with sizes and links, and gift plans the person they're for can't see.” - **[Gift exchange](https://graview.cloud/for/wish-lists#t-gift-exchange)**: Names in the hat, wishlists, and a draw where each giver sees only their own match. It keeps exchanges, participants, matches and gift ideas. Its headline rule, “Everyone gets a gift”, catches this: Everyone in the hat has a Santa. Until the draw is done, this lists who still needs one. - A live demo: [Secret Santa](https://demos.graview.app/a/secret-santa) ### [Thanksgiving dinner](https://graview.cloud/for/thanksgiving) The day's schedule, who's helping, and who's bringing which dish, on everyone's phone. Ask: “Plan our Thanksgiving dinner: the schedule for the day, who's coming, and who's bringing which dish.” - **[Thanksgiving dinner](https://graview.cloud/for/thanksgiving#t-thanksgiving-dinner)**: The day's schedule, who's coming, and who's bringing which dish, on everyone's phone. It keeps events, households, guests, schedule, dishes, rooms and photos. Its headline rule, “Every dish has someone bringing it”, catches this: Every dish has someone bringing it. ## Privacy - **Private until you share it.** Only you can open a new app. Each person you invite gets a role: owner, editor or viewer. - **Your AI has your permissions.** 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. - **Sights decide who sees what.** 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. - **One app can't reach another.** Each app runs on its own, with its own storage, at its own address. - **Not read, not used for training.** 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. - **Leave with everything.** 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 ### Do I need ChatGPT or Claude? No. A chat is the quickest way in, and you can also start from a template on graview.cloud. The people you invite only need the link. ### How is this different from a spreadsheet? Each thing you track is a record with its own page, linked to the records it relates to. Rules check those records, and every change is kept with the name of whoever made it. ### What can my AI do in my app? What you could do yourself: add and edit records, change the app's shape, explain a flagged problem and fix it. Each change it makes is labeled as made for you, and can be undone. ### What if two people edit the same thing? The second person is asked whether to keep their version or the other one. Nothing is overwritten silently, and your chat is told what others changed before it answers you. ### Does it work on a phone? Yes. Every app has Pages laid out for small screens, and you can add it to your home screen. ### What does it cost? Nothing during the private alpha. After it, a workspace stays free with a few apps, and the paid plans are small monthly prices with unlimited people on every one; the plans page on graview.cloud has the details, and nothing is charged before we say so. ### How do I get in? Invites go out in small batches. Join the waitlist and say what you'd keep track of. It helps us choose. ## Connecting a chat Add a custom connector (MCP, OAuth) with the address https://mcp.graview.cloud/mcp in Claude (Settings → Connectors), or ChatGPT (Settings → Apps → Developer mode). You sign in on graview.cloud, choose which apps the chat may reach, and press Allow. ## Links - [Home](https://graview.cloud/) - [Privacy](https://graview.cloud/privacy) - [Terms](https://graview.cloud/terms) - [Status](https://graview.cloud/status) - [Request an invite](https://graview.cloud/#invite) ## Optional - [Everything above in full](https://graview.cloud/llms-full.txt): each job's audience and questions, and each template's kinds, rules and setup questions