React, with the platform behind it
You don’t need Next.js to ship a complete React app.
Write the product. Somewhere runs the backend and handles eligible public-page rendering. There is less for you and your agent to assemble, operate and maintain.
Start buildingKeep the app. Skip the backend assembly.
A complete app needs more than pages: users, data, permissions, files and work that keeps running after a request ends. Somewhere supplies those capabilities through one project. Your agent can build the interface and business logic against that contract.
Deploy raw React and TypeScript source. The platform compiles it, runs server functions and serves the app. Declare data access once and use the generated client instead of rebuilding ownership checks in every browser request.
What you can use today. What comes next.
Live means available now within the scope below. Building means implementation is underway. Planned means a direction, not a shipped capability. Reviewed October 24, 2026.
Public pages with real content
Eligible public routes can serve rendered HTML, including declared public database reads. The platform caches that output and invalidates it when its tracked data changes. Generated sitemaps can include discovered public data routes.
One app, one backend contract
Sign-in, database access rules, files, email, AI and background jobs are available through the platform. Your app still decides its business rules and which actions a person may take.
A clearer next step when something fails
We are improving agent-facing errors and connecting shape-only failure evidence to incident triage. Automatic reproduction and rollback signals are not complete.
Data ready with the first private page
Signed-in page prefetch would deliver authorized data with the page, without putting personal results in a shared cache. It is not available today.
How public rendering works.
Public rendering happens on demand; it does not hold up deployment. On a first visit, the platform waits up to 2.5 seconds for rendered output, then can serve the browser-rendered page while rendering finishes. Unsupported pages also use browser rendering.
The shared render path accepts anonymous public reads. Signed-in and private data are excluded. Dynamic sitemap discovery is bounded; it is not a promise to enumerate every possible application URL. Tracked data changes invalidate cached output; the accepted cache age ceiling is 120 seconds, not a guaranteed sub-minute refresh for every route.
You keep writing ordinary React and declared data access. There are no authored server loaders for this public rendering path. Somewhere does not execute Next.js App Router, Server Component or ISR application code.
Build around your product.
Next.js provides a framework for server and client components, routing and application rendering. Somewhere provides an integrated app platform. Moving an existing Next.js app means adapting its framework-specific code; this is not a drop-in Next.js runtime.
For a new React app that needs a managed backend, you can start directly with Somewhere. Compare the platform responsibilities.
Framework reference: Next.js server and client components.