How It Works

Spawned turns a description of your infrastructure into running cloud resources. Here is the path from idea to live.

1. Describe your infrastructure

You lay out what your app needs as components (a container for your code, a database, a bucket, a domain) and draw connections between them. Together, this description is your project’s infra.json.

You can build it three ways, and mix them freely:

• On the infrastructure canvas, visually.
• With the CLI, editing the infra.json directly.
• By pointing your coding agent at Spawned and letting it write the infra.json for you.

See Components & Connections for the building blocks.

2. Spawned compiles it

Spawned compiles your description into real infrastructure configuration for wherever the project runs, and applies it directly to the selected cloud. Security defaults and best practices are built into this step, so you get safe, sensible infrastructure without configuring it yourself.

Every infrastructure application is tracked as a new version, so you can see exactly what changed and revisit any point in your project’s history.

3. You run and manage it

From the project dashboard you operate everything in one place: view logs, track cost, check health, manage secrets, and restart services, without ever touching a cloud console.

Where projects run

A project runs on a Cloud you connect, that can be a Kubernetes cluster, or a commercial cloud platform such as AWS. The same components describe your app either way, and Spawned handles the translation. See AWS and Kubernetes.