Launcher for applications and emulated games that presyncs and postsyncs to cloud providers using your credentials - this allows the cloud provider to act both as a cloud save and an easily accessible remote backup for your gamesaves. allowing easier backup & sync between devices on games that don't support/allow for cloud saves - all for free!
  • Python 61.6%
  • JavaScript 33.3%
  • CSS 3.9%
  • HTML 1.2%
Find a file
2026-07-02 07:03:16 +00:00
backend fix rclone login on windows 2026-07-02 01:59:34 -05:00
components always call backend endpoint to initialize app on start 2026-05-29 18:50:40 -07:00
css wait for db to start before opening main process window 2026-04-27 20:10:38 -07:00
electron don't depent on backend result for initial db loop 2026-05-29 18:51:44 -07:00
.gitignore add multiple components for frontend homepage UI 2026-04-20 22:32:39 -07:00
index.html add multiple components for frontend homepage UI 2026-04-20 22:32:39 -07:00
package-lock.json change file structure to better support more components and setup vite build config for react 2026-04-16 20:34:04 -07:00
package.json add multiple components for frontend homepage UI 2026-04-20 22:32:39 -07:00
README.md hey genius lets test the code before committing next 2026-04-15 22:31:50 -06:00
vite.config.js add build config for electron-builder to package.json 2026-04-16 21:05:27 -07:00

SyncLauncher (TBD) is an application/emulator launcher that uses rclone to presync and postsync your game save data from and to a cloud storage provider you have credentials to use.

the benefits of using a cloud storage provider (i.e. google drive, dropbox, proton drive, S3, whatever rclone supports) is that it also functionally acts as an easily-accessible backup, instead of an "ephemeral save" that you're unable to access outside the launcher.

first time use

you'll be prompted to enter the path to your rclone executable - then you'll be prompted to select an rclone compatible service, enter the necessary credentials for that service, and a name to that remote destination, which will be tested before being accepted, as we don't want you losing your saves!

defining a game and its save

when defining a game, you'll just need to give us the executables path, but you'll need to know where its saves are stored, usually this is in a universal location, i.e. AppData, however, we don't want to commit to guessing, so you'll be defining where they're stored per game - this does mean you're technically able to make a directory choice that's too broad, so be sure to double check your paths as you don't want to end up accidentally dumping the entirety of your system into your google drive free tier and blow your shit up TBD: if we'll have seperate things to handle emulators & emulated titles - i.e. dolphin & totallyLegitGameCubeGame.iso as one game, and dolphin & totallyLegitOtherGameCubeGame.iso as another

when running a game

before running the game, we'll make an attempt to connect to your cloud storage using the credentials you've previously provided to pull the save (Assuming not first-time sync) so that your game save is up to date! once you're done playing, we'll be sure to start a syncing process back to your cloud provider so that your game save is up-to-date there for next time, maybe on another device! that's up to you!

technologies used

for this, despite knowing and understanding the concerns, we have an electron frontend with a python backend. more later. lol.

using python 3.14 during development, likely works on different versions, can't think of anything that's super version specific.