Execution monitoring Hosted beta
Filltrace.
Know what your bot actually did.
Hosted beta with a public synthetic demo and private workspaces.
Explore Filltrace
filltraceYour bot runs. Know what happened.
Public demo · Synthetic paper telemetryThe screenshot shows Filltrace’s public read-only demo with synthetic paper-order telemetry. Private workspace data is separate. Filltrace does not place live orders or promise strategy returns.
The starting point
A real problem.
A thoughtful response.
The problem
A running bot is not proof that an order was acknowledged or filled. Scattered logs make it hard to see where an execution went wrong.
What we're building
Filltrace brings authenticated paper telemetry into a private workspace. An execution timeline connects each order to its events, while incidents surface missing heartbeats and unexpected outcomes.
Explore FilltraceFollow the whole order.
Inspect signals, submissions, acknowledgments, fills and rejections in one timeline. Duplicate event delivery does not count as a second execution.
Turn an exception into evidence.
Review incidents alongside their source events. Acknowledging an incident records that you have seen it without claiming the cause is resolved.
Connect on your terms.
Use revocable ingest tokens for your client or a local read-only Alpaca paper-history observer. Export a daily report from your workspace.
Something on your mind?
Let's make
it happen.
A new product, a stubborn problem,
or an idea you can't leave alone.