[3np]

I recently set up a Firefox Accounts server - basically the minimum parts necessary for a self-contained FFSync, without either calling home to Mozilla or their integrated third-parties (mostly payments and analytics; AWS, GCP, Paypal, Stripe, and a few others). A handful of microservices and a few MySQL databases and I think a Redis or two? I only recommend doing it if you enjoy it for the challenge, the stack it's clearly not engineered with an independent self-hoster in mind (though they do support it and people are helpful). It took several days to get up and running. I will share this soon, I hope...

In the meantime, if this all sounds like too much but you'd still like self-hosted FFsync, you can run the syncserver docker image standalone and piggyback on the rest of Mozilla's hosted FXA stack.

I'm not certain just how big the gap is for Pocket ATM (I know they've continuously been opening up since acquisition).

EDIT: Just to not be that guy, microservices as this isn't clearly documented anywhere:

  * pushbox (mysql)
  * fxa-auth-server (redis, 2xmysql, smtp)
  * browseridverifier
  * syncserver (actually tokenserver+syncstorage, if you're not running the docker image. db of choice)
  * fxa-contentserver
  * fxa-graphql-api
  * fxa-profile-server (mysql)

...and "just glue them together" with JWT tokens (look for the scripts in the repo instead of trying to find enlightenment through the source code, docs and issues... heh) and your reverse proxy or load balancer of choice.