Skip to main content

​
Organization quotas

Each organization can have up to 10 container instances.
Need higher limits? Contact us to discuss your requirements.

​
Resource options

Each container specifies its CPU, memory, and GPU requirements in tinfoil-config.yml. These values are measured and published with the release; create, start, and relaunch requests cannot override them. Available options:

CPU

Memory

Public resource shapes are CPU-only, gpus: 1, or gpus: 8. GPU access must be enabled for your organization.
Start with the smallest tier that works for your workload and scale up if you see high CPU utilization or slow response times. Over-provisioning wastes resources and you can always resize by redeploying with an updated tinfoil-config.yml.

​
Choosing the right size

Pick resources based on what your application actually needs, not what you think it might need. A few rules of thumb:
  • Compiled languages (Go, Rust, C++) are memory-efficient — 8 GB is often enough.
  • Interpreted runtimes (Python, Node.js, Ruby) typically need 16 GB+ for production workloads.
  • CPU cores should match your concurrency model. A single-threaded app won’t benefit from 32 cores. A multi-process web server (e.g. Gunicorn with workers) should have roughly one core per worker.
  • Measure first. Run your app locally with resource limits to understand its actual footprint before deploying.