Native React server rendering.
Render your React frontend from the same server that runs your backend. The Pylon binary serves file-based routing, <Link> and <Image>, per-route metadata, Suspense streaming, and on-disk ISR caching.
export async function generateMetadata({ params }) { const p = await getProduct(params.slug); return { title: p.name, description: p.summary };} export default function ProductPage({ params }) { return <ProductView slug={params.slug} />;}- Server-rendered React 19 with file-based routing under app/
- <Link> and <Image> follow familiar conventions and include an image optimizer
- Per-route metadata, streaming Suspense, error and not-found boundaries
- On-disk ISR cache keeps anonymous renders independent of the cloud app
How it works.
The Pylon binary that holds your schema, runs your functions, and drives the sync engine also server-renders your React. The frontend and backend share one server, origin, deployment, and session on every request. This site uses that architecture.
What you’d otherwise wire up.
Each line is a piece teams normally assemble for this one capability. On Pylon it is part of the runtime.
- A separate rendering framework and its own build step
- A data-fetching layer written twice, once per environment
- Hydration mismatches to chase between server and client output
- A second deploy target for the frontend
Apps built with it.
Scaffold any of these with npm create @pylonsync/pylon.
A multiplayer procedural island with three.js in the browser and Pylon SSR and realtime sync on the server. Every visitor moves through the same world.
A shared SimCity-style builder on three.js + Pylon SSR. Every open tab is a co-mayor building the same city live.
A complete SaaS product with a marketing site, onboarding, a multi-tenant dashboard, and Stripe billing. Reach for this one to build a product.
Build it on Pylon.
One framework for your schema, sync, auth, functions, realtime, and SSR. Free to start.