---
title: "Deploy LinkAce"
description: "Self-hosted bookmark archive with tags, lists and link checks"
category: "Other"
url: https://railway.com/deploy/deploy-linkace-bookmark-archive
---

# Deploy LinkAce

Self-hosted bookmark archive with tags, lists and link checks

**[Deploy LinkAce on Railway](https://railway.com/template/deploy-linkace-bookmark-archive)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/deploy-linkace-bookmark-archive/manifest.json

- **Creator:** onepush
- **Category:** Other

## Template content

### linkace https://api.iconify.design/mdi/bookmark-box-multiple-outline.svg

- **Image:** ghcr.io/onepush-dev/linkace:v2.6.3@sha256:7529ef1ed38774df28b86835c878e7e83cced4d8ff65648ca076ad33c647c26a
- **Health check:** /login
- **Public domain:** Yes

### postgres https://devicons.railway.app/postgres

- **Image:** postgres:17-alpine

## Documentation

# Deploy and Host self hosted LinkAce (Other) on Railway

This template deploys LinkAce, a self-hosted bookmark archive with tags, lists and link checks, as independent community packaging of Kovah/LinkAce v2.6.3 (GPL-3.0). It is not affiliated with or endorsed by LinkAce or Kevin Woblick.

## About Hosting LinkAce open-source software on Railway (self hosted LinkAce template)

This template runs the unmodified upstream LinkAce v2.6.3 application, released under GPL-3.0, with Postgres in place of the upstream MariaDB default.

## Why Deploy LinkAce, the self-hosted bookmark archive on Railway

A hosted bookmark service stores your links, notes and tags on its servers under its terms, which limits control over exports and retention.

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying LinkAce on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

### Railway vs Other Hosting Providers and VPS for LinkAce self hosting

Self-hosting LinkAce means deciding how much server work you want to do yourself.

| Provider | What You Get with Railway | What You Get with the Other Provider |
|---|---|---|
| DigitalOcean | Two linked services from one template, with Postgres on a private network and a volume for local files. | A virtual machine you control fully, where you install Docker, manage the firewall, and handle updates. |
| AWS | One deploy step with generated secrets and a health check on /login, without building networking first. | A wide set of services you can combine, which gives flexibility but requires configuring each piece. |
| Hetzner | Managed deployment of the app and Postgres with no server administration on your side. | Low-cost servers that give you full control, along with the work of keeping them secure and running. |

Pick the path that matches how much server work you are willing to take on.

## Common Use Cases for hosted LinkAce

- **Personal research archive:** Save articles, papers and tools as you read them, tag each one by project, and group them into lists so a topic stays findable months later.
- **Link rot checks:** Let LinkAce check whether saved URLs still resolve, so you find out a reference is dead before you need it rather than after.
- **Shared team reading list:** Run one instance for a small group, keep public or private lists per topic, and let members add links through the web UI.
- **Bookmark migration:** Import an exported bookmarks HTML file into a fresh instance, then clean up tags and lists in one place instead of across several browsers.
- **Long-term reference store:** Keep your collection in bundled Postgres with local files on a Railway volume, so the data stays under your control and you can back it up on your own schedule.

## Dependencies for LinkAce Docker hosted on Railway

This template runs two services: linkace, the unmodified upstream image with a start wrapper, and postgres on the private network. Keep one replica of each.

### Deployment Dependencies for Managed LinkAce Service

The linkace service is public on port 8080 with a volume at /app/storage/app, a /login health check with a 300 second timeout, and a restart policy of Always. The postgres service is postgres:17-alpine and restarts On Failure.

### Implementation Details for LinkAce

The start wrapper writes /app/.env from the service variables, converts APP_KEY into Laravel base64 format, runs database migrations, marks setup complete, and creates the first admin when no users exist. It then runs the Laravel scheduler every minute, which is how link checks and import queue jobs are started, and patches Caddy so Railway HTTPS redirects work. Redis and Meilisearch are not included, and this packaging uses Postgres rather than the upstream MariaDB default.

The template asks for six variables, all generated or referenced:

- **APP_KEY**: generated, encoded to a Laravel base64 key at boot. Keep it stable.
- **APP_URL**: your Railway HTTPS domain. Update it if you add a custom domain.
- **DB_HOST**: references the private hostname of the postgres service.
- **DB_PASSWORD**: references the postgres password.
- **LINKACE_ADMIN_PASSWORD**: generated password for admin@example.com.
- **POSTGRES_PASSWORD**: generated superuser password on postgres.

## How does LinkAce compare against other tools

### LinkAce vs a hosted bookmark service (Hosted Bookmark Service Alternative)

- **Data ownership:** LinkAce runs in your own Railway project, so the Postgres database and local files stay under your control.
- **Ongoing cost:** LinkAce is GPL-3.0 and free to self-host, but you pay for the Railway usage behind it.
- **Where the hosted service wins:** Mobile apps, sync across clients and managed upgrades are easier with a hosted product.

### LinkAce vs browser bookmarks alone (Browser Bookmarks Alternative)

- **Structure:** LinkAce adds tags, lists and notes, which suits a large collection better than a folder tree.
- **Link monitoring:** LinkAce's automated checks flag links that stop resolving or move, which browser bookmarks cannot do.
- **Where browser bookmarks win:** They are built into your browser, need no server and suit a handful of links.

### LinkAce with Docker vs Railway (Docker Self-Hosting Alternative)

- **Control:** Docker gives you full control of the host, while Railway manages containers, networking and HTTPS for you.
- **Search and cache:** Redis and Meilisearch are not included here, so search uses the database driver either way.
- **Where Docker wins:** Your own hardware avoids usage-based hosting charges, but you then handle backups, updates and health checks yourself.
## How to use LinkAce on Railway?

Follow these steps on your first day after the deploy finishes.

```
1. Open the public Railway domain for the linkace service. It redirects to /login over HTTPS.
2. Sign in as admin@example.com using the LINKACE_ADMIN_PASSWORD value from the Variables tab.
3. Change the email and password under your profile, so the generated password is no longer in use.
4. Add links or import your bookmarks from an HTML export.
5. If you add a custom domain, update APP_URL to match it so links and notifications point to the right address.
6. Keep one replica of each service. The health check runs against /login.
```

## How to self host LinkAce on other VPS Services (LinkAce self hosting guide)

Follow the upstream flow: upstream: follow the Docker Compose setup, which typically includes MariaDB or Postgres, and optionally Meilisearch and Redis; see the upstream repository.

### Clone the Repository

Clone the upstream project at the v2.6.3 tag so you get the matching code.

```bash
git clone --branch v2.6.3 https://github.com/Kovah/LinkAce.git
cd LinkAce
```

### Install Dependencies

Use the Docker Compose setup from the upstream repository.

### Configure Environment Variables

Create your own environment file with a stable application key and your database details.

```bash
APP_URL=https://your-domain
APP_KEY=your-stable-key
DB_CONNECTION=pgsql
DB_HOST=your-db-host
DB_PASSWORD=your-db-password
```

### Start the LinkAce Application

Bring the stack up, run migrations, then create your first admin account and change its email and password after you sign in.

## Pricing and License of LinkAce (LinkAce pricing)

LinkAce is released under the GPL-3.0 open-source license, so you can run this packaging for free and modify it under the terms of that license.

## LinkAce hosted vs self hosted comparison (Pricing, features, costs, and more)

This template packages the GPL-3.0 software. You run the application and its Postgres database yourself, so you control where the data lives.

### Monthly cost of self hosting LinkAce on Railway

Railway bills on usage, so the monthly cost depends on the RAM and CPU the two services use, the size of the volumes, and how many services you run.

### System Requirements for Hosting LinkAce on a VPS

LinkAce runs as a PHP application with Postgres alongside it, plus local storage and a scheduler.


After each deploy, open the public domain and confirm the /login page loads before you treat the service as ready. Keep one replica of each service, because a second replica would not see the same volume data. Copy APP_KEY and LINKACE_ADMIN_PASSWORD from the Variables tab into your own records, and keep APP_KEY stable across redeploys. If you attach a custom domain, update APP_URL to that origin before you rely on login redirects or notification links. Leave both volumes attached when you redeploy so bookmarks, files and the admin account remain in place. Optional mail, SSO or object-storage backups need credentials you add later and were not part of the recorded first-boot test. The wrapper logs migration and admin-creation lines on first boot, so those messages are the first place to look if sign-in fails.

## Frequently Asked Questions (FAQs)

### How do I sign in after deploying?

Open the public domain from the Railway service, which redirects to the HTTPS login page.

### Should I change the admin account?

Yes. After the first sign-in, change the email and password under your profile so the generated credentials are no longer in use.

### Is Meilisearch included?

No. Redis and Meilisearch are not included in this template, so search uses the database driver that ships with LinkAce.

### What should I back up?

Back up the /app/storage/app volume on the linkace service and the Postgres volume on the postgres service.

### Is this affiliated with LinkAce?

No. This packaging is not affiliated with or endorsed by LinkAce or Kevin Woblick. It runs the unmodified upstream image with a Railway start wrapper.


## 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) — Self-hosted virtual tabletop for role-playing games (license required)
- [Double Commander in your browser](https://railway.com/deploy/double-commander-in-your-browser) — The Double Commander file manager in the cloud, from any device

Open this page in a browser: https://railway.com/deploy/deploy-linkace-bookmark-archive
