lint vs Poolside AI

Poolside AI operates at the model-and-platform layer. Laguna S 2.1 is a 118B-parameter open-weight model with 8B active and a 1M context window, positioned for frontier-class long-horizon reasoning; Laguna XS 2.1 is 33B params with 3B active and 256K context, built to run on-device. Around those sit single- and multi-agent orchestration with planning and tool use, sandboxed execution environments for generated code, a desktop app and CLI, data connectors to repositories, databases, and warehouses, role-based access control for both humans and agents, end-to-end trace observability, and governance and auditability aimed at regulated environments. Critically, you can inspect, fine-tune, and own the weights.

lint sits at the code-quality layer and does not compete with any of that. It is an agent-first linter for Tailwind design systems: you declare which components exist, which variants they have, and which theme tokens they may touch, and violations come back as fix instructions rather than verdicts. shadcn/no-restyle takes per-component contracts using pattern, allow, and deny lists — so CardTitle can change typography while CardContent changes spacing. shadcn/no-arbitrary-values keeps classes on your theme's spacing scale. Rules are organized by category (layout, spacing, typography), custom messages attach your design-system instructions to errors, and it fits Tailwind v4 with no rewrite. shadcn/ui is not required. It ships as both an ESLint and an Oxlint integration. It is a linter, not a general-purpose JS/TS linter and not a hosted service.

The pricing models could hardly be further apart, and that is the clearest evidence they serve different buyers. Poolside AI lists pricing as contact — there is no published per-seat rate, no self-serve sign-up, and no free trial. That means budget approval depends on a procurement conversation, and Poolside's own not-for list flags this explicitly: buyers who need a publicly listed per-seat price before they can get budget approval are not the target. Expect enterprise licensing around an open-weight model plus a governed platform, with cost shaped by deployment (on-prem, air-gapped, multi-cloud) rather than by seat count. Small teams without an enterprise budget or procurement process are directed elsewhere.

lint costs nothing. It is open source and installed at the repo level, so the real cost is the engineering time to encode your design-system rules — and there is an agent-oriented setup prompt that reads SETUP.md and installs @shadcn/lint. There is no hosted tier, no dashboard, and no CI product to upsell into. For a Tailwind v4 team, the trade is straightforward: zero license spend in exchange for the work of writing contracts. Comparing the two on price is meaningless — one is an enterprise capital-style purchase gated by security review, the other is a dependency in package.json.