Fishjam 0.27.0 is out! 🎉
This release reworks how testing environments and credentials work, simplifies the path from prototype to production, and turns the Sandbox API into an optional service you can switch on and off whenever you need it.
One set of credentials, end to end
The hard split between sandbox and production credentials is gone. You now have a single set of credentials that work the same way from your first prototype through to production traffic.
What that means in practice:
- The same Fishjam ID and token work whether you’re testing locally or serving real users.
- Upgrading from the free tier to the Regular Jar plan no longer rotates your credentials, they are preserved across the upgrade.
- You don’t need to update your integration after a plan change. Switch plans and your existing code keeps working.
If you’ve been juggling two sets of secrets and two environment configs, you can collapse them into one.
Free tier: no more room limits
The free tier is now usage-based rather than capacity-based. Every account gets a monthly usage quota of up to 10K participant minutes to spend across any combination of conferencing, streaming, and AI agents.
Rooms on the free tier are no longer capped by duration or participant count. You can run a 2-person 5-minute test or a 50-person hour-long call, as long as you’re within your monthly quota. Upgrade to the Regular Jar plan to unlock unlimited usage.
Sandbox API as an optional service
The Sandbox API is now a separate, optionally-enabled service rather than a feature of the sandbox environment. It lets you test Fishjam from a frontend without writing a backend. Useful for prototyping, demos, and quick experiments, but open by design and not meant for production.
When enabled, you get a dedicated Sandbox API URL on the Sandbox page of your dashboard. Pass it to the useSandbox hook in the client SDK, or call it directly from your client to receive a peerToken and connect to Fishjam. Anyone with the URL can create rooms and join them on your account, so keep it private. If you suspect it’s leaked, regenerate it from the dashboard to invalidate the old one.
Turn the service off when you don’t need it.
Stability improvements and bug fixes
As always, this release ships with a round of bug fixes and stability improvements across the stack. Much love to everyone who reported issues and helped us track them down.
Get started
Update to the latest SDKs to pick up any related client changes, and head to your dashboard to see the new credentials view and Sandbox page. For details on the new billing model and quota tracking, check out our documentation.
Happy coding!
