StationOps Documentation

Build, deploy, and operate applications and AWS infrastructure with StationOps.

StationOps brings application delivery and AWS infrastructure into one workflow. Define environments and components in Architect, build versioned service packages from Git, deploy them through controlled releases, and operate the resulting resources from the project dashboard.

Start Here

Create your project structure and add lifecycle environments such as development, staging, and production.
Connect an AWS account and choose the deployment region.
Connect GitHub or GitLab for private source repositories.
Create an infrastructure configuration in Architect.
Configure services and components, then review and deploy the infrastructure revision.
Build and deploy service releases.

Use Architect for the Fastest Start

StationOps Architect can draft an infrastructure configuration from a plain-language description. Always review the generated services, permissions, removal policies, and environment settings before deployment.

What You Can Configure

Application targets on ECS Fargate, EC2, Lambda, CloudFront, CodeBuild, and managed mobile builders.
PostgreSQL, MySQL, and MariaDB databases.
SQS queues, S3 storage, EFS volumes, DynamoDB tables, Redis OSS, Memcached, and Kafka event streams.
Environment variables, component permissions, metrics, alarms, logging destinations, domains, and AWS WAF rules.
Multi-service build and deploy plans, preview environments, uptime monitoring, and rollback workflows.

Find the Right Guide

Goal	Documentation
Create project resources	Create
Configure infrastructure	Configure
Build and release applications	Deploy
Operate deployed resources	Manage
Follow a framework recipe	Frameworks
Control team access	Access
Diagnose a failure	Troubleshooting
Find any product area	Feature Guide Map

Deployment Model

StationOps separates the infrastructure definition from application artifacts:

An infrastructure configuration describes services and AWS components for every project environment.
A successful infrastructure deployment creates a revision and makes the configured runtime available.
A package is a built application artifact associated with a source revision.
A release selects a package for controlled deployment to an environment.

This separation lets teams change infrastructure independently from application releases while keeping both histories visible.

For definitions and a complete product-to-guide index, see the Platform Reference.