Runnable infrastructure for demo teams

Run infrastructure like a function.

Define a workflow once. Launch it from the UI or API and get a working, ready-to-use environment — running in your own AWS account. Spinly orchestrates, tracks, and cleans it up when the job is done.

Request early access See how it works

Runs in your AWS account

One-click CloudFormation onboarding

Auto-cleanup, every time

Customer demo / ceph-cluster

Environment ready

Healthy

Access

3 endpoints

console.demo.spinly.run

ssh ec2-user@10.24.8.12

runbook / operator-readiness

Environment

AWS account: •••• 4821
Region: us-east-1
Ready in: 07m 18s

Lifecycle

Auto-cleanup in 8h

Launch approved

09:42:03

Cluster checks passed

09:49:18

Runbook attached

09:49:20

Runs in your cloud

Your AWS account. Our orchestration.

Spinly never hosts your workloads. Connect your AWS account in three steps — pick a tier, deploy a CloudFormation role (the same pattern you know from Datadog), verify — and Spinly assumes a scoped, auditable cross-account role to launch and retire environments on your behalf. Connections are shared at the workspace level; teammates launch without ever seeing credentials.

Your compute spend stays on your AWS bill at your negotiated rates. Your data never leaves your account. Every action Spinly takes is visible in your CloudTrail.

Scoped by design

Each launchpack runs under its own permission boundary. Spinly can only do what the workflow declares.

Fully auditable

Every create, modify, and destroy lands in your CloudTrail. No black box.

Budgets per teammate

Give each member a credit budget and launch quota. Spend caps are enforced before launch, not discovered on the bill.

AWS today

Built AWS-first. Tell us if your demos live elsewhere: request early access.

Spinly control plane

Coordinate the workflow

scheduler · TTL · orchestrator · logs

Cross-account IAM role

Scoped · auditable · revocable

Your AWS account

Run the environment

VPCs · EC2 · EKS · your demo environment

TTL enforcement

Per-member spend caps

Auditability

Automatic cleanup

Built for

Built for teams that demo real infrastructure.

Turn the environment behind the demo into a repeatable, runnable launchpack.

Primary workflow

Solutions engineers at infra vendors

Launch a customer-ready cluster demo in minutes, drive it from a presenter-mode runbook, and let cleanup happen automatically. No more rebuilding the same environment before every call.

Agent API

AI agents

Give agents a safe API for launching approved infrastructure workflows — guardrails, TTLs, and audit included.

Also used for internal labs, QA validation, and platform self-service.

For solutions engineers

From launch to closed deal.

Spinly keeps the live demo workflow and the sales outcome attached to the same environment history.

Guided runbooks

Keep the room with you.

Every launchpack carries its runbook. Open Presenter mode and drive the demo step by step — objectives, commands, and completion tracking on your screen, a clean guided view for the room. No more alt-tabbing between a wiki, a terminal, and a prayer.

Guide View

Customer demo runbook

GuidePresenter

1 / 4 steps completed

Guided workflow attached to this launchpack.

In progress

Step 2 of 4

Validate cluster health

In progress

Objective

Confirm the environment is ready before moving into the customer workflow.

Commands

ceph -s
kubectl get nodes

Current step: 2 / 4Next

Conversion tracking

Connect demos to outcomes.

Tag every environment with its deal outcome — in pipeline, closed won, closed lost. See which demos convert, what each win actually cost in compute, and walk into your QBR with numbers instead of anecdotes.

Analytics

Launch performance & sales signal

Workspace data hidden

Average environment cost

—

Calculated from tagged environment sessions.

Runtime vs planned TTL

—

Runtime and planned window stay linked.

Conversion snapshot

Sales impact

Mark deals as they progress to keep the funnel honest.

In pipeline—

— of projects

Closed won—

— of projects

Closed lost—

— of projects

Win rate—

Based on projects tagged in the conversion tracker.

Budget control

Workspace credits cap what each teammate can spend. SEs launch freely inside their budget; nobody explains a surprise AWS bill.

Credits are an enforced governance limit. Compute remains on your AWS bill at your rates.

Per-member capLaunch quotaChecked before launch

Product showcase

Environment launch details

3 services healthy

Launchpack

ceph-cluster-demo

Reusable workflow

Access links available

Readiness checks

Runbook attached

Lifecycle

Cleanup scheduled

Launch approved2 min ago

Script install complete6 min ago

TTL cleanup queued8h remaining

Environment output

Environment state

Ready

SSH bastion

Console URL

Operator runbook attached

Product

Every launch returns something usable.

Spinly does not stop when the cloud resources exist. It waits until the environment is usable, shows the access paths, attaches the runbook, tracks lifecycle, and cleans up automatically.

Launch the same environment without rebuilding it by hand

See status, access links, logs, and notes in one place

Know when the environment is actually ready

Launch the same workflow from the UI or API

Retire temporary infrastructure automatically

The problem

Real demos still depend on fragile setup work.

Customer-facing teams lose time rebuilding short-lived infrastructure from cloud consoles, scripts, docs, and memory.

Rebuilt by hand

The same customer environment gets assembled again before every important call.

Scattered operating context

Scripts, runbooks, access details, and readiness checks live in different places.

Forgotten resources

Temporary infrastructure outlives the demo and keeps accumulating cost and risk.

How Spinly works

Define once. Run whenever.

Spinly turns the pieces of an environment into one runnable workflow.

Template

Defines the cloud resources.

Script

Runs setup logic, scripts, and installers.

Runbook

Adds checks and operator guidance.

Launchpack

Bundles the pieces into one approved workflow.

Environment

Returns status, access paths, and logs.

TTL cleanup

Retires the environment when its window ends.

Use cases

When the job needs a real environment now.

Launch a working environment from an approved path, use it, and retire it on schedule.

Primary use case

Customer demos

Launch a customer-ready cluster with access links, readiness checks, and the exact runbook your SE needs for the call.

Team enablement

Internal labs

Run repeatable hands-on labs without rebuilding setup, access, and instructions for every session.

API workflow

Agent-driven operations

Let agents invoke approved launchpacks through a guarded API instead of giving them open-ended cloud access.

Developers and agents

One workflow. Two interfaces.

The launchpack is the contract. People use the product surface; software uses the API.

Read the API docs

Humans click launch. Agents call the API. Same approved workflow, same guardrails.

POST /planner/launch

POST /planner/launch
{
  "spec": {
    "launchpack": "ceph-cluster-demo",
    "ttl_hours": 8
  },
  "ssh_public_key": "ssh-ed25519 AAAA..."
}

GET /api/environments/{id}
{
  "status": "ready",
  "access": ["ssh", "console"],
  "runbook": "operator-readiness"
}

Early access

Get early access.

If you rebuild the same demo environment more than once a month, Spinly will pay for itself in a week. Tell us where to send your invite.

Creates a pending access request for admin approval.