Deprecation notice: Blackfire-hosted Synthetic Monitoring — including periodic builds, webhook-triggered builds, and native integrations — is deprecated and will be removed on May 30, 2026.
Migrate to Blackfire Player
with --report to run Synthetic Monitoring from your own infrastructure,
with full control over scheduling and secret management.
Blackfire Builds offer various options to automatically profile your code, and to run assertions against it.
A Build is a collection of profiles, resulting from scenarios which are triggered upon an event.
When complete, Builds have a status (Successful, Failed or Errored).
The Successful and Failed statuses depend on the assertions which you write. If you don't write any assertion, Blackfire may still mark the Build as Failed if a recommendation is detected.
Builds are Errored when your scenarios cannot be completely executed. This may happen either when something is going wrong with your Builds configuration, or when a Blackfire Player expectation fails.
Builds can be triggered with:
Builds triggered via webhook, periodic scheduling, or PaaS integrations
are run from Blackfire's servers. If the profiled application is behind a
firewall, allow the following IP addresses on the web ports (usually
80 and 443):
46.51.168.254.75.240.245This does not apply to Blackfire Player runs, which initiate requests from your own environment.
When a Build is complete, you may receive notifications where and when it matters to you.