Build Map

Field guide

Real platform surfaces. Real Grok Build / *.grok.me platform. This page is an independent map of it — not the official help center. How to read this →

Honesty zone

Size, storage, logging — what we know

Grok App Builder skills do not publish a complete commercial quota card. This page separates template facts, generic Vercel public limits, and true unknowns.

template template skillinferred public host docsmeasured live probeunknown not published
CapabilitySpecClaim
Vercel static upload (Hobby, generic docs)
100 MB
Public Vercel platform limit — Grok project tier not stated in template
inferred
Vercel static upload (Pro, generic docs)
1 GB
inferred
Vercel build disk (generic docs)
32 GB (up to 64 on some machines)
inferred
Logging retention / volume
Not specified for Grok Apps — host (Vercel) logs
unknown
Bandwidth / egress
Not specified in Grok template skills
unknown
Apps per account
Not specified in template
unknown
Auto-update cannot invent Neon GB, log retention, or Grok-specific bandwidth. Live Lab can only re-check endpoints that answer. For generic host numbers see vercel.com/docs/limits.

Practical sizing guidance

  • Keep production builds lean — large media should be streamed/CDN URLs, not multi‑hundred‑MB JS bundles when avoidable.
  • Hub listings sometimes show app “Size” (e.g. tens of MB) — that is product metadata, not a documented hard cap.
  • Serverless = short-lived compute; long jobs need external workers (not provided by default).
  • Logging: use structured console and Vercel’s project logs; no Grok Apps log-search API is documented here.