Deploy Nogon

Private full-text search engine for your own browsing history

Deploy Nogon

Just deployed

/hister/data

Deploy and Host self hosted Nogon (Other) on Railway

This template deploys Nogon, a self-hosted full-text search engine for your own browsing history, as independent community packaging of asciimoo/nogon v0.22.0 (AGPL-3.0). It is not affiliated with or endorsed by Nogon.

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

This template runs the upstream Nogon release v0.22.0 as a single service named nogon, built from the unmodified upstream ghcr.io/asciimoo/nogon:v0.22.0-root image.

Railway handles the HTTPS domain, the container build, the /health check with a 300 second timeout, and a restart policy of Always.

Why Deploy Nogon, the self-hosted browser history search on Railway

Browser history is hard to search. Nogon indexes the pages you visit so you can search them from one HTTPS URL you control, with access gated by the generated token.

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.

Railway vs Other Hosting Providers and VPS for Nogon self hosting

Railway handles the container, volume, and HTTPS domain for you, while a VPS means doing that setup yourself.

ProviderWhat You Get with RailwayWhat You Get with the Other Provider
DigitalOceanOne Nogon service with a volume at /hister/data, a generated access token, and a public HTTPS domain.A bare Droplet where you install Docker, manage storage, the token, and the domain yourself.
AWSThe same one-service setup with health checks on /health and no networking to configure.Full control of networking and storage, with more configuration to maintain.
HetznerDeployment from the template with no server sizing or OS upkeep, and one replica with its data volume attached.Low-cost servers where you choose the hardware and run Nogon with your own Docker setup and backups.

Pick the option that matches how much of the server you want to manage.

Common Use Cases for hosted Nogon

  • Searching pages you read last month: You install the browser extension, and the pages you visit are indexed so you can find an article by a phrase you remember from it.
  • Recovering a half-remembered reference: Instead of scrolling back through browser history, you run a full-text search over the index on your own server.
  • Keeping research trails private: The index lives on a volume in your own Railway project, so your browsing history is not sent to a third-party search service.
  • Working from several browsers: Point each browser's extension at the same HTTPS URL with the same access token, and one search covers everything you visited.
  • Querying history from AI tools: Nogon's upstream project describes MCP access, so you can let an assistant search the same index you use yourself.

Dependencies for Nogon Docker hosted on Railway

This template deploys one service from the Nogon container image, with a health check, a restart policy, and one persistent volume.

Deployment Dependencies for Managed Nogon Service

The template creates one public service named nogon on port 8080, with a volume at /hister/data, a health check on /health with a 300 second timeout, and restart policy Always. Keep one replica, because the index is local persistent state on that volume.

Implementation Details for Nogon

The image ghcr.io/onepush-dev/nogon:v0.22.0 is the unmodified upstream ghcr.io/asciimoo/nogon:v0.22.0-root image with Railway defaults baked in. The -root variant is used so the Railway volume on /hister/data is writable. The wrapper bakes NOGON__SERVER__ADDRESS=0.0.0.0:8080 and HISTER_DATA_DIR=/hister/data.

The template defines two variables, and you supply no inputs:

  • NOGON__APP__ACCESS_TOKEN: a generated token. Access to the web UI and the browser extension goes through this token. Enter the same value in both places, or send it in the X-Access-Token header. Without a token, the server would be public, so this template always generates one.
  • NOGON__SERVER__BASE_URL: the Railway HTTPS domain. Update it if you add a custom domain.

How does Nogon compare against other tools

Nogon vs Keeping History Only in the Browser (Browser History Alternative)

  • Searchable Index: Nogon builds a full-text index of the pages you visit. The browser wins on simplicity because nothing extra needs to run.
  • Data Location: Your index lives on a volume you control on your own server. Browser history is simpler to back up when you already sync your browser.
  • Access Control: Access goes through the generated NOGON__APP__ACCESS_TOKEN, entered in the web UI and the browser extension.

Nogon vs a Hosted Search Product (Hosted Search Alternative)

  • Ownership: Nogon runs on infrastructure you pick and keeps the index on your own volume. A hosted product handles upkeep for you.
  • Cost Model: Nogon is AGPL-3.0 open-source software, so you pay only for the infrastructure it runs on. Hosted products usually bundle hosting into a subscription.
  • Operations: You maintain updates and backups of the /hister/data volume yourself. Hosted services typically remove that work.

