Builds Explained

ATStatus comes in three distinct builds, each serving a different purpose. Understanding when to use each build is essential for proper deployment.

Important

For production deployment, always use the Clean Build. The Demo and Production builds are for development and testing only.

Build Comparison

Aspect	Clean Build	Demo Build	Production Build
Purpose	Your deployment	Testing & evaluation	Developer reference
Database	Empty (fresh start)	Sample data included	Live development data
Configuration	Default settings	Pre-configured	Full configuration
Users	Setup creates admin	Demo admin included	Development accounts
Support	✅ Fully supported	⚠️ Testing only	❌ Not for distribution
Updates	✅ Safe to update	⚠️ May lose data	❌ Internal only

Clean Build (statuspage-clean)

Recommended for Production

This is the build you should use for all deployments. It provides a clean slate with no pre-existing data, allowing you to configure everything from scratch.

When to Use

✅ Deploying to your own server
✅ Setting up for a client
✅ Any production environment
✅ Starting fresh with no sample data

What You Get

Empty database — No sample incidents, components, or users
Setup wizard — Creates your first admin account
Default configuration — Sensible defaults, customize as needed
All features enabled — Full feature set available
Documentation support — All docs reference this build

Installation

# 1. Navigate to the clean build
cd statuspage-clean

# 2. Install dependencies
npm install

# 3. Run setup (creates database + admin account)
npm run setup

# 4. Start the application
npm start

Demo Build (statuspage-demo)

For Testing & Evaluation

Pre-configured with sample data to explore features without setup. Use this to evaluate ATStatus before committing to a deployment.

When to Use

✅ Evaluating ATStatus features
✅ Testing before production deployment
✅ Showing demos to stakeholders
✅ Learning the admin panel

What You Get

Sample components — Pre-created services to monitor
Sample incidents — Example incidents with updates
Demo admin account — Ready to login immediately
Pre-configured settings — Branding, features already set

Not for Production

The Demo build contains sample data and test credentials. Do not deploy this to a production environment.

Production Build (statuspage-production)

Developer Reference Only

This is the internal development build. It may contain experimental features, development credentials, and is not intended for distribution.

When to Use

❌ Never for your deployments
⚠️ Only for ATStatus developers
⚠️ Reference for feature implementation

Why It Exists

The production build is the active development environment where new features are tested before being merged into the clean build. It contains:

Live development data
Experimental features in testing
Development-specific configurations
May have incomplete or unstable features

How to Choose

Deploying?

Use Clean Build

Evaluating?

Use Demo Build

Contributing?

Fork Clean Build

Best Practice

Start with the Demo Build to explore features, then when ready to deploy, use the Clean Build and configure it to match your needs.

Migrating Between Builds

From Demo to Clean (Recommended)

When you're ready to go live after testing with the Demo build:

Install the Clean Build fresh
Run npm run setup
Recreate your components and settings manually
Configure notifications and integrations

No Data Migration

The Demo build's sample data is not meant to be migrated. Start fresh with the Clean Build and create your actual production configuration.

Next Steps

Quick Start

Install the Clean Build

Core Concepts

Terminology and concepts