Launched this week
SafeFIX
FIX log analyzer, dictionary validator & anonymizer
2 followers
FIX log analyzer, dictionary validator & anonymizer
2 followers
100% client-side FIX protocol log analyzer: dirty-log multi-parser, custom QuickFIX-format XML data dictionary validator, ticket-safe log anonymizer with exact BodyLength (9) and CheckSum (10) recalculation, and order lifecycle latency inspector. Logs never leave the browser.
Free Options
Launch Team
Render Sandboxes: a computer for every agentGive every agent its own machine. Starts in under a second
Promoted
Hi Product Hunt! I built SafeFIX because debugging FIX sessions usually means pasting production logs into tools that upload them, or emailing logs to a broker or vendor with client IDs and account numbers still inside.
SafeFIX is a single static page with no backend. Your log never leaves the browser tab, and you can check that in DevTools.
What it does:
Reads messy logs: SOH, |, ^A or tab delimiters, QuickFIX and other engine prefixes
Validates against FIX 4.2/4.4 or your own QuickFIX XML dictionary
Explains rejects (35=3, 35=j, 35=9, rejected 35=8) next to the message that caused them
Traces each order from NewOrderSingle to fills, with latency
Anonymizes a log for a support ticket and recalculates BodyLength (9) and CheckSum (10), so it still parses
The free version covers 100 lines of a log. Pro is a one-time $19, with no account and no subscription.
No real data to try it with? Synthetic sample logs are here: https://github.com/ekiedev/fix-iso20022-samples
I'd love feedback from anyone running QuickFIX/J, QuickFIX/n or bridges like oneZero, PrimeXM or cTrader FIX: which log formats break it?