Show HN: Pylon Sync, an agent-first full-stack realtime framework
12 points
1 day ago
| 2 comments
| pylonsync.com
| HN
I created Pylon to make it easier to move from hobby projects to full production apps.

When I work on hobby projects, I usually use React or Next.js because they are quick to set up and easy to deploy on Vercel. For production apps, I separate the frontend and backend, then deploy the backend on AWS. But setting up a full backend on AWS can be complex and costly, especially for simple apps.

Pylon is a full-stack, real-time framework that includes server-rendered React, TypeScript functions, entities, policies, real-time sync, built-in authentication, and support for background and scheduled jobs. By default, it uses SQLite, but you can switch to Postgres for production. The authentication system is heavily inspired by better-auth. The runtime is a Rust server that runs TypeScript functions and server-rendered React using Bun.

Pylon itself is inspired by Rails and focuses on convention over configuration, so you have fewer decisions to make before deploying. This approach applies to modern React apps, real-time sync, TypeScript server functions, authentication, job management, and deployment.

One of Pylon’s main goals is agent compatibility. It lets coding agents build and deploy apps with no setup, quick understanding, secure defaults, and easy deployment, all without requiring any third-party services. Pylon works for both quick projects and production apps where performance, observability, ownership, and self-hosting matter.

While it’s easy to self-host Pylon apps, Pylon Cloud provides managed hosting with a developer experience similar to Vercel. You can deploy from git or the CLI, get an instant URL, add custom domains, and go live in seconds. Each app runs on its own server, which can scale to zero, with TLS and global caching enabled.

If you have experience with Next.js, Vercel, Convex, Supabase, Firebase, better-auth, or Rails, I’d love to hear your feedback.

Create your first app: npm create @pylonsync/pylon@latest

Website: https://www.pylonsync.com

Repo: https://github.com/pylonsync/pylon

Docs: https://docs.pylonsync.com/introduction

LLMS: https://docs.pylonsync.com/llms.txt

Skill: npx skills add pylonsync/pylon

Examples: https://github.com/pylonsync/pylon/tree/main/examples

jarekdy
23 hours ago
[-]
For realtime full-stack changes, per-PR preview environments are the fastest way to catch weird sync behaviour before merge. Buddy spins one up with its own URL and tears it down on merge.
reply
ericc59
10 hours ago
[-]
That's a good point. Preview environments are definitely on the roadmap.
reply
anentropic
19 hours ago
[-]
Did it occur to you that naming it "Pylon" makes it sound like a Python project...?

(Py- anything is usually Python in this industry)

reply
ericc59
10 hours ago
[-]
It did not. It was a reference to Starcraft tbh.
reply