---
type: email
from: Clerk <systems@clerk.com>
subject: Clerk Update – Sept 9, 2025
received: 2026-03-06 07:26:43
date_header: Tue, 9 Sep 2025 17:17:14 +0000
priority: normal
status: awaiting_approval
uid: 29942
---

## Email Content

**From:** Clerk <systems@clerk.com>
**Subject:** Clerk Update – Sept 9, 2025
**Date:** Tue, 9 Sep 2025 17:17:14 +0000

### Body (preview)

M2M tokens enter public beta, shadcn/ui registry support launches, free trials arrive in Clerk Billing, and automatic regional

failover enhances service reliability.





https://clerk.com



The Clerk team has been hard at work shipping new features to help you build secure applications faster. Here’s a rundown of the

highlights:

M2M Tokens Public Beta

https://go.clerk.com/UrALaXN

Clerk's M2M tokens are now available in public beta, delivering secure authentication for backend service communication without

the complexity typically associated with inter-service authentication. Consider a typical e-commerce application where your order

processing service needs to communicate with your inventory service, payment processor, and notification service. Instead of

managing API keys or building custom authentication flows, M2M tokens provide a standardized way for these services to

authenticate with each other securely using just a few lines of code with Clerk's SDKs.

This eliminates the need to build custom authentication infrastructure or manage complex certificate chains while maintaining

proper access controls and audit trails across your distributed architecture. The feature is currently free during the beta

period, allowing developers to freely integrate and test with your own applications.

 * Multiple configuration options: Create machines directly from the Clerk Dashboard or programmatically via API, with immediate

   token generation capability

 * Flexible token customization: Support for custom claims, configurable expiration times, and instant revocation for fine-grained

   access control

 * JWT support planned: Future JWT token support will eliminate verification costs for high-throughput scenarios while maintaining

   creation-based pricing



Explore the M2M tokens guide [https://go.clerk.com/UrALaXN] in our changelog, or check out the example repository

[https://github.com/clerk/m2m-example] to see two Express apps communicating securely in

---

## Suggested Actions
- [ ] Reply
- [ ] Archive
- [ ] Escalate