Nogon with Docker vs Railway (Docker and Railway Alternative)

  • Setup Effort: Running the unmodified upstream image with Docker means handling the port, volume, and health check by hand. This template bakes in the listen address and data directory, with a health check on /health.
  • Control: Docker on your own host gives full control over networking. Railway trades some of that control for a managed deploy flow.
  • Replicas: Keep one replica, because local persistent state on /hister/data should not be shared across copies.

How to use Nogon on Railway?

  1. Open the public Railway domain for the nogon service in your browser. Sign in with the value of NOGON__APP__ACCESS_TOKEN, which you can read from the service Variables tab.
  2. Install the Nogon browser extension and point it at the same HTTPS URL. Enter the same NOGON__APP__ACCESS_TOKEN so the extension can send indexed pages to your instance.
  3. If you add a custom domain later, update NOGON__SERVER__BASE_URL to match it so links and sign-in work correctly.
  4. Keep the service on one replica, because the index lives on the local volume at /hister/data.
  5. Confirm the deployment is healthy by checking the /health endpoint, which the template uses with a 300 second timeout.
Public URL:      https://your-domain.up.railway.app
Access token:    NOGON__APP__ACCESS_TOKEN (from Variables)
Health check:    /health (timeout 300 seconds)
Replicas:        1
Volume:          /hister/data

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

Nogon is AGPL-3.0 software, so you can run it on any Linux VPS with Docker. The steps below use the upstream flow.

Clone the Repository

Clone the upstream project and check out the release you want to run.

git clone https://github.com/asciimoo/nogon.git
cd nogon
git checkout v0.22.0

Install Dependencies

You need Docker on the host. Nothing else is required to run the pinned image.

docker --version

Configure Environment Variables

Set an access token so the server is never open to the public, and set the public base URL to match your domain.

export NOGON__APP__ACCESS_TOKEN="generate-a-long-random-token"
export NOGON__SERVER__BASE_URL="https://your-domain"

Keep the token secret, since you enter it in the web UI and the browser extension.

Start the Nogon Application

Run the documented nogon container with a data directory mounted so the index persists, then check the health endpoint.

docker run -d --name nogon -p 8080:8080 \
  -v nogon-data:/hister/data \
  -e NOGON__APP__ACCESS_TOKEN \
  -e NOGON__SERVER__BASE_URL \
  -e NOGON__SERVER__ADDRESS=0.0.0.0:8080 \
  ghcr.io/asciimoo/nogon:v0.22.0-root
curl -s http://localhost:8080/health

For full details, see the upstream repository. On Railway, the platform handles the domain, HTTPS, the volume and restarts for you.

Pricing and License of Nogon (Nogon pricing)

Nogon is open-source software released under the AGPL-3.0 license, and it is free to self-host.

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

This template packages the AGPL-3.0 software, and no hosted search plan prices are quoted here.

Monthly cost of self hosting Nogon on Railway

Railway billing is usage-based, so the monthly cost depends on the RAM and CPU the service uses, the size of the /hister/data volume, and any other services you add.

System Requirements for Hosting Nogon on a VPS

Nogon runs as a single service that stores its index on disk, so a VPS needs enough memory and disk for the index and the server process. Keep one replica for local persistent state.

Frequently Asked Questions (FAQs)

How do I sign in to my Nogon instance?

Open the public Railway domain and enter the NOGON__APP__ACCESS_TOKEN value from the service Variables tab into the web UI.

How does the browser extension authenticate?

The extension uses the same access token as the web UI. Point it at the same HTTPS URL and enter the same NOGON__APP__ACCESS_TOKEN value.

What should I back up?

Back up the volume mounted at /hister/data, which holds the search index. Keep the access token somewhere safe too, since you need it to sign in after a redeploy.

Do I need to change anything for a custom domain?

Yes. Update NOGON__SERVER__BASE_URL to the new HTTPS URL so links and sign-in use the custom domain. Keep one replica, because the local index on the volume is not shared between replicas.

Is this affiliated with Nogon?

No. This is independent community packaging of asciimoo/nogon v0.22.0 (AGPL-3.0), and it is not affiliated with or endorsed by Nogon.


Template Content

More templates in this category

View Template
Rocky Linux
Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀

codestorm
51
View Template
Foundry Virtual Tabletop
Self-hosted virtual tabletop for role-playing games (license required)

Lucas
71
View Template
NEW
Double Commander in your browser
The Double Commander file manager in the cloud, from any device

Nermin Sabanovic
0