Farm.js

Farm.js is an open-source framework for building product-integrated web applications as one coordinated project. It brings pages, server rendering, API routes, middleware, typed clients, integrations, documentation, agent runtimes, and deployment configuration under a common application structure. React 19 is the default interface layer, but the framework also presents renderer choices for Preact, Solid, Vue, and Svelte while keeping routing, server features, server rendering, and hydration on the same contract. The goal is to reduce the seams between a product's interface, backend routes, documentation, and agent-facing surfaces. It also gives a development server one view of page and API requests, which helps a team see the whole application during local work.

Development centers on an app router that keeps pages, layouts, loading states, API endpoints, and typed links in one directory. An API route is defined once, and Farm.js generates a client whose inputs and responses carry the route's types. Advanced route definitions can validate parameters, prepare request data, load the main result, run follow-up work, and specify pending, error, and page components together. This structure is aimed at TypeScript teams that want the boundary between frontend and backend to stay explicit without manually maintaining a second client contract.

Farm.js packages application pieces into one production build, including routes, middleware, typed clients, server rendering, and deployment settings. Built-in Nitro presets target Vercel, Cloudflare, Netlify, self-hosted Node, and other environments listed by the project. The site publishes benchmarks for development startup, production builds, server boot, rendering, and response size against several full-stack frameworks. Those measurements come from Farm.js's own routed fixture and are useful as project evidence rather than a guarantee that every real application will reproduce the same lead.

Integrations connect common product services while letting developers bring existing provider instances. The official set spans authentication, billing, email, background jobs, databases, key value storage, API keys, and interface components. Examples include Farm Auth, Better Auth, Auth.js, Clerk, Auth0, WorkOS, Supabase, Stripe, Polar, Resend, Prisma, Inngest, Trigger.dev, Unkey, and shadcn/ui. Runtime storage can mount drivers such as SQLite, Redis, and S3 for caches, settings, counters, idempotency data, or object-backed values. Local and packaged layers can share routes, middleware, integrations, components, and configuration while project files retain precedence.

Documentation and agent access are part of the product surface rather than a separate site bolted on later. A project can enable MDX documentation with navigation, search, MCP, and agent-ready endpoints from the same source. Every app page can receive a Markdown representation at a corresponding URL or through content negotiation, with an override available when generated output isn't enough. This means a pricing page or product guide can serve browser HTML and an agent-readable Markdown view from the same route. The project also supports reusable layers that combine routes, middleware, integrations, components, and configuration, with the consuming application's files taking precedence. That mechanism is intended to share architecture without forcing every product to copy the same boilerplate. For agent applications, Farm.js can run Eve on Vercel or Cloudflare Agents on Workers, place their routes beside the main app, and preserve each provider's native client SDK instead of adding a duplicate abstraction.

This broad scope makes Farm.js relevant to teams building SaaS products, developer tools, agent applications, or internal systems that need a frontend and operational backend in the same repository. It can replace some assembly work across a router, API layer, documentation framework, deployment adapter, and integration glue. The tradeoff is maturity. The site labels the project at an early 0.1 release, marks native rendering for static regions as experimental, and explicitly warns that the framework evolves quickly. Teams should verify imports against current documentation, pin package versions carefully, and expect a smaller ecosystem than older full-stack frameworks.

Farm.js is available as open-source software, with the source repository linked from the official site. There is no framework subscription described on the homepage. Developers still pay whichever hosting, database, authentication, billing, email, job, model, or other external services they choose to connect. That access posture makes it practical to evaluate in a small application without buying a platform plan, while production adoption should still account for the cost of the surrounding stack and the effort of tracking a young framework's changes. Its strongest fit is a technical team that values typed boundaries and wants human and agent interfaces to grow from the same product foundation.