Kiiind of. For the syncserver itself, where all the data is synced and stored, you just need tokenserver+syncstorage, plus a database backend of choice. Easy-p

Kiiind of. For the syncserver itself, where all the data is synced and stored, you just need tokenserver+syncstorage, plus a database backend of choice. Easy-peasy, you can set it up trivially in minutes if you're used to spin up docker containers and have a database server. Loads of people do this. However, you still need a way to authenticate. Most people just piggyback on Mozilla's servers for this. This means some metadata (not the synced data itself, mind you, but still) will be shared with Mozilla and a surprising number of third-parties. To get the last meter and be fully self-reliant you need to go down quite the rabbit hole and set up the fxa stack. It involves several interconnected microservices and a handful of separate mysql databases. I managed to but it took a couple of days to dig through the sources and figure out exactly what is necessary and disable all the third-party integrations. The pieces are all there and it's all done in the open but it's clearly built with the mindset of a cloud-based startup. https://github.com/mozilla/fxa https://github.com/mozilla/fxa Once up and running it has been hands off, not much maintenance at all. Happy I did it but unless you like doing this kind of stuff as a challenge, I'd probably recommend using some alternative extension, until it becomes more approachable. If you take it on, there are helpful people in the #fxa:mozilla.org Matrix room. More activity there, and self-hosting related discussion/issues/PRs in the fxa github repo, might push them to put in more effort to make it easier to self-host the stack and bring/keep docs up to date. Hoping to do a proper write-up soon to make it more approachable for others, once things cool down a bit at work.