Examples

Your canvas starts empty because Spawned does not guess what your system should look like. That decision is yours, and it is the interesting one: the same application can be one container or four, keep files on a disk or in a bucket, run work on a timer or all day long, and each choice pulls the rest of the design behind it.

Each page here is a worked example of that. It takes one architecture apart, explains what every connection actually provisions, argues the decisions it embodies, and says where it stops holding up. The infra.json on each page is the whole thing rather than an excerpt, and the diagram beside it is that file rendered through the product’s own canvas.

New to building with Spawned? Start with Components & Connections.