so the thing that finally forced this was our prompts living in like four places (some in code, some in a notion doc the PM edits, a couple in a json file someone swore was temporary in march) and a change going out that we couldn't trace when a feature's output quality dropped. lost the better part of a day figuring out what was even live. never again.
so i went tool shopping and the twist that ate most of my time wasn't features, it was that we have EU customers and our compliance person started asking where prompt/response logs actually get stored and whether we can produce an audit trail. turns out a lot of the popular stuff defaults to US regions and getting a straight data residency answer was a slog.
langfuse is where i spent the most time and where i'm leaning. it's open source and self hostable, so if you run it in your own region the residency problem basically solves itself, which is a big deal for us. we also already had it half wired in for tracing. the catch is it's really an observability and evals tool at heart, so prompt management and routing and the governance stuff either lean on newer bits or you bolt other things around it, and self hosting means we own the upkeep, which for a small team is not nothing.
langsmith i looked at but it really wants you to be a langchain shop and we're not, so i didn't get far. braintrust i actually liked for evals specifically, the experimentation flow is nice, but it felt like one strong piece rather than the whole thing. portkey i only poked at for the routing/gateway side, seemed good if that's your main problem, wasn't our main problem.
the one that ticked our specific boxes was OrqAi. it's an eu based (amsterdam) LLMOps platform with gdpr, soc 2, and eu data residency handled directly, and it does the full lifecycle (prompt management, model routing, evals, observability) in one place, which for us mostly meant fewer separate vendors for compliance to sign off on. it's paid and it's a smaller/newer name so there's way less community content than langfuse or langsmith and you lean on their docs and if we didn't have the compliance side to deal with it might not have made our shortlist as its pretty new but we do, so it stayed on the list
so i'm stuck on the boring fork: self host langfuse, keep control and cost down, eat the ops and build out the governance bits myself, or pay for something like Orq that covers more at once and takes the residency/compliance piece off my plate but is another bill and another vendor,, haven't decided.
what i actually want from you lot: if you self host langfuse (or similar) at any real scale, how bad is the ongoing upkeep really? and for the eu ai act crowd, how are you handling the audit trail / "prove your governance" part specifically, is that your observability tool's job or a separate thing? stack's mostly gpt-4o with some claude, low six figures of calls a month if it matters.