GoKawiilYou don’t hand your whole stack to a framework on faith. So here are the four questions we’d expect from you, answered straight — then open the repo and judge for yourself.
01 Why wouldn't I just build this myself? You could — you've built each piece before: the schema and migrations, the row-level access checks, the session handling, the REST endpoints, the socket that pushes live updates, the generated client. The work isn't the hard part; it's that all of them have to agree, and they stop agreeing the day the schema moves. Pylon generates the whole set from one entity and its policy and regenerates them together on every change. What you buy back is the afternoon you'd otherwise spend re-syncing them by hand.
02 Doesn't a framework lock me in? Your code does import Pylon's SDK — that's real, and it's the trade: one typed model in place of six services you wire together yourself. But the runtime is a single open-source binary you host, sitting on ordinary SQLite or Postgres. There's no proprietary datastore to escape — take a plain dump, or run the whole platform on your own box with no account. The lock-in worth fearing is a cloud engine you can't self-host. Pylon isn't one.
03 Is "agent-native" just marketing? It's a concrete set of affordances: the rules, commands, generated types, local data, and logs all live in one workflow an agent can drive end to end — scaffold, run a migration, read the failure, redeploy — without hopping between four consoles. Run npm create @pylonsync/pylon and watch an agent take it from empty folder to running app. That's the claim, and it's testable.