Name: NiubiGEO
Availability: InStock
Author: onepush

Deploy and Host self hosted NiubiGEO (AI Visibility Reports) on Railway

This template deploys NiubiGEO, an open-source tool showing how AI models describe your brand, which competitors they name and which sources they cite.

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

This template runs one NiubiGEO container built from the community-maintained onepush-dev/niubigeo:0.3.3 image, which wraps the upstream v0.3.3 release (Apache-2.0) with a login gate and a schedule worker.

Why Deploy NiubiGEO, the open-source AI visibility reporting tool on Railway (Railway Free Trial)

Peec AI is a hosted SaaS, so you pay a subscription and the reports stay on their platform. Model charges still apply, so a trial will not predict your steady monthly bill.

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 NiubiGEO 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 NiubiGEO self hosting

Railway runs the container, volume and variables; a VPS leaves those to you.

Provider	What You Get with Railway	What You Get with the Other Provider
DigitalOcean	A managed deploy with the login password generated and a persistent volume attached.	A droplet where you install Docker, mount storage for /app/data and manage the login gate.
AWS	One application with a schedule worker and volume, without building networking first.	Broad service choice across EC2 and EBS, with each piece configured and maintained by you.
Hetzner	Setup with no server administration for the workbench and worker.	Low-cost servers where you manage the OS, Docker and backups of the data directory.

Keep one replica for local persistent state, since the data lives in the attached volume.

Common Use Cases for hosted NiubiGEO

Brand-description checks: Ask several models to describe your product and compare whether they name the right category, features and audience. Inaccurate descriptions can flag site or docs content needing clearer wording.
Competitor comparisons: Run the same prompts for your brand and rivals, then review which competing products each model links to your category. Co-mention differences can show where to look at positioning.
Inspect answer evidence: Open the original answer and any returned sources behind a finding before you act on it. This stops one surprising response from driving decisions alone.
Repeated prompt monitoring: Re-run the same keyword set over time so that changes are measured under the same conditions. Failed runs stay on record, helping you judge each data point's reliability.
Scheduled GEO reports: The worker collects comparable runs on a schedule for review in one place. Remember that scheduled runs consume your model provider credits.

Dependencies for NiubiGEO Docker hosted on Railway

This template runs NiubiGEO as one Docker service built from onepush-dev/niubigeo:0.3.3, which wraps the upstream v0.3.3 release with a cookie login gate and a schedule worker.

Deployment Dependencies for Managed NiubiGEO Service (one application, cookie login gate and schedule worker; persistent /app/data volume)

The workbench and schedule worker run together as one application. Do not scale to multiple replicas, since the volume is not shared.

Implementation Details for NiubiGEO (onepush-dev/niubigeo:0.3.3 adds auth and scheduler around upstream image)

The image defaults NIUBIGEO_USERNAME to admin, NIUBIGEO_WORKER_ENABLED to true and NIUBIGEO_WORKER_INTERVAL to 60. The template runs the gate and the worker in one container. NIUBIGEO_PASSWORD is a generated template variable for the login gate; it is separate from the optional, non-generated OPENROUTER_API_KEY. Changing NIUBIGEO_PASSWORD changes the gate password only and does not bootstrap an upstream account.

How does NiubiGEO compare against other tools

NiubiGEO vs Peec AI (Peec AI Alternative)

Source access: NiubiGEO is Apache-2.0 open source, so you can read, run and change the code. Peec AI is a hosted commercial product used as the vendor provides it.
Data location: With NiubiGEO on your own Railway project, you choose where the stored runs live. Hosted tools keep your data on their infrastructure.
Where Peec AI may win: For a managed service with vendor support and no infrastructure to maintain, a hosted product is easier.

NiubiGEO vs Profound (Profound Alternative)

Cost model: NiubiGEO is free to self-host. You pay for Railway usage and for the model API calls you make with your own key.
Evidence view: NiubiGEO lets you open the original API answer and its returned sources for each result, so you can check a finding yourself.
Where Profound may win: Hosted platforms with large prompt datasets and marketing workflows can offer breadth a single self-hosted tool does not match.

