Deployment Guide

On-premise, hosted, and hybrid deployment options for Pharos.

Deployment Options

Pharos supports three deployment models:

| Model | Data Location | Pharos Location | Best For | |-------|--------------|-----------------|----------| | On-premise | Your servers | Your servers | Maximum control, strict compliance | | Hosted | Your servers | Phygital cloud | Minimal IT overhead | | Hybrid | Your servers | Both | Phased migration |

In all models, your data stays on your infrastructure. Pharos reads from your databases. It does not replicate or store your data.

On-Premise Deployment

System Requirements

• OS: Linux (Ubuntu 22.04+, RHEL 8+) or Windows Server 2019+
• Runtime: Node.js 20+ or Docker
• Memory: 512 MB minimum, 1 GB recommended
• Network: Access to SYSPRO/Tempo databases (TCP port 1433 for SQL Server)

Installation

# Docker (recommended)
docker pull phygital/pharos:latest
docker run -d \
  --name pharos \
  -p 8080:8080 \
  -e SYSPRO_HOST=your-db-server \
  -e SYSPRO_DB=your-company-db \
  -e PHAROS_SECRET=your-secret-key \
  phygital/pharos:latest

Network Configuration

Pharos needs outbound access to:

• Your SYSPRO SQL Server (port 1433)
• Your Tempo MRP database (if applicable)
• Your analytics warehouse (if applicable)

Inbound access required:

• Port 8080 (or your configured port) from AI clients

For Claude Desktop on user workstations, ensure they can reach the Pharos instance over your network.

Hosted Deployment

With hosted deployment, Phygital runs Pharos on our infrastructure. You provide:

1. A secure tunnel (WireGuard or SSH) to your database servers
2. Read-only database credentials
3. Write credentials (optional, for read-write operations)

We handle updates, monitoring, and scaling. Your data never leaves your network. The tunnel is point-to-point, and Pharos queries are executed in real-time.

Hybrid Deployment

Start with hosted, migrate to on-premise when ready. Or run both:

• Hosted instance for external/cloud AI clients
• On-premise instance for internal/factory-floor access

Both instances use the same configuration and token system.

Configuration

Pharos is configured via environment variables:

| Variable | Required | Description | |----------|----------|-------------| | SYSPRO_HOST | Yes | SQL Server hostname | | SYSPRO_DB | Yes | Company database name | | SYSPRO_USER | Yes | Database username | | SYSPRO_PASS | Yes | Database password | | TEMPO_HOST | No | Tempo MRP database host | | PHAROS_SECRET | Yes | Secret key for token signing | | PHAROS_PORT | No | HTTP port (default: 8080) | | LOG_LEVEL | No | debug, info, warn, error |

Health Check

Verify your deployment is running:

curl -s https://your-pharos-instance/health

Expected response:

{
  "status": "healthy",
  "version": "1.4.2",
  "databases": {
    "syspro": "connected",
    "tempo": "connected",
    "analytics": "connected"
  }
}

Support

For deployment assistance, contact [email protected] or book a call.