Vibeleaderboard
Index / tool
Visit github.com
Category
Developer Tools
Rank
No. 4266Tools index

Previous survey · No. 3945 ·

Pricing
Open Source
Type
TOOL
Use case
Deployment & Operations
GitHub
8 stars
Date

About

sqlite-modal lets you work with SQLite locally as an ordinary file while pushing and pulling changes to a synced server running in a Modal workspace, with a Volume persisting the remote copy on exit. It uses the Turso SDK for syncing and resolves conflicts on a last-push-wins basis; it is not a managed multi-tenant database service.

At a glance

sqlite-modal lets you query a local SQLite file and push or pull changes through a server in your Modal workspace. It is worth a trial if you need local SQL with occasional handoffs between jobs and can control who writes when.

Good fit

Python developers already using Modal who need to move a small database between local work and remote jobs.

Consider something else when

Skip it if writers can edit the same data concurrently and you need both changes preserved automatically.

Start here

Use a disposable database with one sample row. Push it, pull it into a second local file, and verify the row. Then try conflicting edits on the two copies to see which value survives.

Cost and requirements

Apache-2.0 project. The documented setup needs Python 3.12 or newer, a Modal account and a deployed sync server. Account for Modal compute and storage when planning costs.

Limits to know

SQL runs against your local file. Push and pull cross the network and sync data through the Modal workspace. The documented conflict rule is last push wins.

Why it made the leaderboard

Gives Modal users a lightweight way to keep a local SQLite working copy synced to durable remote storage without standing up a managed database.

Tags

sqlitemodaldatabasesyncturso

Tech Stack

Python

Comments (0)

No comments yet

Editorially curated, with community endorsements as a secondary signal. Corrections welcome.