Multi-project rollouts, org API keys & end-to-end tracing
Coordinate one rollout across multiple projects and surfaces, manage projects and environments programmatically with organization API keys, and get answers faster thanks to end-to-end tracing across the platform.
Multi-project & multi-surface rollouts
One rollout can now span multiple projects and multiple surfaces. A change that touches a backend service and the web app ramps as a single unit — shared guardrails, one evidence trail, and one flip to roll everything back together.
Organization API keys & the /v1 management API
Create organization API keys and drive Fireweave programmatically: the new /v1 API manages projects and environments. It also powers the Fireweave Terraform provider, which gained an fireweave_org_member resource this week — declare your organization, projects, environments, and members as code.
End-to-end tracing across the platform
The platform now emits OpenTelemetry spans end to end — every API request, database query, message, and durable-workflow step nests into a single trace. When something looks off during a ramp, we can answer “what exactly happened?” in minutes, not hours.
Improved
- Rollout Alerts link the rollout id straight to the rollout detail page
- Filter a project’s rollout list by who created the rollout
- Ramp control is replay-safe — interrupted ramp operations resume exactly where they left off
Fixed
- Web-surface deploy stamps are attested from the SSR server boot, so web rollouts register their deploys reliably
- Feature-flag keys resolve from runtime configuration rather than the build, so the right flags evaluate in every environment