Full-stack apps coding agents can ship.
Declare an entity once. Pylon derives the table, the access rules, the API, and the typed React client from it, so a schema change fails at compile time instead of in production.
Typed schema
Entities and fields in TypeScript. Pylon creates the tables and migrates on save.
Live queries
db.useQuery opens a subscription. Every write pushes a diff — no polling, no refetch.
db.useQuery("Order")liveRow-level policies
Access rules sit next to the schema. Every read and write is checked; default deny.
Auth, included
Magic link, 25+ OAuth providers, OIDC, and API keys.
File uploads
Presigned uploads to local disk or any S3-compatible bucket.
Rooms & presence
Cursors, typing, and who is online over the same server.
Faceted search
Full-text queries with live facet counts, updated in the same transaction as your writes.
SQLite or Postgres
Start on a single SQLite file. Point DATABASE_URL at Postgres and nothing above the driver changes.
Server-rendered React
Queries and policies run on the server for first paint, then the same typed client hydrates and subscribes.
Server functions
Queries, mutations, and actions in TypeScript files, validated and called through the typed client.
Reactive server queries
Joins and derived data. The server tracks what it read and re-runs when those rows change.
Scheduled & deferred work
runAfter, runAt, and cancel. Delays and retries run in the same process — no separate worker.
Admin studio
Browse tables, inspect live queries, and tail logs at /studio. Admin-gated in production.
Pick what you need. Every piece shares one schema and one runtime.
Explore the product →Give agents a system they can inspect.
Pylon keeps rules, commands, generated types, local data, and logs inside the workflow. Your agent can scaffold, run, debug, and deploy without guessing which console owns the next step.
Rules live in the repo
New apps include AGENTS.md, and the Pylon skill installs with npx skills add pylonsync/pylon. The agent reads the conventions before it edits code.
The path is command-line
npm create @pylonsync/pylon scaffolds the app. pylon dev runs it locally. pylon deploy ships it to Cloud.
Generated types catch drift
pylon codegen builds the client from your schema and functions. Bad entity names, missing fields, and wrong arguments fail at compile time.
Runtime state is visible
The agent can inspect tables, live queries, and logs in /studio while pylon dev runs. Debugging happens against current data.
Your app model stays in TypeScript.
Declare an entity and its access policy. Pylon creates the table, REST and realtime API, row-level checks, and typed React client. That keeps resolvers, an ORM layer, and a separate backend service out of your stack.
// one entity → a synced table + typed clientconst Order = entity("Order", { customer: field.string(), total: field.float(), paid: field.boolean().default(false),}); // access rules next to the schema — deny by defaultpolicy({ entity: "Order", allowRead: "auth.userId != null", allowInsert: "auth.userId == data.ownerId",}); // the React side — live, typed, no fetchconst { data } = db.useQuery("Order");Deploy from GitHub or the CLI.
Connect GitHub
Install the Smallware GitHub App once. Pushes to the default branch deploy; pull requests get previews that disappear after merge.
- 1.Create a project and connect a repo.
- 2.
git push origin maintriggers a deploy. - 3.Live at
your-app.smallware.run.
pylon deploy
Use the CLI for CI, locked-down environments, or a manual release. It reaches the same Cloud runtime as the GitHub flow.
Scale from one dashboard.
Every app sits behind a global edge network. Resize machines, add replicas and regions, or expand storage from the same dashboard, without pre-provisioning or per-seat pricing.
Global edge network
Cloudflare's edge provides CDN caching, TLS, and DDoS protection worldwide with no extra configuration.
Resize on demand
Add RAM up to 64 GB, choose performance CPUs, and expand the volume without redeploying.
Replicas
Run up to 32 load-balanced replicas per region.
Global regions
Deploy in US, EU, APAC, and South America regions.
Up to 500 GB volume
Grow storage live when the app needs room.
Managed Postgres — private beta
Bundled SQLite by default; co-located managed Postgres is in private beta.
Autostop on idle
Scale to zero when idle, or keep a project always warm.
Custom domains + TLS
Bring your domain; Pylon handles TLS.
SSO — OIDC + SAML
Configure org-level SSO from the dashboard.
Audit log + snapshots
Activity log, one-click volume restore.
Common questions.
Everything else is in the docs.
Which database does it use?
SQLite by default — one file, nothing to provision. Set DATABASE_URL to a Postgres connection string and the same schema and application code target Postgres instead. On Cloud, bundled SQLite is the default and co-located managed Postgres is in private beta.
Do I have to use Smallware?
No. The runtime is a single open-source binary — run it on your own box or container platform with a volume for SQLite, or point it at your own Postgres. Cloud is the managed path, not a requirement, and it runs the same binary.
How do migrations work?
Your schema is TypeScript. In development Pylon diffs it and applies the change on save, so the tables follow the file. On deploy the schema is applied as part of the release, before traffic cuts over.
How do I deploy?
Two ways into the same runtime. Install the GitHub App and pushes to your default branch deploy, with pull requests getting preview environments. Or run pylon deploy from your machine or CI when you want a manual release.
Which clients can talk to it?
A typed React client with server-side rendering, and a Swift SDK for mobile. Every entity also gets a REST and realtime API, so anything that can speak HTTP or WebSocket can read and write subject to the same policies.
What does auth cover?
Magic-link email, 25+ OAuth providers, generic OIDC discovery, guest sessions, and API keys. Whatever the caller signed in with, policies read the same auth.userId, so access rules do not change per provider.
Can it run background work?
Yes — ctx.scheduler.runAfter, runAt, and cancel schedule follow-up work, and delays and retries run in the same process as the rest of your app. There is no separate queue or worker to deploy.
What happens to my data if I leave?
It is a SQLite file or an ordinary Postgres database, with no proprietary storage layer in between. Take a dump and it opens in any client. What you would rewrite on the way out is the SDK calls, not the data.
Create a Pylon app.
The framework is free to self-host. Smallware runs it for you — connect GitHub or deploy from the CLI.