AtlasOps documentation.

Set up authentication, database migrations, email delivery, deployments, monitoring, webhooks, API access, billing flows, and production domain settings.

AtlasOps operations dashboard in a modern cloud operations room

Production environment

Set these values before running AtlasOps behind your domain.

DATABASE_URL="mysql://atlasops:strong-password@127.0.0.1:3307/atlasops"
AUTH_SECRET="$(openssl rand -base64 32)"
NEXTAUTH_URL="https://aelshi-nui.in"
APP_BASE_URL="https://aelshi-nui.in"
RESEND_API_KEY="re_xxxxxxxxx"
EMAIL_FROM="AtlasOps <onboarding@aelshi-nui.in>"
RAZORPAY_KEY_ID="rzp_live_..."
RAZORPAY_KEY_SECRET="..."
RAZORPAY_WEBHOOK_SECRET="whsec_..."

Local setup

The repository includes Docker, Prisma, seed data, and a public-bind dev runner.

Run docker compose up -d mysql to start the local MySQL service.
Run npm run db:generate after schema changes to refresh the Prisma client.
Run npm run db:migrate -- --name your_change to create and apply migrations.
Run npm run db:seed to create the local workspace and seeded admin account.
Run npm run dev:auto to choose a free public-bound development port automatically.

Resend email setup

AtlasOps sends verification and reset emails through a Resend-ready provider abstraction.

Create or sign in to a Resend account.
Add and verify the sending domain, for example aelshi-nui.in.
Add the DNS records Resend shows for SPF, DKIM, and domain verification.
Create an API key with sending permission.
Set RESEND_API_KEY and EMAIL_FROM in .env.
Restart the dev or production server so the email provider reads the new environment.

RESEND_API_KEY="re_..."
EMAIL_FROM="AtlasOps <onboarding@aelshi-nui.in>"

# quick smoke test
npm run dev:auto
# register a new account and check the verification email

Razorpay live payment setup

AtlasOps generates Razorpay payment links after the customer enters billing details.

Create live Razorpay API keys in the Razorpay dashboard.
Set RAZORPAY_KEY_ID and RAZORPAY_KEY_SECRET in .env.
Customers choose a plan, enter billing details on /payments, and AtlasOps creates a fresh hosted Razorpay payment link.
Create a Razorpay webhook pointing to https://aelshi-nui.in/api/razorpay/webhook.
Subscribe the webhook to payment.captured, payment.failed, payment_link.paid, and payment_link.cancelled events.
Set RAZORPAY_WEBHOOK_SECRET to the exact webhook secret from Razorpay.
Restart the production server after changing .env so billing reads the live values.

RAZORPAY_KEY_ID="rzp_live_..."
RAZORPAY_KEY_SECRET="..."
RAZORPAY_WEBHOOK_SECRET="whsec_..."

Operational modules

The app data model and pages are organized around the workflows a DevOps team repeats every day.

Projects connect repositories, environments, deployments, domains, variables, secrets, and webhooks.
Deployments preserve status, version, commit metadata, rollback targets, and deployment logs.
Servers track region, OS, CPU, memory, storage, tags, health, restart and shutdown workflows.
Monitoring snapshots capture CPU, RAM, disk, bandwidth, latency, response time, and alert context.
Billing records preserve subscriptions, invoices, payments, Razorpay IDs, hosted invoice URLs, and webhook payloads.

REST API

Use scoped API keys to list projects and build integrations.

Open

CLI

Use command-line workflows for deployment and server operations.

Open

Security

Review authentication, session, validation, and webhook security controls.

Open

Production environment

Set these values before running AtlasOps behind your domain.

DATABASE_URL="mysql://atlasops:strong-password@127.0.0.1:3307/atlasops"
AUTH_SECRET="$(openssl rand -base64 32)"
NEXTAUTH_URL="https://aelshi-nui.in"
APP_BASE_URL="https://aelshi-nui.in"
RESEND_API_KEY="re_xxxxxxxxx"
EMAIL_FROM="AtlasOps <onboarding@aelshi-nui.in>"
RAZORPAY_KEY_ID="rzp_live_..."
RAZORPAY_KEY_SECRET="..."
RAZORPAY_WEBHOOK_SECRET="whsec_..."

Local setup

The repository includes Docker, Prisma, seed data, and a public-bind dev runner.

Run docker compose up -d mysql to start the local MySQL service.
Run npm run db:generate after schema changes to refresh the Prisma client.
Run npm run db:migrate -- --name your_change to create and apply migrations.
Run npm run db:seed to create the local workspace and seeded admin account.
Run npm run dev:auto to choose a free public-bound development port automatically.

Resend email setup

AtlasOps sends verification and reset emails through a Resend-ready provider abstraction.

Create or sign in to a Resend account.
Add and verify the sending domain, for example aelshi-nui.in.
Add the DNS records Resend shows for SPF, DKIM, and domain verification.
Create an API key with sending permission.
Set RESEND_API_KEY and EMAIL_FROM in .env.
Restart the dev or production server so the email provider reads the new environment.

RESEND_API_KEY="re_..."
EMAIL_FROM="AtlasOps <onboarding@aelshi-nui.in>"

# quick smoke test
npm run dev:auto
# register a new account and check the verification email

Razorpay live payment setup

AtlasOps generates Razorpay payment links after the customer enters billing details.

Create live Razorpay API keys in the Razorpay dashboard.
Set RAZORPAY_KEY_ID and RAZORPAY_KEY_SECRET in .env.
Customers choose a plan, enter billing details on /payments, and AtlasOps creates a fresh hosted Razorpay payment link.
Create a Razorpay webhook pointing to https://aelshi-nui.in/api/razorpay/webhook.
Subscribe the webhook to payment.captured, payment.failed, payment_link.paid, and payment_link.cancelled events.
Set RAZORPAY_WEBHOOK_SECRET to the exact webhook secret from Razorpay.
Restart the production server after changing .env so billing reads the live values.

RAZORPAY_KEY_ID="rzp_live_..."
RAZORPAY_KEY_SECRET="..."
RAZORPAY_WEBHOOK_SECRET="whsec_..."

Operational modules

The app data model and pages are organized around the workflows a DevOps team repeats every day.

Projects connect repositories, environments, deployments, domains, variables, secrets, and webhooks.
Deployments preserve status, version, commit metadata, rollback targets, and deployment logs.
Servers track region, OS, CPU, memory, storage, tags, health, restart and shutdown workflows.
Monitoring snapshots capture CPU, RAM, disk, bandwidth, latency, response time, and alert context.
Billing records preserve subscriptions, invoices, payments, Razorpay IDs, hosted invoice URLs, and webhook payloads.