Deploy Google Chrome

Deploy and Host Google Chrome on Railway

Google Chrome is a widely used web browser developed by Google, built on the Chromium engine for fast, secure, and compatible web browsing. This Railway template deploys Google Chrome as a persistent cloud browser with remote desktop access, powered by the LinuxServer.io Docker image and Selkies streaming technology.

About Hosting Google Chrome

Hosting Google Chrome on Railway allows you to run a fully functional browser in the cloud without managing virtual machines, installing desktop environments, or maintaining a custom GitHub repository.

This template uses the LinuxServer.io Google Chrome Docker image, featuring Selkies for browser-based remote desktop streaming. Railway handles container deployment, networking, and HTTPS termination, while a persistent volume preserves browser profiles, bookmarks, extensions, and settings across redeployments.

The deployment supports configurable authentication, shared memory allocation, and desktop hardening. Google Chrome runs as a single containerized service without requiring external databases or additional infrastructure, making it suitable for remote browsing, web application testing, and persistent cloud workspaces.

Common Use Cases

• Personal Cloud Browser: Maintain a dedicated Google Chrome browsing environment accessible from different devices.
• Remote Browser Access: Access a graphical Chrome desktop through a web browser without installing additional remote desktop software.
• Web Application Testing: Test websites, frontend applications, and web services using Google Chrome.
• Persistent Browser Sessions: Preserve bookmarks, extensions, browser preferences, and profiles across deployments.
• Remote Development Workspace: Access web-based IDEs, API documentation, dashboards, and administrative interfaces.
• Browser Isolation: Separate browsing activity from your local operating system using a containerized environment.
• Cloud-Based Productivity: Access browser-based productivity applications from a remotely hosted workspace.

Dependencies for Google Chrome Hosting

• Docker Image: lscr.io/linuxserver/chrome:latest — LinuxServer.io Google Chrome container.
• Selkies: Integrated web-based remote desktop streaming environment.
• Persistent Storage: Railway volume mounted at /config for browser profiles, settings, and user files.
• Shared Memory: Recommended 1 GiB allocation for stable browser operation.
• Networking: Railway-generated HTTPS domain forwarding traffic to container port 3000.

No PostgreSQL, Redis, or external database services are required.

Implementation Details

Docker Configuration

Environment Variables

RAILWAY_RUN_UID=0
RAILWAY_SHM_SIZE_BYTES=1073741824

PUID=1000
PGID=1000
TZ=Asia/Jakarta

PORT=3000
CUSTOM_PORT=3000

CUSTOM_USER=admin
PASSWORD=${{secret(32)}}

HARDEN_DESKTOP=true
SELKIES_ENABLE_SHARING=false

Environment Configuration Explained

The shared memory configuration does not limit the total RAM available to Google Chrome. Actual resource consumption depends on open tabs, extensions, and browser activity.

Persistent Storage

Mount a Railway persistent volume at:

/config

This directory stores Google Chrome profiles, browser settings, bookmarks, extensions, and user files.

Data remains available across container restarts and redeployments as long as the persistent volume is retained.

Accessing Google Chrome

1. Deploy the template to your Railway project.
2. Open the generated HTTPS domain.
3. Enter the configured CUSTOM_USER and PASSWORD credentials.
4. Access the Google Chrome desktop through the Selkies interface.
5. Start browsing and customize your persistent cloud environment.

Security Considerations

This template includes configurable login credentials and optional desktop hardening settings.

However, the LinuxServer.io desktop interface is not designed to rely solely on HTTP Basic Authentication for internet-facing deployments. An additional authentication gateway or trusted-network restriction is strongly recommended.

A remotely hosted Chrome browser does not automatically provide anonymity, malware protection, or complete isolation from security threats.

Avoid using sensitive credentials or accessing confidential systems without appropriate access controls.

Resource Recommendations

• Memory: Start with 2 GB and increase based on browser workload.
• Shared Memory: 1 GiB recommended.
• CPU: Start with 1–2 vCPUs.
• Storage: Allocate sufficient persistent storage for browser profiles, extensions, and downloads.
• GPU: Optional; standard browsing can operate using CPU rendering.

Why Use Google Chrome?

Google Chrome vs Alternatives

Google Chrome is suitable for users who prioritize compatibility with Google's browser ecosystem, widely adopted web standards, and Chrome-specific application testing.

Brave emphasizes built-in privacy features, Firefox provides the independent Gecko rendering engine, Microsoft Edge offers Microsoft's browser experience, and Chromium provides an open-source alternative.

Why Deploy Google Chrome on Railway?

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 Google Chrome 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.