---
title: "Deploy Linkora Sync Server"
description: "Token-protected Linkora synchronization with persistent SQLite."
category: "Other"
url: https://railway.com/deploy/linkora-sync-server
---

# Deploy Linkora Sync Server

Token-protected Linkora synchronization with persistent SQLite.

**[Deploy Linkora Sync Server on Railway](https://railway.com/template/linkora-sync-server)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/linkora-sync-server/manifest.json

- **Creator:** orenaksakal
- **Category:** Other

## Template content

### linkora-sync

- **Image:** sakethpathike/linkora-sync-server:0.3.0@sha256:5e01902af90011c4d6bb9f55f71304eac8d9d09c1d0f10a2fac52ab782c75a57
- **Public domain:** Yes

## Documentation

# Deploy and Host Linkora Sync Server on Railway

Token-protected Linkora synchronization with persistent SQLite.

**Draft status:** Configuration and upstream documentation reviewed. Container startup, Railway application workflows, restart behavior, backup restoration and costs remain unverified.

## About Hosting

Token-protected Linkora synchronization with persistent SQLite.

| Service | Role | Persistent path |
| --- | --- | --- |
| `linkora-sync` | Public application | `/data` |

## Why Deploy

Run this application in your own Railway project, with explicit configuration and storage under your control.

## Common Use Cases

- Personal bookmark sync
- Linkora companion backend

## Dependencies for Linkora Sync Server

### Deployment Dependencies

The application images are pinned by registry digest. Database services, when included, stay on the private network. One replica is supported for each volume-backed service.

## First use

Open the application HTTPS domain and follow the native authentication steps below.

Configure a compatible Linkora client with the HTTPS URL and generated LINKORA_SERVER_AUTH_TOKEN. Railway terminates TLS and forwards HTTP.

## Scope and limitations

- Single-user sync backend without browser management UI or separate per-user accounts.
- Only the HTTP listener is exposed through Railway HTTPS; internal self-signed HTTPS is unused.
- Keep token private and coordinate rotation across clients.

## Acceptance checks before use

- Verify token-free requests cannot access sync content.
- Connect two clients and synchronize a link.
- Restart and verify SQLite persistence.
- Confirm generated credentials are distinct on a second fresh deployment.
- Back up every listed persistent path and database, then restore into a separate test project.
- Measure Railway usage with representative data and workload before estimating operating costs.

## Backups and upgrades

Back up databases, file volumes, encryption keys and configuration together. Keep a copy outside the running project. Review upstream migration notes before changing a digest; rollback can require restoring a compatible database and files, not just selecting an older image.

## Sources and selection evidence

- [Upstream documentation](https://linkora-sync-server-docs.netlify.app/deployment/docker): Official image, SQLite persistence and HTTP listener.
- [Upstream documentation](https://linkora-sync-server-docs.netlify.app/configuration/config-file-env-vars): Environment config, host, port and auth token.
- [Upstream documentation](https://linkora-sync-server-docs.netlify.app/configuration/database): sqlite: database URL format.
- [Upstream documentation](https://raw.githubusercontent.com/LinkoraApp/sync-server/release-v0.3.0/src/main/kotlin/com/sakethh/linkora/Application.kt): Startup requires nonempty keystore password even though Railway exposes only HTTP behind edge TLS.
- [Upstream project](https://github.com/LinkoraApp/sync-server)

Product and alias searches found no matching public Railway listing during this research. This is a bounded search result; private, unindexed or differently named listings may exist. It is not evidence of demand or revenue.

Upstream software retains its own license and edition restrictions. This deployment draft does not imply upstream endorsement.


## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/linkora-sync-server