Farm.js

Farm.js is an open-source full-stack framework for building product applications whose frontend, backend, integrations, documentation, agents, and deployment need to work together. Instead of treating those concerns as unrelated packages, it connects them through one application structure and configuration. React is the default interface layer, while Preact, Solid, Vue, and Svelte are also supported renderers. The framework is aimed at TypeScript teams building a complete product rather than a single static site. Its homepage presents routing, typed APIs, middleware, product services, docs, storage, and production output as parts of the same system.

The development workflow starts with one server for the whole application. Pages and API handlers appear in the same app directory, with familiar files for layouts, loading states, and route content. Farm derives route information from that tree and generates typed clients for API calls, which reduces the gap between a server handler and the code that consumes it. More advanced route definitions can validate parameters, prepare request data, load the main result, and schedule work after the main load. The project page also emphasizes visible request timing during development, so a developer can see page and API activity without assembling a separate observability layer just to understand local behavior.

Integrations are another central part of the framework. Farm shows built-in or supported paths for authentication, billing, email, background jobs, API keys, databases, user interface components, and AI services. The homepage names options such as Farm Auth, Better Auth, Auth.js, Clerk, Auth0, WorkOS, Supabase, Stripe, Polar, Autumn, Resend, Inngest, Trigger.dev, Prisma, Unkey, and shadcn UI. Developers can pass an existing provider instance and keep direct control of the underlying service while using Farm's typed application calls. This is useful for teams that want one integration point without giving up access to a vendor's native SDK or moving business logic into a closed visual builder.

Renderer choice does not discard the rest of the application model. React works with no renderer configuration, and Farm also offers paths for Preact, Solid, Vue, and Svelte. Routing, server features, server rendering, hydration, and deployment stay on the shared contract, although the exact client capabilities can differ between renderers. That flexibility makes the framework relevant to teams with an existing UI preference, but React receives the clearest default path and the optional compiler work. A buyer evaluating Farm for a non-React application should check current renderer coverage rather than assuming every framework feature behaves identically across all five choices.

Production concerns remain inside the same project. Farm packages routes, middleware, typed clients, and deployment settings into one build, with built-in Nitro presets for Vercel, Cloudflare, Netlify, and self-hosted Node. Its documentation feature can create MDX pages, navigation, search, MCP access, and agent-readable endpoints from one source. Layers let teams share routes, middleware, components, integrations, and configuration while allowing the consuming project to override local details. Key-value mounts can use SQLite, Redis, S3, or another driver for caches, settings, counters, idempotency records, and object-backed values. These pieces make Farm broader than a router, though each added provider still has its own setup and operational requirements.

The framework also explores performance and agent-focused features. Its experimental React ahead-of-time compiler prepares a safe subset of state updates during the build and falls back to React when it can't prove that an optimization is safe. Experimental native rendering targets large host-only server component regions while leaving interactive or unsupported trees on React. Farm can also run Eve or Cloudflare Agents beside an application and keep the provider's native client interface. Pages can receive Markdown representations for agent readers, and a docs surface can expose MCP access. These features are optional, so a team can start with ordinary pages, APIs, and integrations before deciding whether compiler or agent infrastructure belongs in the application.

Farm.js is free and open source, with public packages available through common JavaScript package managers. The site announces version 0.1.0 as its first stable release, which is useful progress but also signals a younger ecosystem than established alternatives. Some of its most distinctive rendering work is still marked experimental, provider integrations bring separate accounts and charges, and the supported surface varies by renderer. The practical fit is a team that wants an integrated TypeScript product framework and is willing to verify fast-moving documentation against the installed package version. For that audience, the combination of typed APIs, multiple renderers, product integrations, agent-friendly content, and several deployment targets is the main reason to evaluate it.