NiubiGEO vs Ahrefs Brand Radar (Ahrefs Brand Radar Alternative)

Scope: NiubiGEO tests the models you configure, using the API responses they return. It is not a search index or a consumer chat interface.
Setup: You deploy NiubiGEO once and keep it running. Brand Radar is a subscription inside an existing SEO suite.
Where Brand Radar may win: If you already rely on Ahrefs data, its index and history are a strong reason to stay. Small samples from any tool, including NiubiGEO, do not prove SEO growth alone.

NiubiGEO with Docker vs Railway

Setup effort: Docker on a VPS means you manage the host, volume and updates. Railway handles the container and networking.
Persistence: Both options can keep the /app/data volume. On Railway, keep one replica for local persistent state.
Upgrades: Back up the data directory before you change image versions, whichever host you use.
Where Docker may win: A plain Docker host offers more control over networking and resource limits, without usage-based billing.

How to use NiubiGEO on Railway?

Open the deployed service URL and log in as admin with the NIUBIGEO_PASSWORD value from your Railway Variables.
Add a provider key in the browser, then create your first report. Browser keys are temporary and unavailable to the worker.
For reports the server runs and for the worker, set OPENROUTER_API_KEY in the service Variables tab so it persists.
Open the report and inspect the evidence behind each finding before you trust it.
Scheduled runs call your model provider and cost provider money, so set NIUBIGEO_WORKER_ENABLED=false in Variables if you do not want background runs yet.
Check the health endpoint to confirm availability only, not that AI calls succeed:

GET /health

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

Use the upstream Docker flow at v0.3.3 and persist data on your own host.

Clone the Repository

Clone the pinned release so your deployment matches what you tested.

git clone --branch v0.3.3 --depth 1 https://github.com/Albert-Weasker/niubigeo.git
cd niubigeo

Pull and Start with Docker Compose

Pull the published v0.3.3 image and start the service without a local build.

docker compose pull
docker compose up --no-build -d niubistar-geo

Optional monitoring runs as a separate worker on the same VPS, using the same image and data directory:

docker compose --profile monitoring up --no-build -d niubigeo-worker

Add Your Own Access Control

Upstream v0.3.3 has no built-in login. Before exposing the service, deploy your own TLS and authentication boundary, such as a reverse proxy with authentication. Do not publish the port without it.

Railway handles HTTPS and volume attachment; on a VPS you manage these yourself.

Official Pricing of NiubiGEO (NiubiGEO pricing)

NiubiGEO is Apache-2.0 open-source software, free to self-host with no vendor fees for the open-source edition.

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

NiubiGEO Community Edition is free to self-host under Apache-2.0; you bring your own model API keys.

Monthly cost of self hosting NiubiGEO on Railway

Railway bills by usage, so monthly cost depends on RAM, CPU, volume storage and services consumed.

System Requirements for Hosting NiubiGEO on a VPS

Requirements depend on workload, volume size and models tested. Confirm capacity on your host before relying on scheduled runs.

Frequently Asked Questions (FAQs)

Is there a login on the workbench?

Yes. The gate uses the admin username and the generated NIUBIGEO_PASSWORD value. Keep it private; upstream has no built-in login.

Is an API key required to use NiubiGEO?

The app starts without one, but you need a model provider key for useful reports. Browser keys are temporary, so use Variables for anything you rely on.

Are keys entered in the browser saved permanently?

No. Browser-entered keys are temporary and are not available to the worker. Store the key as the OPENROUTER_API_KEY Railway variable instead, which the server and worker can use.

Can I turn off the monitoring worker?

Yes. Set NIUBIGEO_WORKER_ENABLED to false in Variables to stop scheduled runs.

Does NiubiGEO measure exactly what consumer ChatGPT shows users?

No. NiubiGEO observes responses returned through provider APIs, not the consumer chat interface, so results may differ from what end users see.

What should I back up?

Back up the /app/data directory, which holds your products and monitoring records. Keep one replica, since local state lives in that volume.