# New: Bursty concurrency + Sandboxes in open beta

Canonical: https://brew.new/templates/inngest/new-bursty-concurrency-sandboxes-in-open-beta

Brand: inngest.com
Category: newsletter

![Preview of New: Bursty concurrency + Sandboxes in open beta](https://cdn.brew.new/email-preview-631a7db1e44aa80f-tracking_r57yqkxpbjphca1md34hadt3zx8fr1n9-1791328903194.png)

## Email content

New in Inngest this week: Bursty concurrency, Sandboxes in open beta, and scoped access for MCP/CLI/API. Read on for more!

As functions spike, concurrency is raised to 3x the limit for a total of 1 hour per month.

One spiky function shouldn’t slow you down. Beginning this week, Inngest will automatically "burst" Pro and higher accounts 3x over plan concurrency limits to handle unexpected spikes. Accounts will have 60 total minutes of bursted concurrency every month, for free.

Why? Previously, your concurrency ceiling would cause spikes to build a backlog. Bursty concurrency lets you:

Keep things moving when unexpected events occur.

Better assess what your monthly concurrency should be set to.

What is concurrency, and what’s changing?

Concurrency lets you fan out work that arrives at once, across multiple runs. Previously, when you’d hit your limit, you probably felt like Inngest was moving slow; your backlog would build and you weren’t sure why.

In reality, remaining work was just queuing up. Bursty concurrency lets that work run when it arrives (up to 3x your limit). If your burst is only needed for a few minutes, you bank the remaining of your monthly hour.

For more information, check out our blog, or the bursty concurrency docs.

Want to add concurrency right now? Head to your billing page.

Note: You will never be charged for a burst, nor for concurrency you didn’t add yourself. A burst is a tool to help you right-size your plan, and does not supersede function-level concurrency you set. Today, bursts are only applied to Inngest paid plans.

What else is new?

Sandboxes in Open Beta - Every part of your workflow should be durable, including how you test code. Inngest Pro and higher accounts on the TypeScript SDK can now call step.sandbox in any function to boot a microVM in under a second.

Sandboxes are charged per-second for each CPU and GB of ram they consume. Each CPU is charged at $0.000011/second, and each GB of ram at $0.000003/second.

Read the docs, or get a feel before you try in our new Sandbox playground!

What's better?

Scoped Access - We released the MCP with one API key that could do anything. Some of you liked that, some of you wanted more granular control. You can now tune MCP, CLI, and API permissions (read or write) for all parts of Inngest. See the MCP docs for more.

That's all for now! Happy building,

Lauren, Head of Marketing @ Inngest

TwitterLinkedIn

About Terms Contact

©2026 Inngest

The email was sent to you@example.com. To no longer receive these emails, unsubscribe here.

[Open and remix this design](https://brew.new/templates/inngest/new-bursty-concurrency-sandboxes-in-open-beta)

[Browse email designs](https://brew.new/browse/templates)