As FoodieTrack grows, we’ve been making changes behind the scenes to keep the service fast, reliable, and affordable for everyone.
One of those changes is rate limiting for AI-powered text and image analysis.
Why introduce rate limits?
Every meal you log is processed using AI. Whether you’re:
- 📝 Describing a meal in text
- 📷 Uploading a photo of your food
- 🥣 Scanning food packaging
- 🏷️ Reading nutrition labels
…each request consumes computing resources.
Bursts of AI requests can strain computing capacity and increase operating costs. Rate limits help manage that demand.
Rate limits help ensure FoodieTrack remains responsive and sustainable for everyone.
What does this mean for you?
You may see a wait message if you send several AI requests within the service’s limit window. Ordinary meal logging is the intended use, but this isn’t a guarantee that any particular sequence of requests will avoid a limit.
If that happens, you’ll simply be asked to wait a little before trying again.
Why not make it unlimited?
I’d love to.
FoodieTrack is still an independent project, and every AI request has a real cost. Rather than introducing aggressive restrictions or compromising on AI quality, sensible rate limits allow me to:
- Keep the service fast
- Prevent abuse and automated spam
- Continue improving AI accuracy
- Spend more time building new features instead of managing infrastructure
This may change over time
These limits aren’t set in stone.
As FoodieTrack grows and the platform evolves, I’ll continue reviewing usage patterns and adjusting limits where it makes sense. The goal is always to keep the experience generous for genuine users while protecting the service from abuse.
Thank you ❤️
Every meal logged, every bug report, and every piece of feedback helps improve FoodieTrack.
Thanks for being part of the journey as we continue building a smarter and more reliable nutrition tracker.
