---
title: "Deploy MASTERXTEST"
description: "UNDERSTAND YOUR DEVICE BTR"
category: "Automation"
url: https://railway.com/deploy/masterxtest
---

# Deploy MASTERXTEST

UNDERSTAND YOUR DEVICE BTR

**[Deploy MASTERXTEST on Railway](https://railway.com/template/masterxtest)**

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

- **Creator:** NANES
- **Category:** Automation
- **Total deploys:** 71

## Template content

### deduce

- **Source:** nenennenehssjbs-blip/deduce

## Documentation

# Deploy and Host high-vast on Railway

high-vast is a single-file Node.js benchmark that runs a known, controlled CPU and RAM load and logs its own resource usage over time. Instead of guessing how fast a trial's credit balance drains, you get real numbers: point it at your Railway trial and see exactly how many $/hour a given load costs — then use that rate to plan what your actual project will need.

## About Hosting high-vast

Deploying high-vast is a one-click affair — Railway auto-detects Node via `package.json` and runs `npm start`. No database or external services required. Once live, it runs continuously, holding a fixed amount of memory and CPU load and printing periodic JSON stats to the deploy logs. You can hit the `/stats` endpoint anytime for live numbers, and cross-reference against Railway's own Usage tab to calculate your actual $/hour burn rate. Defaults are tuned for the free trial tier (1 vCPU / 0.5GB RAM), but every load parameter is adjustable through environment variables — no redeploy needed.

## Why Deploy high-vast

Trial credits are billed by resource-hours, not by "did it survive" — pegging everything to 100% just gets the process OOM-killed and tells you nothing useful. high-vast runs a measured, known load instead, so the $/hour figure you get back is actually usable for planning. It's the fastest way to answer "how long will my trial credit actually last" with real data instead of a guess.

## Common Use Cases

- Measuring exactly how fast a Railway trial's credit balance drains under a known load, before committing real budget
- Comparing $/hour cost at different RAM/CPU levels to right-size a real project's resource plan
- Stress-testing a trial or low-tier plan's stability under sustained (but controlled) load

## Dependencies for high-vast Hosting

- Node.js 18+ (Railway auto-detects via `package.json`)
- No database, API keys, or external services required
- Optional env vars: `RAM_TARGET_MB` (default 420), `CPU_LOAD_PCT` (default 95), `LOG_INTERVAL_MS` (default 60000)

## Similar templates

- [N8N Main + Worker](https://railway.com/deploy/n8n-main-worker) — Deploy and Host N8N with Inactive worker.
- [Evolution API with n8n](https://railway.com/deploy/evolution-api-with-n8n) — Automate WhatsApp workflows with Evolution API, n8n, and Postgres.
- [Postgres Backup](https://railway.com/deploy/postgres-s3-backups) — Cron-based PostgreSQL backup to bucket storage

Open this page in a browser: https://railway.com/deploy/masterxtest