Git push hosting for stateful SQLite apps

Your app is faster with SQLite.
Now deploying it is too.

Local SQLite on disk, native binaries, zero downtime deploys, continuous backup, and object storage per project. All wired into a single git push workflow.

Local
SQLite on disk
Native
ffmpeg, ONNX, FFI
Zero
Downtime deploys
Seconds
Backup RPO
S3
Bucket per project
Push
GitHub to live
Local
SQLite on disk
Native
ffmpeg, ONNX, FFI
Zero
Downtime deploys
serverlite.com/dashboard
Serverlite
+ New Project
Dashboard
Overview
Your projects
Manage your apps, track traffic, and monitor deployments.
Projects
3
3 active
Visitors
58,699
Across all projects
Deployments
142
Total deployments
Traffic
Visitor overview
Last 3 months
Dec 28Jan 11Jan 25Feb 8Feb 22Mar 8Mar 22
api service landing page saas app
Projects
All projects
+ New Project
Name Framework Created Status
saas app
SvelteKit Jan 4 Active
landing page
Next.js Feb 12 Active
api service
Hono Mar 1 Active
What it's for

Built for apps that run as real servers

Serverlite runs your app as a normal stateful server with a local data directory, native binaries, and long running processes. The deploy ergonomics you expected from Vercel, for the kind of app you actually built.

SQLite on disk
Queries at memory speed. Full WAL, extensions, joins, transactions. A SQLite file you own, sitting on the same disk as your app.
Native runtimes
better-sqlite3, ffmpeg, ONNX, OCR, Puppeteer. The binaries your app depends on run here unchanged, on Node, Bun, Python, Ruby, or PHP.
Stateful deploys
A new container starts, passes health checks, Caddy cuts traffic over, the old one stops. The /data volume is preserved throughout, with continuous Litestream backup running alongside.
Platform

Everything your app needs, wired together

01

SQLite on local disk

Your database lives on the same disk as your app. Queries at memory speed, full WAL, extensions, joins, and transactions, with the file you own sitting next to the process that reads it.

02

Native runtimes and binaries

better-sqlite3, ffmpeg, ONNX, OCR, Puppeteer, Pillow. Anything that runs on a normal server runs here, on Node, Bun, Python, Ruby, or PHP.

03

Zero downtime stateful deploys

A new container starts, passes health checks, and Caddy cuts traffic over. The /data volume is preserved throughout, so disk state survives every deploy.

04

Continuous SQLite backup

Litestream streams every SQLite commit to durable object storage. RPO measured in seconds. Snapshot and restore from the dashboard.

05

Object storage per project

Each project gets an S3 compatible bucket with scoped credentials, injected as environment variables. Ready to upload to from your app out of the box.

06

Push to deploy

Connect a GitHub repository. Push to a branch. Serverlite builds, deploys, runs migrations, and cuts traffic over. Backups and domains already wired.

Positioning

Every layer your stateful app needs, built in

Five capabilities that define the Serverlite runtime, shown alongside platforms you might also consider.

Vercel, Netlify
Cloudflare Workers, D1, DO
Railway, Render
Fly.io
Serverlite
Local SQLite on disk
Not supported
Remote only
With volumes
With volumes
Built in
Native binaries and FFI
Limited
Not supported
Supported
Supported
Built in
Zero downtime for stateful apps
Stateless only
Stateless only
Caveats
Manual setup
Built in
Continuous SQLite backup
Manual setup
D1 managed
Manual setup
Manual setup
Built in
Object storage per project
Separate
R2 (separate)
Separate
Tigris (separate)
Built in

Serverlite's Litestream replication to durable object storage is the SQLite durability path Fly.io now recommends after deprecating LiteFS. The difference: on Serverlite it ships by default. On Fly, every layer is manual.

Start shipping

Local database, persistent disk, native binaries, and zero downtime deploys, all in one workflow from git push to live.

serverlite.com