Project Dashboard
Everything for a project lives on its dashboard, built around a live map of your infrastructure.
When you open a project, a sidebar on the left gives you five sections: Infrastructure, Versions, Usage, Security, and Settings.
Infrastructure
The infrastructure view is your main workspace: a live diagram of every component in your project and how they connect. It is where you build and change your setup.
- Add components. Use the Add button, or right-click the canvas, to add compute, storage, networking, and more.
- Connect components. Turn on connect mode and click one component, then another, to wire them together. A connection handles the plumbing for you, such as passing a database’s credentials to a container or routing a domain to it.
- Inspect and configure. Click any component to open its details (see below).
- Check status at a glance. Each component shows its health on the canvas, along with any changes waiting to be applied.
- See the source. The Source button opens your project’s
infra.json, the declarative definition of everything on the canvas.
You don’t have to build on the canvas by hand. Point your coding agent at Spawned and let it generate your infrastructure with the CLI.
Component details
Click a component to open its panel. The available tabs depend on what the component is.
| Tab | What it shows |
|---|---|
| Properties | The component’s settings. For a Secret, a key/value editor where you can type values or paste a .env file. |
| Logs | Live runtime logs, for containers and functions. |
| Replicas | The running instances of a container, with a rolling restart. |
| Files | A file browser for a bucket: upload, download, and organize objects. |
| Outputs | Live values such as generated URLs and DNS records. |
| Connections | What this component depends on, and what depends on it. |
| Settings | Remove the component. |
Applying changes
Edits on the canvas do not go live immediately. They collect as pending changes, shown in a bar with Details, Apply, and Discard.
When you Apply, Spawned builds and provisions the changes. A status indicator shows progress and links to the build logs if something fails. There is no separate deploy button. You make your changes, review them, and apply.
Versions
Every apply creates a new version of your project, which is backed by Git. The Versions view is a timeline of those versions. Open any one to see its build logs and a read-only snapshot of your infrastructure as it was at that point. This is where you go to watch a deploy in progress or debug one that failed.
Usage
A breakdown of your project’s cloud cost over time: the total, a daily average, the trend against the previous period, and a per-day table. Switch between the last 7, 30, and 90 days.
Cloud cost data is typically delayed by a few days, so the most recent usage can take time to appear.
Security
A security posture scan of your project. You get an overall grade, a count of passing checks and open issues, and expandable categories with the specific findings and links to remediation guidance. It populates once your infrastructure is deployed.
Settings
Project-level actions:
- Rename the project and set its icon.
- Clone with Git. Generate an API key and copy a
git clonecommand to pull the project’sinfra.jsondown locally. - Export the project as a zip.
- Delete the project.