We use an in-house tool that we originally wrote in '92 (but have improved greatly over the years) called OmniBugZapper. It’s not available outside Omni, but you can read a little about it in the “Inside Omni” article that Brent Simmons wrote for objc.io shortly after he joined our engineering team.
(It was originally implemented for the NeXT using DBKit, then rewritten using EOF, almost rewritten in WebObjects when NeXT was giving up on the desktop, but returned to EOF when Apple shipped that as part of Mac OS X—which unfortunately disappeared before the final 10.0 release, though we kept it limping along as long as we were able to run PowerPC software. Once OS X dropped support for PowerPC emulation, OmniBugZapper was rewritten with native client libraries, talking to the same FrontBase SQL database server we’d been using with EOF. A few years ago we ported the app to our iPads and iPhones, and last year, we migrated the database to PostgreSQL which is serving us quite well. But while this slowly-changing-over-24-years stack is something we’ve been comfortable managing for ourselves, it hasn’t really ever been in a state where it would make sense to offer this solution to anyone else.)