Who is Netlify Functions best for?

Best use cases for Netlify Functions

• Static sites and Jamstack applications on Netlify that need occasional server-side logic — form handling, webhook processing, OAuth callbacks — without adding a separate backend service.
• Teams that want zero serverless configuration — Netlify automatically deploys functions in a `/netlify/functions` directory with no additional setup, making it the fastest path to a working serverless function for Netlify users.
• Projects using Netlify Identity, Netlify Forms, or Netlify Commerce where function integration with other Netlify platform features (triggered on form submission, authenticated user context) reduces integration complexity.

Who should avoid Netlify Functions?

• You need broad cloud-native triggers/integrations as the default
• Your backend will quickly become complex or long-running
• Portability and infra control are primary constraints

Upgrade triggers for Netlify Functions

• Backend scope grows beyond lightweight endpoints
• Limits/cost behavior becomes a bottleneck under traffic growth
• Need deeper observability and operational control

Next steps