Configuration
Usage Pattern
Unique users per day
How often each user accesses
Total daily sessions
Traditional Live Query (Other)
Real-time backend queries
Average user session length
Compute + DB + cache per query
GUUT InfoApp
One-time generation query
One generation per user
No server resources consumed
GUUT does not make queries cheaper. It makes many queries disappear. InfoApps are generated once per user (regardless of sessions), then run entirely in the browser. Session duration is irrelevant because no backend resources are consumed during user interaction—all compute happens client-side.
Note: Concurrent sessions are used only for peak capacity planning (hardware sizing). All cost calculations are based on total daily sessions.
For infrastructure capacity sizing
Percentage of read operations
Future traffic projection
Note: Infrastructure costs remain the same. GUUT reduces how often they're needed.
Application Tier
Database Tier
Cache Tier
GUUT Generation Infrastructure
One-time compute per generation
Scheduled/on-demand generations
Average size per InfoApp
Data Storage Cost
Fixed database storage
Storage cost per GB
Network & Delivery
JSON responses per query
Complete packaged InfoApp