Deployment Status

Monitor your deployment across multiple servers and regions

Pre-Deployment Checks

GitHub Connection

Checking...

Environment Variables

Checking...

Database Connection

Checking...

WebSocket Server

Checking...

API Health

Checking...

SSL Certificate

Checking...

Deployment Overview

1

Instance Running

ℹī¸ Deploy to more regions

100%

Uptime

Last 24h

12

Connected Devices

0

Errors (7d)

Deployment Checklist

1

Setup Railway Account

Open

Create a free Railway account at railway.app

2

Connect GitHub Repository

Link cyberalphatech/v0-websocket-iot-protocol to Railway

railway link
3

Set Environment Variables

Add Supabase credentials to Railway dashboard

NEXT_PUBLIC_SUPABASE_URL=your-supabase-url
SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
NODE_ENV=production
4

Deploy to Production

Push to main branch - Railway auto-deploys

git push origin main
5

Configure Domain

Point iot-access.com to Railway deployment

6

Setup SSL Certificate

Railway provides free SSL via Let's Encrypt

7

Test Deployment

Use API Tester page to verify production URL

8

Enable Multi-Region (Optional)

Deploy to US East, EU, and APAC regions

🌍 Multi-Region Deployment (Optional)

Deploy to multiple regions for better performance and redundancy:

US East

us.iot-access.com

Active

EU

eu.iot-access.com

Pending

APAC

asia.iot-access.com

Pending

View Full Deployment Guide →

⚠ī¸ Still on Localhost?

Your app is running locally on localhost:3000

To allow external connections (like from iot-access.com), you need to deploy to a public server:

  1. Follow the Deployment Checklist above
  2. Use Railway, Vercel, or self-hosted servers
  3. Port 3000 only works locally - production uses port 443
  4. Update API URLs in your IoT devices after deployment