SnapFlow Docs

The public landing page

SnapFlow's marketing site is what you see before signing in. The navigation bar has links to Log in and a filled Get Started button; the hero section describes the product and offers two paths: Enter the swarm (goes to sign-up) and Try the Sandbox — no login required (goes straight to the live demo, no account needed).

snapflow.online
SnapFlow marketing landing page hero section
● Live screenshot — The public marketing homepage.

Creating your account

Go to Sign up from the landing page or navigation bar. There is no plan, tier, seat count, or company-name field on this screen — signing up is a single, free-form step.

/signup
SnapFlow sign-up screen with name, email, password fields and GitHub button
● Live screenshot — The sign-up screen. Google appears alongside GitHub when the deployment has both social providers configured.

Two ways to sign up:

Validation you may see

If your passwords don’t match, SnapFlow shows "Passwords do not match." If the password is under 8 characters, it shows "Password must be at least 8 characters." A duplicate email or other server-side problem surfaces its own message, falling back to "Sign up failed."

Click Create account (it reads "Creating account…" while working). On success you're taken straight into the onboarding wizard — every new account starts there, whether you signed up by email or by a social provider.

Signing in

/login
SnapFlow sign-in screen with email, password fields and GitHub button
● Live screenshot — The sign-in screen for returning users.

Returning users sign in with email + password, or with Google/GitHub if enabled. The password field has a show/hide toggle (the eye icon). If you submit an incomplete or malformed form, SnapFlow validates client-side before it ever contacts the server:

SituationMessage shown
Email left blank"Email is required"
Email not in a valid format"Invalid email format"
Password left blank"Password is required"
Password under 8 characters"Password must be at least 8 characters"
Wrong email/password combination"Invalid credentials"
Connection problem"Network error"

On success, SnapFlow signs you in and takes you to Mission Control — or, if you followed a link that required you to sign in first (for example a shared approval or a deep link), back to that original destination.

Onboarding your workspace

Right after creating an account, SnapFlow walks you through a short, skippable setup wizard so the swarm has something to work with. A progress bar with four labels — Welcome, GitHub, Cloud, Discovery — tracks where you are. You can leave at any point with the "Skip to Dashboard →" link in the header, and every individual step also has its own skip option.

1. Welcome

/onboarding
S SnapFlow
Skip to Dashboard →
Welcome
GitHub
Cloud
Discovery
🚀
Welcome to SnapFlow
Your AI-powered DevOps command center. Let's get you set up in a few steps.
I'll connect these later →
◐ Recreated illustration — The welcome step of the onboarding wizard.

A short welcome message, a primary button "Set up your workspace" that starts the flow, and a secondary link "I'll connect these later →" that skips straight to the finish screen.

2. Connect your code (GitHub)

/onboarding
S SnapFlow
Skip to Dashboard →
Welcome
GitHub
Cloud
Discovery
Connect your code
Link your GitHub account so SnapFlow can read your repositories and Infrastructure-as-Code files.
✅ GitHub connected successfully
scalenation/snapflow-infra · 12 repositories
◐ Recreated illustration — The GitHub connection step.

Lets SnapFlow read your repositories and any Infrastructure-as-Code files in them. Click Connect GitHub (shows "Connecting..." while redirecting) to go through GitHub's install flow and back. Once linked, a green banner confirms "✅ GitHub connected successfully." The continue button reads "Next: Connect Cloud →" if you connected, or "Skip to Cloud Connection →" if you didn't — either way it moves you forward.

3. Connect your cloud

/onboarding
S SnapFlow
Skip to Dashboard →
Welcome
GitHub
Cloud
Discovery
Connect your cloud
Link your cloud provider so SnapFlow can discover infrastructure and execute changes.
☁️
Amazon Web ServicesEC2, EKS, S3, IAM, RDS, Lambda
Connected ✓
🔷
Google Cloud PlatformGKE, Cloud Run, Compute Engine
🔵
Microsoft AzureAKS, App Service, VMs
◐ Recreated illustration — The cloud provider connection step, with AWS, GCP, and Azure cards.

Three provider cards, each connectable independently — you can link none, one, two, or all three:

ProviderWhat SnapFlow can see/manage
☁️ Amazon Web ServicesEC2, EKS, S3, IAM, RDS, Lambda
🔷 Google Cloud PlatformGKE, Cloud Run, Compute Engine, Cloud Storage
🔵 Microsoft AzureAKS, App Service, VMs, Cosmos DB, Storage

Each card's Connect button redirects to that provider's connection flow and back; once linked the card shows "Connected ✓". ← Back returns to the GitHub step; the forward button reads "Next: Discover Infrastructure →" once at least one provider is connected, or "Skip to Discovery →" otherwise.

You can connect cloud providers later

Nothing here is a one-time offer — every provider you skip during onboarding can be connected any time from Infrastructure & Targets → Connections. See Infrastructure & Targets.

4. Discovery (automatic)

/onboarding
S SnapFlow
Skip to Dashboard →
Welcome
GitHub
Cloud
Discovery
Mapping your infrastructure
The Discovery Swarm is analyzing your connected accounts…
Starting infrastructure discovery...
🔍 Scanning AWS account...
✅ Found 34 resources in AWS
📂 Scanning GitHub repositories for IaC files...
✅ GitHub IaC scan complete
◐ Recreated illustration — The automatic infrastructure discovery step with its live scanning log.

Nothing to click here — SnapFlow's Discovery Swarm scans whatever you connected and prints its progress as a live-scrolling log (for example "🔍 Scanning AWS account…", "✅ Found N resources in AWS", "📂 Scanning GitHub repositories for IaC files…"). If you connected nothing, it says so and moves on immediately. This step advances automatically once scanning finishes.

5. Your workspace is ready

/onboarding
S SnapFlow
Skip to Dashboard →
Welcome
GitHub
Cloud
Discovery
Your workspace is ready
Your accounts are connected and the swarm has mapped your infrastructure.
GitHub✅ Connected
Cloud Providers✅ 1 connected
Infrastructure Discovery✅ Completed
◐ Recreated illustration — The onboarding completion summary screen.

A summary of what got connected (GitHub, cloud providers, and whether discovery ran, each marked ✅ or ⏭️ Skipped), and a final button — "Enter the Command Center →" — that drops you into Mission Control, SnapFlow's home screen.

Try the Sandbox demo (no account needed)

/sandbox
SnapFlow Sandbox demo with Paste Error Log and Public Repo URL modes
● Live screenshot — The public Sandbox — a taste of SnapFlow before you sign up.

The Sandbox is a public, zero-signup playground at /sandbox. Anyone can try it. Choose one input mode, then submit:

ModeWhat it does
📋 Paste Error LogA textarea for a build log, error trace, or pipeline output. SnapFlow diagnoses it.
🔗 Public Repo URLA single field for a public GitHub repo URL. SnapFlow produces a containerization plan for it.
  1. Pick a mode and paste your log or repo URL.
  2. Click ✨ Fix with SnapFlow (shows "⚡ Connecting..." briefly).
  3. Watch the agents work in a live-scrolling terminal-style log, each line tagged with the responsible agent’s emoji.
  4. When it finishes, a green result card shows the write-up (diagnosis or containerization plan) with an ⧉ Copy button.
  5. Click Run this on your own infrastructure → to jump to sign-up, or ← New Request to try something else.
What the Sandbox is not

It’s read-only and ephemeral: "No login required. Read-only sandbox. Results auto-delete after 1 hour." It never touches your real infrastructure — that only happens once you’ve connected an account in Infrastructure & Targets.