Folder sync and shared drives
Tessamark requires no central account or subscription sync server. If you store your workspace in a folder managed by iCloud Drive, Dropbox, Syncthing, Nextcloud, or Google Drive, your files sync automatically through that service.
Because cloud providers sync file trees rather than hidden git metadata, Tessamark packages version history into device packs placed inside your folder under .mde/history/. When enabled, your history travels along with your notes, allowing other devices to read past saves.
Reading history from other devices is free at every tier. Publishing this device's version history into the shared folder is part of Tessamark Pro.
Android storage: Android does not support folder sync because workspaces live inside Tessamark's sandboxed app-private storage where external sync daemons cannot read them. On Android, sync operates exclusively through your git remote.
Syncing to a git remote
Self-hosters and team writers can sync version history directly to any standard git repository over HTTPS, including GitHub, GitLab, Gitea, or a private server.
- Open Settings → General on macOS or iOS, or the Sync tab on Linux and Android.
- On macOS and iOS, expand Advanced: sync to a git remote.
- Enter your Remote URL (for example,
https://github.com/you/notes.git).
- Enter your username and a personal access token with repository write permissions.
- Click Save, then test your connection.
Tokens are stored directly in your system's secure keyring (macOS/iOS Keychain, Linux Secret Service, Android Keystore) and never written to plain preferences or files. Pulling and fetching from your git remote is permanently free. Pushing revisions requires Tessamark Pro.
End-to-end encryption (Pro) and the recovery code
End-to-end encryption is a Tessamark Pro feature. When enabled, Tessamark seals your version history and remote sync payloads client-side with authenticated cryptography. Opening notes you have already encrypted is never gated: an existing encrypted workspace remains fully readable on any device even without Pro.
When you enable encryption, Tessamark reseals past commits so that unencrypted history is not leaked to your remote. It then displays a Recovery Code.
If you lose this recovery code and this device, your version history cannot be recovered — by you, by us, or by anyone. That is what end-to-end encryption means. Your current documents are unaffected: they remain plain Markdown files in your folder.
To access an encrypted workspace on a second device, open the workspace and enter this recovery code under Settings → General → Encryption (or Settings → Sync on Linux and Android) to unlock its history.
The merge window (Pro)
Merging outside changes into unsaved edits is part of Tessamark Pro. On the free tier, you can reload the file or keep your version, and both choices stay in your version history.
When you have Pro, Tessamark opens a three-way merge review window rather than making you pick one whole file over another. You see your edits, the historical common base save, and the incoming version on disk, with an editable combined buffer below. For each conflicting section, choose which edits to keep.
Handling outside changes
If another application edits or syncs a note that is open in Tessamark, the app detects the file system change promptly:
- Clean buffer: If you have no unsaved edits, Tessamark reloads the note from disk silently.
- Unsaved edits: If you have unsaved edits, Tessamark displays an external change warning banner. Free users can choose Reload (discarding unsaved local edits in favour of disk) or Keep mine (preserving local edits; if saving was refused, this displays as Overwrite). Tessamark Pro users also see Merge… to resolve overlapping sections.
Under Settings → General (and on Linux/Android under General), Tessamark Pro users can configure When a file changes on disk while you have unsaved edits to merge automatically when changes do not overlap, or always prompt for review.
