Ask your AI agent for a web app — a poll, a game, a sign-up sheet — and it's live on a campus URL in one prompt. Illinois sign-in, shared data, live updates, and AI are already wired in.
Get started — mint a deploy token My sitesSign-up sheets, RSVPs, polls, surveys, office-hour queues, suggestion boxes — every response attributed to a real Illinois account, no login code written.
Try it: live campus poll (results move as people vote)Leaderboards, guestbooks, discussion walls, brainstorm boards, live Q&A during lecture — everyone sees the same data, updated live.
Try it: the guestbook demoPresence ("who's here"), shared cursors, lightweight multiplayer games, voting where the results move as people click.
Try it: shared cursors (open in two windows)Flashcards that track progress, habit trackers, slot pickers, dashboards over data your app collected.
A summarize-this box, a study-question generator, writing feedback — each user gets a daily AI allowance, no API key needed.
Rule of thumb: if it's "a web page where people at Illinois can ___ together", it probably works here. Your app is static files — the platform provides the backend.
Thirty seconds later it's at
…/s/<your-netid>-topic-vote/ — share the link with anyone
at Illinois. Site names carry your netid automatically, so everyone can tell
whose app is whose. Manage or delete your sites any time at
/my.
Every visitor signs in silently with their Illinois account — your app
always knows quick.user.name without you building auth. Apps
are visible to anyone at Illinois with the link (not listed publicly, not
private either). Apps are static pages — no user code runs on the server —
and this is not a store for FERPA-protected or sensitive data.