Send your eas.json and a recent build log. Get a specific, itemized report on exactly what's driving your cost and how to fix it. Free while in early access.
See what you'll get
Launch offer
Freewhile in early access — no payment needed
This is normally a paid report. It's free for now while I'm getting the first real reports out and learning what's useful — submit above and I'll email yours within 48 hours.
If this saved you a headache, you can buy me a coffee ☕ — totally optional, just appreciated.
← back
eas / optimizer report · sample
Here's what a real report looks like
Illustrative example — your actual report is based on your own files.
Detected worker size: large
Detected cache status: miss
Detected bundle size: 9.2 MB
Builds referenced in log: 1
High impact~$38/mo
Preview builds are using a large worker
Your production profile needs `large`, but this log shows the same resource class on a non-production build. Switching preview/dev profiles to `medium` cuts per-build cost by up to 50% for builds that don't need the extra power.
Medium impact~$14/mo
Dependency cache isn't hitting
This build shows a cache miss on node_modules. Recurring misses usually mean your cache key includes something that changes every build (like a timestamp or lockfile hash mismatch). Fixing this alone can cut several minutes of billed build time per run.
Low impact~$6/mo
Bundle size is trending up
9.2 MB is on the higher side for a typical Expo Router app. Worth auditing recent dependency additions — this affects OTA bandwidth cost every time you push an update, not just this one.
~$58/mo
estimated potential savings if all three are addressed
Estimates based on the single log provided — patterns may vary across builds. Not a guarantee of actual billing changes.