Docs
Powered by

# StationOps Architect Guide

Architect is the AI-assisted infrastructure workspace in StationOps. It combines a chat assistant, an editable architecture diagram, environment views, cost context, repository import, AWS connection, draft saving, and deployment controls in one place.

# Open Architect

  1. Open the StationOps dashboard.
  2. Choose the organisation and project you want to work on.
  3. Go to Architect in the project navigation.

  4. StationOps creates or opens an Architect chat for the project.

    You can also reach Architect from setup and troubleshooting paths, including deployment failures, logs, metrics, and infrastructure activity. When Architect opens from one of those contexts, it may preload a hidden system prompt or a visible message with the relevant project details.

# Understand the Workspace

Architect has two main areas:

  1. The architecture diagram, where you review infrastructure components and switch environments.
  2. The chat panel, where you ask for changes, reviews, explanations, and deployment guidance.

When a project already has infrastructure, Architect opens with the current environment diagram, component count, estimated monthly cost, suggested next moves, and readiness items.

Architect Workspace
Architect Workspace

For new or onboarding projects, Architect also shows readiness items such as:

  • Project created
  • Draft infrastructure created
  • Git repo connected or skipped
  • AWS account connected
  • Configuration reviewed
  • Ready to deploy

# Draft an Architecture

  1. In the chat panel, describe the system you want to run.
  2. Use a suggested next move if it fits your goal.
  3. Attach project spec files when you want Architect to use existing written requirements.
  4. Press Enter or click the send button.

  5. Wait while Architect is thinking and creating a response.

    Architect Prompt

Example prompts:

  • Draft a minimal production-minded web app with a frontend, backend, database, SSL, and dev/prod environments.
  • Import my repository before drafting infrastructure.
  • Review this architecture for reliability, security, cost, and operational simplicity.
  • Simplify this draft to the smallest deployable version.

Tip: Architect works best when you describe the application shape, repositories, environments, data stores, public/internal services, and deployment goals.

# Apply or Refine Changes

Architect responses can include proposed infrastructure configuration changes. Review the response, then use the action buttons below the message when they appear.

  1. Click an action such as Apply, Generate configuration, or another suggested action when it matches your intent.
  2. Review the diagram after the change is applied.
  3. Ask a follow-up question or request another change.

Select text in an Architect response and click Reply to quote that text in your next message.

Use the code toggle to inspect or edit the underlying configuration JSON. Save the JSON edit to apply it back to the draft.

When Architect changes the draft, use Changes to see what components were added, removed, or updated.

# Edit the Diagram Manually

Architect is not chat-only. You can edit the draft directly from the diagram.

  1. Turn on Edit mode.
  2. Select a component to edit its settings.
  3. Click Add Component to add services, databases, storage, queues, caches, event streams, key-value stores, or Bedrock agents.
  4. Use the environment pills to review each environment.

  5. Save the component changes.

    Note: Manual edits and AI changes work on the same draft. You can ask Architect to explain, review, or revise changes after editing.

# Import a Repository

Architect can start from repository detection instead of a blank prompt.

  1. In Architect, open the connection or add menu.
  2. Choose Connect GitHub repo or Connect GitLab repo.
  3. Authorize the repository connection.
  4. Select the repository and branch to inspect.

  5. Let Architect detect services and create a deployable starting configuration.

    Repository Readiness

    Note: If you started onboarding with Import repository, Architect waits for the repository connection before drafting infrastructure.

# Connect AWS

Architect needs an AWS project configuration before it can deploy.

  1. Click Deploy to environment from Architect, or open Settings > AWS.
  2. If the project does not have an AWS configuration yet, click Create.
  3. In the AWS configuration flow, choose an existing AWS connection and region.
  4. If needed, create a new AWS connection and authorize the StationOps CloudFormation stack in AWS.

  5. Return to StationOps and save the project AWS configuration.

    AWS Settings

    Create Stack

    Important: The AWS account must allow StationOps to create the infrastructure resources in your draft.

# Connect Domains

  1. Open Connect.
  2. Click Connect domains.
  3. Configure the domain for the active environment.
  4. Save the domain settings.

Architect can then account for domain and routing requirements while reviewing or updating the infrastructure.

# Save a Draft

Use drafts when the architecture is not ready to deploy yet.

  1. Click Save Draft.
  2. Enter a configuration name.
  3. Click Save Draft .

  4. StationOps opens the saved infrastructure configuration.

    Tip: Saving a draft is useful before making larger AI or manual changes.

# Deploy from Architect

  1. Select the environment you want to deploy with the environment pills.
  2. Click Deploy to environment.
  3. Enter or confirm the configuration name.
  4. If StationOps asks for root account emails, provide the required account email addresses or use Quick Add +.
  5. Click Confirm .

  6. StationOps creates the infrastructure configuration and launches the infrastructure deployment.

    Architect Deploy Context

    Note: If no AWS connection exists, Architect opens AWS configuration before showing the deployment confirmation.

# Use Activity and Live Context

The Architect workspace can also show project activity and deployed infrastructure context.

  1. Open the Activity panel to see recent project events.
  2. Select an activity item to inspect details.
  3. Ask Architect to explain failures, logs, metrics, or deployment changes.
  4. Switch back to the Architect panel to ask for a fix or configuration update.

This is the same workflow used when Architect opens from logs, metrics, service deploy failures, or infrastructure revision screens.

# Tips for Better Results

  • Be specific about the application shape, traffic path, and deployment environments.
  • Attach concise project specification files for requirements-heavy projects.
  • Ask Architect to review cost, security, reliability, and operational simplicity before deploying.
  • Keep the first draft small, then add components as the project needs them.
  • Use Save Draft before risky or broad changes.

Architect can draft the first topology, help import repositories, explain configuration tradeoffs, apply infrastructure changes, and launch the first deployment from the same workspace.

© Copyright 2026. All rights reserved.