Terms of service.

Use AtlasOps responsibly for infrastructure, deployment, monitoring, billing, and team operations you are authorized to manage.

Authorized use

AtlasOps is built for legitimate deployment and infrastructure operations.

You must only connect repositories, servers, domains, generated payment links, and infrastructure accounts that you are authorized to manage.
You are responsible for maintaining secure passwords, API keys, SSH keys, webhook secrets, and organization member access.
You must validate deployment, rollback, restart, shutdown, and billing changes before applying them to production systems.
You may not use AtlasOps to disrupt third-party systems, probe infrastructure without permission, or store illegal content.

AtlasOps provides the software controls; customers retain operational ownership.

Customers own the correctness of deployment configuration, server access, environment variables, and billing links.
AtlasOps records audit and activity history to support accountability but cannot guarantee that every external system will accept a requested action.
Customers should maintain separate backups, recovery procedures, and incident response plans for production workloads.
Integrations with email, billing, DNS, infrastructure, and repositories depend on the availability and configuration of those providers.

Billing pages and webhook records are designed for transparent review.

Paid plans may be started through Razorpay payment links generated from submitted billing details.
Payment, invoice, and subscription states are recorded when payment links or webhooks return data to AtlasOps.
Plan limits and access may change when subscriptions are upgraded, canceled, overdue, or manually adjusted.
Refunds and billing disputes are handled under the refund policy and payment-provider rules.

Authorized use

AtlasOps is built for legitimate deployment and infrastructure operations.

You must only connect repositories, servers, domains, generated payment links, and infrastructure accounts that you are authorized to manage.
You are responsible for maintaining secure passwords, API keys, SSH keys, webhook secrets, and organization member access.
You must validate deployment, rollback, restart, shutdown, and billing changes before applying them to production systems.
You may not use AtlasOps to disrupt third-party systems, probe infrastructure without permission, or store illegal content.

Service responsibilities

AtlasOps provides the software controls; customers retain operational ownership.

Customers own the correctness of deployment configuration, server access, environment variables, and billing links.
AtlasOps records audit and activity history to support accountability but cannot guarantee that every external system will accept a requested action.
Customers should maintain separate backups, recovery procedures, and incident response plans for production workloads.
Integrations with email, billing, DNS, infrastructure, and repositories depend on the availability and configuration of those providers.

Plans and billing

Billing pages and webhook records are designed for transparent review.

Paid plans may be started through Razorpay payment links generated from submitted billing details.
Payment, invoice, and subscription states are recorded when payment links or webhooks return data to AtlasOps.
Plan limits and access may change when subscriptions are upgraded, canceled, overdue, or manually adjusted.
Refunds and billing disputes are handled under the refund policy and payment-provider rules.