Core Concepts
Understanding these concepts will help you get the most out of plutonium.io.
Architecture Overview
plutonium.io is built around three pillars:
| Pillar | Purpose | Examples |
|---|---|---|
| Compute | Run your code close to users | Lambdas, edge functions |
| Storage | Persist and query data | S3, DynamoDB |
| Delivery | Ship changes quickly | CI/CD, preview deploys |
Projects
A project is the top-level container for your work. Each project has its own:
- Configuration
- Environment variables
- Deploy history
- Access controls
Environments
Every project ships with three environments by default:
- Development — local iteration with hot reload
- Staging — pre-production validation
- Production — live traffic
Resources
Resources are the infrastructure components that back your project. They are declared in configuration and managed automatically.
Tip: You don’t need to provision resources manually. Declare what you need and plutonium.io handles the rest.
Workflows
A workflow chains multiple steps into a deploy pipeline:
steps:
- name: test
run: npm test
- name: build
run: npm run build
- name: deploy
run: plutonium deploy --env production
Each step runs in an isolated environment and has access to project secrets.