Hi everyone. I'm Sanghyun Park, the founder and the only engineer on LexQ.

For six years on Java/Spring teams, I watched the same thing repeat. A PM asks to change the blood pressure level that triggers an alert.

An engineer opens a PR. Review, staging, production. One number can take two weeks.

That is an architecture problem, not a process one. Business logic sits inside application code, so every change to it rides the deploy pipeline.

LexQ is the Decision Operations Platform I built to pull that logic out.

Rules live as data, versioned and rolled back in place, without touching application code.

Test. Impact Simulation runs a version against production data you already have and shows the delta before anything goes live.

Understand. Every execution leaves a trace, and Decision Replay re-runs a past decision against another version, so you can see the blast radius first.

Deploy. Publish a version, split traffic for an A/B test, roll back with no application redeploy.

There is also an MCP server, so an agent can drive the whole lifecycle from your editor. That is the demo in the gallery.

What it does not do yet: managed hosting only, no client libraries, USD billing only, and no third-party audit report. Support is one person, and that is me.

If your rules change once a quarter, a config file and a deploy are cheaper.

LexQ earns its place when they change often, and when someone has to explain a decision made last month.

Thank you for taking a look. I will be here all day, and I would rather hear where it breaks than where it looks good.