Storage model
Each project receives a stable UUID. File contents are persisted in Postgres with lightweight metadata and compressed source snapshots. Large assets move to object storage linked from project records.
# roadmap
What's next for All in the Tab.
Autosave and multiplayer are the next milestones. After that, server-side execution for more languages.
# delivery phases
Now, next, and later.
Now
- Local-first autosave keeps drafts in the browser so nothing is lost between refreshes.
- Starter templates for HTML, CSS, and JavaScript with instant preview synchronization.
- Manual share payloads via clipboard while authentication is under construction.
Next
- Cloud sync powered by a Supabase Postgres database storing project metadata and file blobs.
- Incremental snapshotting so only changed files are sent to the server, ideal for fast autosave.
- Authentication via Google or email magic links with workspace-level permissions.
Later
- Realtime collaboration with operational transforms streaming through Supabase Realtime channels.
- Background build agents for Python, Rust, Go, and more using containerized sandboxes.
- Project insights such as activity timelines and restore points.
# autosave blueprint
How autosave will work.
Autosave is currently local-first while we finalize the backend contract. The architecture below outlines the production path.
Sync cadence
The client batches edits every few seconds. When no edits occur, it sends a heartbeat to keep the session active. A manual Save now action always forces an immediate snapshot.
Conflict resolution
When multiplayer lands, edits merge through operational transforms. Until then, the server keeps the latest snapshot and archives previous versions for safe rollback.
Want to join early collaboration trials? Reach out at hello@allinthetab.com.
