Requests

The primary way to make infrastructure changes through Opsitron.

A Request is how you tell Opsitron what you need. It’s the starting point for every infrastructure change — from deploying a new application to updating a DNS record.

How Requests Work

When you submit a request, it flows through a structured lifecycle:

  1. Submitted — You describe what you need, either in plain English or by selecting a template
  2. Planning — AI analyzes your request, examines your existing infrastructure, and generates a detailed plan
  3. Plan Review — An engineer reviews the AI’s plan for correctness, security, and cost implications
  4. In Progress — The approved plan is implemented as code (Terraform/OpenTofu) and submitted as a pull request
  5. Deployment — Changes flow through your environments: dev → staging → production

Each step is visible in the Opsitron portal. You can track progress, view the plan, see the pull request, and approve deployments.

Request Types

Opsitron includes pre-built templates for common operations:

TemplateWhat It Does
Module DeployDeploy infrastructure for an application environment (ECS, static site, etc.)
Infrastructure RequestGeneral-purpose request described in plain English
DNS ZoneProvision a Route53 hosted zone for a domain
Setup Shared ServicesCreate ECR repositories and artifact buckets

Some templates are deterministic — they follow a fixed pattern and can be auto-approved, making routine operations instant.

What Happens Behind the Scenes

Every request creates a complete audit trail:

  • Plan — The AI’s analysis and proposed changes, stored as structured JSON
  • Tasks — AI execution records with full transcripts
  • Pull Request — The actual code changes in your GitHub repository
  • Deployments — Terraform plan/apply results with blast radius and cost estimates
  • Events — Timeline of every state change and action

You own all the code. The pull request lands in your GitHub organization’s config repository, where your team can review it like any other PR.

Autonomy Rules

For routine operations (DNS provisioning, ECR setup), Opsitron can auto-approve plans based on configurable rules. This means simple requests complete end-to-end without human intervention, while complex changes always require review.