Advanced observability for every Bubble app. Monitor your app at scale with Buildprint logs.
Buildprint syncs your Bubble server logs, so you and your agent can search them, follow a workflow step by step and get an alert when errors spike.
- live14:32:07Workflow errorCharge failed: amount is below the order totaldana@northwind.co
- live14:32:07Running actionCharge the customerdana@northwind.co
- live14:32:06Finished running actionApply discount to Orderdana@northwind.co
- live14:32:06Running actionApply discount to Orderdana@northwind.co
- live14:32:06Finished running actionCreate a new Orderdana@northwind.co
- live14:32:06Started running workflowcheckout_paydana@northwind.co
- live14:32:05Request for API workflowcheckout_paydana@northwind.co
Search every log your app writes. Go from a customer's complaint to the step that failed.
Follow a workflow step by step
Open any event to see the whole workflow run in order, and how long each action took.
- checkout_pay
- Create a new Order
- Apply discount to Order
- Charge the customer
Narrow it to one customer
Filter by text, event type, user email or Thing ID. Paste an ID into search and it becomes a filter.
Share the exact event
Copy a link to any event, so a teammate sees exactly what you see.
- User
- dana@northwind.co
- Version
- live
- Latency
- 610 ms
- Workload units
- 0.62
See how hard your app is working
Track workload units, active users, action times and error rate across your Bubble versions.
- Workload units
- 18,420
- Unique users
- 1,203
- Median action time
- 42 ms
- Error rate
- 0.8%
- ops@northwind.co
- dana@northwind.co
- sam@acme.io
Hear about errors before your users do. Then let your agent find the cause.
Get an alert when errors spike
Tell your agent what to watch for. Buildprint checks your logs and sends a webhook or an email when it happens.
Alert me when checkout_pay has more than 10 errors in 5 minutes.
- checkout_pay errorsThreshold2m agoDelivered
- Workload spikeAnomaly3d agoEmail
- Sending email failedMatch event1w agoDelivered
Your agent reads the logs
In Buildprint, Claude Code, Codex or Cursor, your agent searches the logs itself and links to the events it found.

3 checkout_pay runs failed at Charge the customer today, all with a discount code. The first one is 14:02:51 · Workflow error. The discount is applied before tax, so the charge comes out below the order total.
Send your logs to your own tools. Logpush forwards a copy to the services your team already uses.
Keep your own stack
Push a copy of every log to Axiom, Datadog, ClickHouse, Grafana Loki or any OpenTelemetry endpoint.
Choose where logs live
Send logs to a destination in your own region, then turn off the copy Buildprint stores in the US.
Test before you switch it on
Check the connection when you add a destination, and pause or edit it any time.
EnabledBuildprintUS. Powers Explorer and Monitors- EnabledAxiomDataset acme-store
- EnabledDatadogdatadoghq.eu
Common questions, answered.
Which Bubble apps can use Logs?
Logs is rolling out through a waitlist, starting with apps on Bubble's Growth plan and above. Join it from Logs in your Buildprint project.
How quickly do new logs show up?
Busy apps usually sync within minutes. Quiet apps can take up to 12 hours, because Buildprint checks them less often to keep the load on Bubble down.
How many logs are included?
Every plan includes a monthly log allowance, shown in the pricing table. If you reach it, sync pauses and the workspace owner gets an email. Logs you've already synced stay available.
How do I set up an alert?
Describe what you want to catch to the Buildprint agent, or to your own agent through the CLI or MCP server, and it creates the monitor. Alerts go to a webhook, or by email if you don't set one.
Where are my logs stored?
Buildprint stores them in the US. To keep them in another region, add a Logpush destination there and turn off the Buildprint copy. Explorer and alerts use that copy, so they stop getting new logs once it's off.
What access does Buildprint need?
Give connect@getbuildprints.com permission to view Logs in your Bubble app, for each version you want synced.
Stop guessing why it broke. Read the logs.
Connect your Bubble app, and the next time something breaks you'll know where to look.