Deployment Guide
Transition from local development to a production-grade deployment on your own infrastructure.
Development (Local)
Run directly on your laptop using npm scripts. Ideal for building and testing workflows.
Production (VM/VPS)
Deploy to a dedicated server or VPS (AWS, DigitalOcean, etc.) using PM2 or Docker.
Production Deployment (PM2)
For a robust production setup on a single server, we recommend using PM2 to manage your processes.
module.exports = {
apps: [
{
name: "agent-api",
script: "./dist/server.js",
env: { NODE_ENV: "production" }
},
{
name: "agent-worker",
script: "./dist/worker.js",
instances: "max",
env: { NODE_ENV: "production" }
}
]
};Deployment Strategies
On-Premises
Deploy to your own bare-metal hardware for maximum data control and performance.
Cloud VPC
Deploy to a private cloud network with restricted external access for high-security workflows.
Hybrid
Keep the execution engine local but interact with cloud-based LLM providers via encrypted tunnels.
Network Configuration
If you plan to access the dashboard remotely, ensure you set up an Nginx reverse proxy with SSL (Let's Encrypt). We recommend keeping the API server behind a firewall and only exposing the necessary ports. If using local LLMs, ensure the worker instances have high-bandwidth network access to your model server.