Skip to content

Limits

Warning

These limits may be subject to change.

Nextmv sets limits on API usage, run duration, and input/output sizes. If you need higher limits, please contact Nextmv support.

Rate limits

  • 50 runs lifetime maximum.
  • 30 second maximum run time per run.
  • 5 run requests per second.
  • 200 run result requests per 10 seconds.
  • 2,000 API requests per minute (all /v1 endpoints).
  • 15 minute maximum run time per run.
  • 5 run requests per second.
  • 200 run result requests per 10 seconds.
  • 2,000 API requests per minute (all /v1 endpoints).
  • 15 minute maximum run time per run.
  • 5 run requests per second.
  • 200 run result requests per 10 seconds.
  • 2,000 API requests per minute (all /v1 endpoints).
  • 15 minute maximum run time per run for standard execution classes.
  • Premium execution classes support longer runtimes and different machine sizes. See [execution classes][run-execution-classes].

Info

Higher rate limits are available for power users: 10 run requests per second, 500 run result requests per 10 seconds, and 10,000 API requests per minute. Contact Nextmv if you need these limits.

Input/output limits

  • Input files have a 700 MiB limit (raw json file & multi-file .tar.gz bundle).
    • However, total file content of multi-file inputs has a 2.5 GiB uncompressed maximum.
  • Managed Input Upload Limit: 100 MiB.
    • However, managed inputs can be created from runs too in which case above normal input file limits apply.
  • Output files for Free plan: 5 MiB maximum.
  • Output files for Innovator plan: 10 MiB maximum.
  • Output files for Scale-up plan: 100 MiB maximum.
  • Output files for Premium, Enterprise, and Premium v2 plan: 700 MiB maximum.
  • Output size is measured on uncompressed size for JSON output.
  • Output size is measured on compressed size for multi-file output.

Premium plan custom asset limits

App artifact limits

  • App bundle uploads: 700 MiB compressed maximum, 1.5 GiB uncompressed maximum.

Runtime limits

Runtime limits are based on the execution class of the run. See execution classes for more information.

Info

Keep runs a little below the hard runtime limit so your app has time to return its final solution or error cleanly.