ddvk/rmfakecloud
ddvk/rmfakecloud has 1,374 GitHub stars and 132 forks. GitHot measured -1 stars in 24 hours. Last checked 2026-11-08 06:23 UTC. Last push 2026-10-28.
host your own cloud for the remarkable
Measured star growth
- in 24h
- -1
- in 7 days
- Collecting history
- in 15 days
- Collecting history
- in 1 month
- Collecting history
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
README.md
Originalrmfakecloud
This is a replacement of the cloud, in case you want to sync/backup your files and have full control of the hosting environment.
See the project documentation for setup and configuration.
Supported Devices
| Device | Is Supported |
|---|---|
| reMarkable 1 | ✅ |
| reMarkable 2 | ✅ |
| reMarkable Paper Pro | ✅ |
| reMarkable Paper Pro Move | ✅ |
| reMarkable Paper Pure | ✅ |
The current release of rmfakecloud supports file synchronization up to reMarkable software 3.27.1. Newer releases have not been tested yet.
See the documentation for how to setup your device to use rmfakecloud.
Feature Parity With Official Cloud
| Features | Supported | Notes |
|---|---|---|
| File synchronization (1.0) | ✅ | |
| File synchronization (1.5, 2, 3, 4) | ✅ | |
| Send document by email | ✅ | |
| Handwriting recognition | ✅ | |
| Handwriting search | ❌ | |
| Screen sharing | ✅ | |
| Storage integrations | ✅ | |
| Integration with Dropbox | 🟡 | WIP |
| Integration with Google Drive | 🟡 | WIP |
| Integration with OneDrive | ❌ | |
| Integration with WebDAV | ✅ | Nextcloud, Owncloud, ... |
| Integration with FTP | ✅ | |
| Messaging integrations | ✅ | |
| Messaging integration through webhook | ✅ | |
| Calendar integration | ✅ | ICS currently supported |
| Messaging integration to Slack | 🟡 | Not directly, use a webhook with zapier/make/n8n |
| Archive document to cloud | 🟡 | It works but the information is not saved |
| Passcode (PIN) reset | ✅ | reMarkable 1 / reMarkable 2 only |
| Document rendering in web interface | ❌ | WIP |
Breaking Changes
- For SW >= 3.15
STORAGE_URLshould not be set (or only https://some.ho.st without a port should be used) - after v0.0.3 the files in
/datawill have to be manually moved to the user that will be created - with v0.0.5 the new diff sync15 is added as an option, in order to use it modify the user with
setuser -u user -sor modify the profile and addsync15:truea full resync will be needed (the tablet will do it), the old files are kept as they were and everything is put in a new directory
Development
run ./dev.sh which should start the UI and backend
Caveats/ WARNING
- (applies when you don't have security, version <= 0.0.3) connecting to the api will delete all your files, unless you mark them as not synced
synced:falseprior to syncing (advisable just to disconnect, reconnect the cloud) - if you delete files from the users directory on the host, on the next sync those will be deleted from the device
- if you delete the whole user directory (by mistake) on the host, you should disconnect the cloud from the device and reconnect it
- after an official update, the proxy and hosts file changes will be removed, the tablet will automatically disconnect from the cloud (by sending an invalid token to the official cloud and getting 403) just reinstall the proxy and reconnect to your cloud
Troubleshooting
check the connectivity between the tablet and the host: ping my.remarkable.com (should be localhost) ping local.remarkable.com (should be localhost) ping thehostpc wget -qO- http://host:3000 (or relevant ports, should get Working...) wget -qO- https://local.appspot.com (should get Working...)
check that the proxy is running and certs are installed:
echo Q | openssl s_client -connect localhost:443 -verify_hostname local.appspot.com -CAfile /etc/ssl/certs/ca-certificates.crt 2>&1 | grep VerifyYou should see: Verify return code: 0 (ok)
if both (host and tablet) are on a wifi make sure "Client Isolation" is not activated on the AP
check if the proxy is configured correctly
systemctl status proxy #or journalctl -u proxycheck whether the CA cert was installed correctly when doing
update-ca-certificatesthere should have been1 addedcheck the logscheck xochitls's logs, stop the service, start manually with more logging
systemctl stop xochitl QT_LOGGING_RULES=rm.network.*=true xochitl | grep -A3 QUrlif you see SSL Handshake failed then something is wrong with the certs
check sync logs
journalctl -u rm-sync
Explore related projects
codecrafters-io/build-your-own-x
Master programming by recreating your favorite technologies from scratch.
560,842 starspublic-apis/public-apis
A collective list of free APIs
497,090 starsmorluto/rea
Reverse engineer anything with agents, from app behavior down to native binaries.
441,585 starsopenclaw/openclaw
The AI that really does things. Any OS. Any Platform. The lobster way. 🦞
394,158 stars