Pain point 1
Rebuilding the same setup over and over
The control plane for ephemeral infrastructure workflows
Build once. Launch environments on demand.
Example environment
Ollama + OpenWebUI demo
A reusable demo launched from a saved workflow.
Environment ready
Workflow overview
Source
Template1-gpu-node
LaunchpackOllama + OpenWebUI Demo
Ownerspinly-user
Status
StateReady
Ready in7 minutes
Auto cleanup8h policy
Access
Open WebUI available
Controlled access
ModePrivate access only
Endpointhttp://<node-ip>:3000
NotesVPN required
Endpoints and operator notes stay attached to each environment.
Setup history
7 completed · 0 failed · 0 pending
1
Enable NVIDIA GPU
Success
2
Prep Ubuntu GPU
Success
3
Install Ollama
Success
4
Pull Ollama model
Success
5
Start Open WebUI
Success
View full setup log
Environment details
Demo environment is ready
InstanceGPU L4 · g6.xlarge
StorageHigh performance · 200 GB
Runtime44m
Cost$0.91/hr
Cleanup8h policy
Runbook, setup history, and access stay linked to the environment.
Built for
Teams running demos, labs, validation, and technical field workflows.
Solutions engineers
Infrastructure software vendors
Developer relations teams
Platform teams
Technical sales and demo teams
The problem
Most ephemeral environments are still built the hard way
Teams still stitch together cloud instances, scripts, notes, and tribal knowledge just to run demos, labs, or tests.
Pain point 2
Scripts scattered across repos and docs
Pain point 3
Runbooks depend on tribal knowledge
Pain point 4
Temporary environments become cloud sprawl
Pain point 5
Agents have no real control plane to operate against
How Spinly works
Package the full workflow once. Launch it on demand.
The product model is simple:
01
Template
Defines the infrastructure baseline
02
Spinner
Installs and configures software
03
Runbook
Provides guided operational steps
04
Launchpack
Bundles everything into a reusable workflow
05
Environment
The running output with controls, access, and lifecycle
06
TTL cleanup
Retires temporary infrastructure automatically
Use cases
Built for real infrastructure workflows
Where Spinly fits in practice.
Use case
Customer demos
Give field and sales teams a ready-to-run environment for every conversation.
Use case
Internal labs
Stand up hands-on environments for training, enablement, and internal testing.
Use case
QA and validation
Create short-lived test environments for release checks and validation work.
Use case
Agent-driven operations
Give operators and agents the same environment on demand.
Product showcase
Environment launch details
3 services healthy
Workflow
ceph-cluster-demo
Launchpack
Access endpoints
Readiness checks
Runbook notes
Lifecycle
Cleanup scheduled
Launch approved2 min ago
Spinner install complete6 min ago
TTL expiry queued8h remaining
Readiness
Environment state
Ready
SSH bastion
Console URL
Operator runbook
Product
One place to launch, inspect, access, and retire environments
See readiness, access, and lifecycle state in one operator view.
Launch reusable workflows in minutes
Track environment state and readiness
Surface access endpoints and operational guidance
Enforce TTLs and lifecycle cleanup
Keep every launch on a consistent path
Guardrails
Ephemeral by default. Guarded by policy.
Spinly keeps temporary infrastructure safe and controlled by default.
Control
TTL enforcement
Control
Cleanup automation
Control
Launch guardrails
Control
Repeatable execution paths
Control
Auditability
Control
Reduced orphaned infrastructure
Developers and agents
Built for humans and agents
Use Spinly through the UI or API for the same actions across operators, automation, and agents.
Spinly 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
Package the workflow once. Launch it when you need it. Retire it automatically.