I've been in the data engineering space for over a decade.
As the workload for our team started to scale faster than our staff and context switching thrashed my focus, PRs took a backseat. Releases, pipelines, and reports downstream started failing or silently degrading.
Layer on AI-assistance and suddenly the PRs are 5x the size, with no additional time to review every line.
I built Lexega to block PRs for the things I was afraid I would overlook. It's a static analyzer for SQL that runs in CI and comments on the PR. It's written in Rust, ships as a single binary, runs entirely inside your network with zero telemetry, and outputs standard SARIF. You can try it in the playground without signing up: https://lexega.com/playground.
Lexega is early-stage. I'm looking for a handful of design partners to review their own PRs, stress the parser, gauge the value of the built-in rules, encode their definition of risk with custom rules, and help me shape the roadmap. If you feel the same pain I've felt: hello@lexega.com.
1 comment
[ 1.5 ms ] story [ 17.4 ms ] threadAs the workload for our team started to scale faster than our staff and context switching thrashed my focus, PRs took a backseat. Releases, pipelines, and reports downstream started failing or silently degrading.
Layer on AI-assistance and suddenly the PRs are 5x the size, with no additional time to review every line.
I built Lexega to block PRs for the things I was afraid I would overlook. It's a static analyzer for SQL that runs in CI and comments on the PR. It's written in Rust, ships as a single binary, runs entirely inside your network with zero telemetry, and outputs standard SARIF. You can try it in the playground without signing up: https://lexega.com/playground.
Lexega is early-stage. I'm looking for a handful of design partners to review their own PRs, stress the parser, gauge the value of the built-in rules, encode their definition of risk with custom rules, and help me shape the roadmap. If you feel the same pain I've felt: hello@lexega.com.