UniQuick

A Gies Disruption Lab experiment · University of Illinois

Ask for an app.
It's live in one prompt.

Tell your AI agent what you want — a poll, a guestbook, a game — and UniQuick hosts it on a campus URL with Illinois sign-in, shared data, live updates, and AI already wired in. No backend to write.

> read /llms.txt, then build and deploy my app
your AI coding agent
Build a ranked-choice voting page for my section's project topics, then deploy it as topic-vote.
Read /llms.txt → created site → uploading files → deploying…
LIVE …/s/anya-topic-vote/

Workflow

Prompt. Deploy. Share.

No clone, no config, no servers. You drive your AI agent; it drives UniQuick. About five minutes from idea to a shareable campus link.

  1. Mint a deploy token at /token — sign in with your @illinois.edu account; it's shown once.
  2. Hand the token to your agent — Claude Code, Codex, or similar. It adds the UniQuick tools in one line, runs npx -y uniquick, or reads /llms.txt.
  3. Ask for an app, in plain English. The agent builds the page and ships it.
  4. Share the URL with anyone at Illinois. Manage or delete sites at /my.

Where it runs

On Illinois infrastructure.

  • University of Illinois Azure — App Service, Postgres, Blob storage, and Azure OpenAI, all inside the U of I tenant.
  • Your prompts never train any model — the built-in AI is gpt-4o-mini on Azure OpenAI, not a consumer service.
  • Free to build and host — paid for by the Gies Disruption Lab.
  • Not a vault — apps are visible to anyone at Illinois with the link, and this is not a store for FERPA-protected or sensitive data.

Ready when you are

Build your first app this afternoon.

Bring an AI agent and an idea. UniQuick brings everything else.