Code quality
enforcement,
from the IDE
to the org.
ScaleArch is a three-part platform for catching mechanical, repeatable code issues — SQL injection, N+1 queries, SOLID violations, your company's deprecated APIs — before they ever reach review. Local. Deterministic. Zero AI runtime.
Senior engineers waste hours catching the same issues every sprint.
SELECT *.
Empty catch blocks. Hardcoded secrets. 200-line functions.
SQL queries firing inside loops. These are not architectural debates —
they're mechanical, repeatable, and catchable by a machine.
Generic linters exist. But they don't know your company's standards.
They don't know PaymentV1 was
deprecated last quarter, that every fetch must go through your internal
HttpClient, or that three
incidents proved every async function needs a try/catch.
That knowledge lives in Confluence. In PR comments. In onboarding calls that don't scale. ScaleArch gives it a home in code.
💬 Slack threads
👀 PR review nitpicks
🤝 Onboarding tribal knowledge
→ enforced inconsistently, by humans
Written once. Enforced forever.
Live on every save, in every editor.
→ enforced deterministically, by the machine
One platform. Three surfaces. One coherent answer to organizational code quality.
The Extension catches issues at the keystroke. The Rule Builder lets anyone author org-specific rules without learning AST internals. The Validator gives engineering leadership governance, audit logs, and an API for CI.
ScaleArch Extension
Two engines run on every keystroke. The Regex Engine catches DB anti-patterns and security issues line-by-line. The AST Engine parses the file into a syntax tree and catches structural problems regex can never see — SOLID violations, deep nesting, empty catch blocks.
ScaleArch Rule Builder
Fill in a form — name, message, severity, language, pattern. Get back
production-ready TypeScript ready to paste into customRules.ts.
54-pattern library. AST node picker. Regex tester. Verify-with-Claude flow
for a second opinion before shipping.
ScaleArch Validator
REST API your CI pipeline or save flow calls to validate code against your org's active ruleset. Dashboard for engineering leadership: API call volume, pass/fail rates, most-triggered rules, language breakdown. Every POST /validate call is logged — filterable by API key, time range, and language. API keys per team or service. Enable/disable built-in regex rules per org. Author custom regex rules through the UI without touching code.
Two engines, one extension, every save.
ScaleArch routes through an AstGateway
that picks the right parser per language. Adding a new language is one file and one line.
strcpy, sprintf,
raw new in C++…
ast ·
Java via tree-sitter · 13 dedicated Java rules including method length,
empty catch, public non-final fields, == on Strings.
What it catches, by category
Database
db/no-where-clause
db/query-in-loop · N+1
db/leading-wildcard-like
db/delete-without-where
db/update-without-where
Security
security/eval-usage
py/exec-usage · py/shell-true
java/sql-concatenation
cpp/gets · strcpy · sprintf
Performance
perf/sync-fs-call
perf/json-parse-in-loop
java/string-concat-in-loop
py/new-object-in-loop
SOLID & Quality
- solid/srp10+ method classes
- solid/dipconcrete-class injection
- quality/function-too-long
- quality/high-complexity
- quality/deep-nesting
Python AST
- py/ast-function-too-long
- py/ast-class-too-many-methods
- py/ast-missing-docstring
- py/ast-no-type-hints
- py/ast-init-too-complex
Java AST (v2.0)
- java/ast-empty-catch
- java/ast-system-exit
- java/ast-thread-sleep
- java/ast-string-equals-compare
- java/ast-public-field+ 8 more
Skip the AST tutorial. Ship the rule.
Writing a custom lint rule from scratch means understanding AST node shapes, tree-sitter property names, TypeScript generics, and webpack externals. That's a steep barrier for any team that doesn't have a compiler engineer on staff.
The Rule Builder eliminates it. Single-page web app. No backend. No accounts. Pick a pattern from the 54-pattern library, tweak it, regex-test against sample code, and copy production-ready TypeScript to your clipboard.
- → 54 ready-made patterns across 5 languages
- → Searchable AST node picker with code examples
- → Live regex tester against your own sample
- → "Verify with Claude" — copies a tuned prompt for sanity-check
- → Documented 6-step pattern for adding new languages
Save-time guardrails, audit logs, and a dashboard.
The Validator is a separate runtime service — its own dashboard for authoring regex rules
per language, its own auth and API keys, and a single POST /validate
endpoint to wire into save flows, CI pipelines, or any system that writes data.
Every POST /validate is audited: language, line count,
errors found, rules triggered, processing time. Filterable by API key, time range,
and language with sub-second queries.
Two tracks. One philosophy.
The Extension and Rule Builder are one product family — IDE-time static analysis, regex across 5 languages, AST for JS/TS/Python/Java. The Validator is a separate runtime service — its own UI for authoring regex rules, called at the moment data is saved (form submits, API writes, scheduled pipelines). Same mindset, different enforcement point.
customRules.ts. Pick the track that fits the
enforcement point: IDE for human-readable feedback as code is written, runtime for save-time
guardrails on data and APIs the IDE can't see.
A new org-wide rule is one file, one function, zero ceremony.
Five sections in customRules.ts cover every flavour of rule —
regex, JS/TS AST, whole-AST, Python AST, Java tree-sitter. Pick the section, write the
check function, ship.
Not a replacement for ESLint. A layer above it.
Generic linters do generic linting well. ScaleArch does what they don't: cross-language org rules, structural anti-patterns, and a no-AST-required path to authoring them.
| ESLint | SonarQube | AI code review | ScaleArch | |
|---|---|---|---|---|
| Cross-language with one ruleset | No | Yes | Probabilistic | Yes — 5 langs |
| Author rules without AST knowledge | No | No | N/A — no rules | Yes — Rule Builder |
| Real-time in IDE | Yes | Plugin | PR-time | Yes — <600ms |
| Deterministic / no AI | Yes | Yes | No | Yes |
| Works offline / on airgap | Yes | Yes | No | Yes |
| Org-wide governance + audit | No | Yes | Limited | Yes — Validator |
| Cost model | Free | $$ enterprise | $ per seat | Free + open source |
Tribal knowledge → enforced standard, in one afternoon.
ScaleArch is designed to be forked. A staff engineer spends an afternoon writing the
rules that come from your last six post-mortems. Distributes the
.vsix internally. Every developer — from day one — gets your
company's coding standards enforced live, in their editor.
Pair with the Validator and the same rules block bad PRs in CI. The dashboard tells leadership which standards developers struggle with most.
Real org-rule examples
In a world chasing AI for everything, I built the boring, deterministic, instant version.
Further left than any tool you have.
Not at PR-time. Not at CI-time. At keystroke-time. The feedback loop is milliseconds, not hours, not days.
Works on the plane.
No tokens. No quotas. No flaky API. Works on a plane, on an airgap, on day one and day one thousand. Same answer, every time.
Built for real teams.
API keys, audit logs, dashboard, rule overrides. Solo dev gets value alone. 200-dev org gets governance.
Good code standards
should enforce themselves.
All three products are live and free to use. The Extension repo is public and forkable.