Skip to main content

Hey monday code developers!


As part of our commitment to fostering a thriving and sustainable developer ecosystem, we’re sharing the guidelines about new usage limits for monday code, outlined in this post and documented here. These guidelines, applicable starting today, are designed to ensure platform stability, fair usage, and predictability for all developers and customers building on monday code and using monday apps.


Limits now in effect


The following limits are already enforced and documented, but we want to remind you of them:



  • monday code apps limits: Maximum of 5 monday code apps per account

  • Requests limits:

    • Up to 80 concurrent requests per instance.

    • Up to 10 instances (auto scale).

    • Request timeout: 300 seconds max per request.



  • Memory Size: Limit of 512MB RAM per instance

  • Storage Limits:

    • Key length: 256.

    • Storage per key: 6MB.

    • Storage API Concurrency: 1,000 requests/min per JWT token.

    • Secret Storage API Concurrency: 30 requests/sec.




Currently in monitoring phase (enforcement in Q2)



  • Running Minutes per Instance: This limit is currently in log mode only, meaning it will be monitored without enforcement. We are tracking usage patterns to provide developers with feedback and insights. Enforcement will begin in Q2, giving you time to prepare. See here for more details


Why are these limits necessary?


Monday code has shown strong adoption across developers, partners, and customers since its General Availability (GA) release. As the platform grows, we are encountering instances of overuse that stretch our infrastructure. These clear limits enable us to balance fairness and scalability, while supporting the creation of complex apps.


What’s next?


These changes align with our broader efforts to introduce advanced limiting mechanisms, similar to those in our GraphQL APIs, to support platform maturity and reliability.


We encourage you to review the monday code quotes and limits documentation and assess how these changes might impact your apps.


Your feedback is invaluable as we roll out these changes. Please don’t hesitate to reach out with any questions.

@gregra thanks for the reminder 🙂


Is there going to be a monitoring screen (say) in the developer centre that warns vendors when they are over quota?


Hey David, this is still TBD, more details will be published prior to the rollout




  • Maximum of 5 monday code apps per account



Is this a hard rule, or is it possible to update? I have 4 marketplace apps at the moment, dev versions of those, and a few others in development and if I modernize some of the older ones (which predate monday code) I will be welllll over this limit.


Hey Ben, this is a case by case situation. If you have 5 marketplace apps on monday code, and you need more, we will probably extend this limit for you. This limit is intended so that developers that have toy apps / private apps that produce little to zero value won’t abuse our infra.

If you need to extend your limits (not just that one), you should open a support ticket and we’ll reach out to you directly to understand your specific need.

Hope it makes sense


Greg


I’m guessing that this 5 app limit is to stop the crypto miner wannabes and other freeloaders.


Hey everyone. Lately we’ve been seeing an increase in storage api usage (which increased the noisy neighbour effect) , so I’m giving you a heads up that we’re planning to reduce the current (very high limits) for storage:



  1. Lower concurrency limits (instead of the permissive 1000 requests per minute per token)

  2. Storage limit per key (6MB is quite large, we’re looking into reducing it)


Before we do that, I’ll be very happy to understand if there are any concerns, questions or even concrete numbers you can share so that this process has the minimal effect on your apps.


Thanks, Greg


We use the storage API quite a bit.


For our app Multi Board Kanban, we store board items on storage so that we don’t have to query them on each load.


Sometimes, the data is more than 6MB, so we wrote code to chunk it into smaller sections. If the limit is decreased even more, that would mean more chunks and slower loading.


Do you recommend any alternative approach for apps like ours?


Some architecture suggestions that can help developers like me:




  1. If there was an API that gave all the the information of a board (or a collection of boards ) in the form of a dump, instead of dealing with graphql and its complexity budgets, that would make things simpler.




  2. Something like powersync that syncs the data that a user has access to their browser’s sqlite, and gives access to this data through the SDK. This would remove the overhead from the backend infra.




Like Kranthi, I’m planning to use storage for caching and would also prefer to make fewer API calls to retrieved cached data.


I saw that a new API analytics dashboard was released for Enterprise accounts. It would be great to have something similar for storage/monday code/etc. for dev accounts.


Just food for thought: I’ve been thinking about using Cloudflare products like logging, R1 (cloudlfare’s S3), and D1 (edge SQLite) because of some of the current limitations. It would provide more insight and control which I feel I’m missing right now.


All that said, not maintaining servers is pretty nice and I appreciate all the work the dev team does for developers!


@gregra will a monitoring dashboard be added before the new limits are introduced?



I’m just concerned that some people might be close to/hitting their quota without realising.


@dvdsmpsn We’re still considering the strategy here. A dashboard might be a bit of a stretch at this point, so we might use other ways to expose this data / notify about these things


Hey everyone,


We’ve revised the limit on the number of monday code apps per account and excluded the Marketplace listed apps from the 5 app limit with the hope that this change encourages more Marketplace apps to run on monday code


@benhowes FYI


Hi everyone! We’ve been monitoring the usage of monday code servers over the last 6 months, with almost zero apps breaching the existing runtime limits that were running in log mode.


Today, we finally activated the actual enforcement of the limits, with the hope that this change will strengthen the resilience of our infra.


Reply