Roadmap

Where Yentic is headed.

We ship in small, deliberate increments. Autosave and multiplayer are the next major milestones, followed by a cloud execution layer for more languages.

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

Autosave is currently local-first (via browser storage) while we finalize the backend contract. Here's how the cloud flow will work when we flip the switch:

Storage model

Each project will receive a stable UUID. File contents are persisted in a Supabase Postgres table using JSONB for metadata and a compressed text column for code. Large assets will live in Supabase storage buckets referenced by the project record.

Sync cadence

The client batches edits every few seconds. If nothing changed, it sends a heartbeat to keep the session active. We also expose a manual "Save now" action that forces an immediate snapshot.

Conflict resolution

When multiplayer lands, edits merge through operational transforms. Until then, the server keeps the latest snapshot and prior versions are archived so you can roll back if needed.

Get involved

We're looking for teams who want to dogfood the multiplayer builds. Reach out at hello@yentic.com to reserve a spot.