Pain point 1
Same environment rebuilt over and over
Runnable infrastructure
Run infrastructure like a function.
Define the workflow once. Hit launch or call the API. Spinly gives you a working environment, then cleans it up when the job is done.
Package the cloud resources, setup scripts, access endpoints, checks, and runbook into one reusable launch path.
Define once
Launch on demand
Use immediately
Auto-cleanup
Spinly is not a provisioning dashboard.
Stop provisioning.
Stop configuring.
Run.
Define a workflow once.
Attach scripts, dependencies, access, and runbooks.
Launch it from the UI or API.
Get a working environment.
Let it self-destruct when done.
Example workflow
Customer demo environment
Environment ready
Infrastructure
Cloud environment
Choose the resources, network, access, and cleanup window.
Setup
Setup logic
Run the scripts, installers, agents, and checks the same way every time.
Guide
Use it
Surface access links, readiness, notes, logs, and the runbook when the environment is ready.
Workflow built
Reusable launch workflow
Ready to run
Automation
6 setup steps
Runbook
12 guided tasks
Live environment
Working environment
Ready in7 minutes
AccessLinks available
ChecksPassed
Runbook attached
Auto-cleanup in 8h
Built for
Teams that need real environments on demand without rebuilding them by hand.
Solutions engineers
Infrastructure software vendors
Developer relations teams
Platform teams
Technical sales and demo teams
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
Spinner 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
Most ephemeral environments are still built the hard way
Teams still use cloud consoles, Terraform, scripts, docs, Slack messages, and tribal knowledge just to get a temporary environment running.
Pain point 2
Scripts, notes, and access details scattered everywhere
Pain point 3
Runbooks live in people's heads
Pain point 4
Temporary environments get forgotten
Pain point 5
Agents can plan, but they cannot safely run infra
How Spinly works
Define once. Run whenever.
Spinly turns the pieces of an environment into one runnable workflow.
01
Template
Defines the cloud resources.
02
Spinner
Runs setup logic, scripts, and installers.
03
Runbook
Adds instructions, checks, and operator guidance.
04
Launchpack
Bundles everything into something runnable.
05
Environment
Returns the working environment with status, access, and logs.
06
TTL cleanup
Retires the environment automatically when its window is over.
Use cases
When you need a real environment now.
Use Spinly when the job needs an actual cloud environment, not another ticket, script, or wiki page.
Use case
Customer demos
Launch demo environments that are ready to use, easy to access, and safe to retire.
Use case
Internal labs
Run repeatable labs without rebuilding setup, access, and instructions every session.
Use case
QA and validation
Create short-lived validation environments with the same setup path every run.
Use case
Agent-driven operations
Give agents a safe API for launching approved infrastructure workflows.
Guardrails
Ephemeral by default. Guarded by policy.
Spinly makes temporary infrastructure safer by giving every launch limits, lifecycle, and cleanup.
Control
TTL enforcement
Control
Cleanup automation
Control
Launch guardrails
Control
Repeatable execution paths
Control
Auditability
Control
Fewer forgotten resources
Developers and agents
Built for humans and agents
Humans can click launch. Agents can call the API. Both use the same approved workflow.
Run the same workflow over API
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"
}Start with one workflow
Stop rebuilding ephemeral environments by hand
Define the workflow once. Run it when you need it. Get a working environment, then let Spinly clean it up.